Well, it happened again at a convenient time (at exactly 12:37, in case that's relevant), so I'm posting the four relevant logs again:
/var/log/messages
Code:
Oct 30 12:37:01 altay-laptop kernel: [ 8.522624] eth0: RealTek RTL8139 at 0xa000, 00:0f:b0:70:a3:47, IRQ 20
Oct 30 12:37:02 altay-laptop kernel: [ 9.670617] input: b43-phy0 as /devices/virtual/input/input10
Oct 30 12:37:02 altay-laptop kernel: [ 4.996538] [drm] Loading R300 Microcode
Oct 30 12:37:03 altay-laptop kernel: [ 5.998867] Registered led device: b43-phy0:tx
Oct 30 12:37:03 altay-laptop kernel: [ 5.999079] Registered led device: b43-phy0:rx
Oct 30 12:37:03 altay-laptop kernel: [ 5.999219] Registered led device: b43-phy0:radio
Oct 30 12:37:03 altay-laptop kernel: [ 6.037029] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Oct 30 12:37:05 altay-laptop kernel: [ 15.651921] eth0: link up, 10Mbps, full-duplex, lpa 0x4061
Oct 30 12:37:08 altay-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name
Oct 30 12:37:08 altay-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
Oct 30 12:37:08 altay-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers
Oct 30 12:37:08 altay-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.interface_mtu
/var/log/syslog
Code:
Oct 30 12:37:09 altay-laptop NetworkManager: <info> Activation (eth0) Finish handler scheduled.
Oct 30 12:37:09 altay-laptop NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
Oct 30 12:37:10 altay-laptop dhclient: Discarding packet with bogus hlen.
Oct 30 12:37:10 altay-laptop avahi-daemon[5104]: Registering new address record for fe80::20f:b0ff:fe70:a347 on eth0.*.
Oct 30 12:37:10 altay-laptop dhclient: Discarding packet with bogus hlen.
Oct 30 12:37:13 altay-laptop ntpdate[15384]: no server suitable for synchronization found
Oct 30 12:37:15 altay-laptop dhclient: Discarding packet with bogus hlen.
Oct 30 12:37:18 altay-laptop dhclient: Discarding packet with bogus hlen.
Oct 30 12:37:19 altay-laptop kernel: [ 29.580392] eth0: no IPv6 routers present
Oct 30 12:37:21 altay-laptop dhclient: Discarding packet with bogus hlen.
Oct 30 12:37:52 altay-laptop last message repeated 12 times
Oct 30 12:38:56 altay-laptop last message repeated 22 times
Oct 30 12:39:57 altay-laptop last message repeated 20 times
Oct 30 12:41:00 altay-laptop last message repeated 19 times
Oct 30 12:42:01 altay-laptop last message repeated 18 times
Oct 30 12:42:53 altay-laptop last message repeated 18 times
Oct 30 12:44:06 altay-laptop last message repeated 23 times
/var/log/kern.log
Code:
Oct 30 12:37:02 altay-laptop kernel: [ 9.978113] b43-phy0 debug: Loading firmware version 351.126 (2006-07-29 05:54:02)
Oct 30 12:37:02 altay-laptop kernel: [ 4.996538] [drm] Loading R300 Microcode
Oct 30 12:37:03 altay-laptop kernel: [ 5.996499] b43-phy0 debug: Chip initialized
Oct 30 12:37:03 altay-laptop kernel: [ 5.996968] b43-phy0 debug: 30-bit DMA initialized
Oct 30 12:37:03 altay-laptop kernel: [ 5.998867] Registered led device: b43-phy0:tx
Oct 30 12:37:03 altay-laptop kernel: [ 5.999079] Registered led device: b43-phy0:rx
Oct 30 12:37:03 altay-laptop kernel: [ 5.999219] Registered led device: b43-phy0:radio
Oct 30 12:37:03 altay-laptop kernel: [ 5.999259] b43-phy0 debug: Wireless interface started
Oct 30 12:37:03 altay-laptop kernel: [ 6.036351] b43-phy0 debug: Adding Interface type 2
Oct 30 12:37:03 altay-laptop kernel: [ 6.037029] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Oct 30 12:37:05 altay-laptop kernel: [ 15.651921] eth0: link up, 10Mbps, full-duplex, lpa 0x4061
Oct 30 12:37:19 altay-laptop kernel: [ 29.580392] eth0: no IPv6 routers present
/var/log/daemon.log
Code:
Oct 30 12:37:09 altay-laptop NetworkManager: <info> Activation (eth0) successful, device activated.
Oct 30 12:37:09 altay-laptop NetworkManager: <info> Activation (eth0) Finish handler scheduled.
Oct 30 12:37:09 altay-laptop NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
Oct 30 12:37:10 altay-laptop dhclient: Discarding packet with bogus hlen.
Oct 30 12:37:10 altay-laptop avahi-daemon[5104]: Registering new address record for fe80::20f:b0ff:fe70:a347 on eth0.*.
Oct 30 12:37:10 altay-laptop dhclient: Discarding packet with bogus hlen.
Oct 30 12:37:13 altay-laptop ntpdate[15384]: no server suitable for synchronization found
Oct 30 12:37:15 altay-laptop dhclient: Discarding packet with bogus hlen.
Oct 30 12:37:46 altay-laptop last message repeated 11 times
Oct 30 12:38:47 altay-laptop last message repeated 21 times
Oct 30 12:39:49 altay-laptop last message repeated 21 times
Oct 30 12:40:55 altay-laptop last message repeated 20 times
Oct 30 12:41:57 altay-laptop last message repeated 16 times
Oct 30 12:42:53 altay-laptop last message repeated 22 times
Oct 30 12:44:06 altay-laptop last message repeated 23 times
Oct 30 12:45:08 altay-laptop last message repeated 15 times
Oct 30 12:46:09 altay-laptop last message repeated 17 times
Oct 30 12:46:59 altay-laptop last message repeated 17 times
I guess I'm just going to shut down the computer because restarting hal and dbus didn't work last time. Let me know if you have any new ideas.
I plan to upgrade to Intrepid Ibex relatively soon via clean install, probably on its own partition at first. I'll see if that changes the issue in any way. Perhaps it will solve the problem, but I'm convinced it's linked to the ATI driver, so it probably won't.
Bookmarks