Activity log for bug #253852

Date Who What changed Old value New value Message
2008-08-01 03:36:49 Jeremy Bar bug added bug
2008-08-01 03:36:49 Jeremy Bar bug added attachment 'freeze-bug.tgz' (Compressed Tar archive containing logs.)
2008-08-29 00:24:23 Leann Ogasawara bug added subscriber Leann Ogasawara
2008-11-01 18:36:43 Shyam displayname Bug #253852 Bug #253852 (shyam)
2008-11-01 18:36:43 Shyam name shyam
2008-11-01 18:36:43 Shyam description I looked at similar bugs, but the characteristic of those kind of issues being limited information, I couldn't be sure that my case was exactly the same as an other, so I opened a new bug. Typically, those kind of hangs are very hard to diagnose because of the lack of logging. (See further on how I got more info) So, what happens is that my IBM Lenovo Thinkpad x60s totally locks frozen after some time on a daily basis. Even during the night under light load. Higher network load seems to make it hang faster, especially when it acts as a router and traffic transitions through it to an other machine on the internal network. (I was running Windows XP before that and I never had any problems of this kind) At this point, I can say that the problem is reproducible daily. I am lucky that my file system didn't get corrupted yet with all the daily hangs ... I hope it will not happen as I type this bug report. Technical information: Ubuntu 8.04.1 Hardy uname -a Linux travel 2.6.24-19-generic #1 SMP Fri Jul 11 23:41:49 UTC 2008 i686 GNU/Linux cat /proc/cmdline root=/dev/mapper/travel-root ro console=ttyS0,115200n8 console=tty0 "Visual Effects" disabled. I use an encrypted file system. (Installed from alternate CD) I use shorewall for my firewall rules. I installed the linux-backports-modules-hardy package for the latest iwl3945. I also use an external monitor with 1600x1200 resolution. (See X log file for more info) The x60s sits on its docking station. All cables run from it. The BIOS is the latest. (v2.17, see dmidecode output) I didn't perform a suspend-resume cycle before the machine hang. I use 2.6.24-19-generic and couldn't test with 2.6.24-20-generic because my system doesn't boot with it. (The subject of an other coming bug report) Being tired of those freezes every days with no error message written to the disk, I finally got the time to purchase a null modem cable, connected from the docking station to an other laptop running minicom, enabled printk capture at boot and I got the following lines printed at the point of freeze: [25408.657345] Uhhuh. NMI received for unknown reason a1 on CPU 0. [25408.663266] You have some hardware problem, likely on the PCI bus. [25408.669440] Dazed and confused, but trying to continue Other than that, the information files are attached in a tar archive: dmesg.log lspci-vvnn.log lspci-vv.log xorg.conf dpkg-l.log lsmod.log proc-interrupts.log Xorg.0.log dmidecode.log smartctl_--all_-d_ata_dev+sda.log sysctl-a.log cpuinfo.log Hope it helps. I am completely new user to Ubuntu desktop edition. Yes I am also facing this problem , I am running hardy on my Dell Vostro 1310 , All of a sudden without any error laptop hangs/Freezs only wait to bring it back is power down and power on happening frequently... uname -a Linux xxxx-laptop 2.6.24-21-generic #1 SMP Tue Oct 21 23:43:45 UTC 2008 i686 GNU/Linux cat /proc/cmdline root=UUID=ed31cd50-f48d-414a-8efd-02b4401a5c5e ro quiet splash tail -f /var/log/kern.log Nov 1 23:09:47 shyam-laptop kernel: [ 51.145259] groups: 02 01 Nov 1 23:09:47 shyam-laptop kernel: [ 51.145265] domain 1: span 03 Nov 1 23:09:47 shyam-laptop kernel: [ 51.145269] groups: 03 Nov 1 23:10:20 shyam-laptop kernel: [ 57.103717] usb 1-2: new full speed USB device using uhci_hcd and address 2 Nov 1 23:10:20 shyam-laptop kernel: [ 57.287025] usb 1-2: configuration #1 chosen from 1 choice Nov 1 23:10:20 shyam-laptop kernel: [ 57.423421] Bluetooth: HCI USB driver ver 2.9 Nov 1 23:10:20 shyam-laptop kernel: [ 57.424723] usbcore: registered new interface driver hci_usb Nov 1 23:10:56 shyam-laptop kernel: [ 66.689572] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready Nov 1 23:11:06 shyam-laptop kernel: [ 67.905980] eth1: no IPv6 routers present Nov 1 23:11:18 shyam-laptop kernel: [ 69.313309] eth1: no IPv6 routers present Nov 1 23:10:20 shyam-laptop kernel: [ 57.424723] usbcore: registered new interface driver hci_usb Nov 1 23:10:54 shyam-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.reason Nov 1 23:10:56 shyam-laptop kernel: [ 66.689572] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready Nov 1 23:11:07 shyam-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.host_name Nov 1 23:11:07 shyam-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.domain_name Nov 1 23:11:07 shyam-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.nis_domain Nov 1 23:11:07 shyam-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.nis_servers Nov 1 23:11:07 shyam-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.interface_mtu Nov 1 23:29:08 shyam-laptop -- MARK -- Nov 1 23:49:08 shyam-laptop -- MARK -- is it because of DHCPbd handler i am not sure on this , Help me out on this.
2008-11-22 00:04:50 Leann Ogasawara linux: status New Incomplete
2008-11-22 00:04:50 Leann Ogasawara linux: statusexplanation Hi Jeremy, The Intrepid Ibex 8.10 final release came out last month. Just curious if you have been able to test and confirm if htis is still an issue? Thanks.
2009-01-11 08:58:39 Javier Jardón linux: status Incomplete Invalid
2009-01-11 08:58:39 Javier Jardón linux: statusexplanation Hi Jeremy, The Intrepid Ibex 8.10 final release came out last month. Just curious if you have been able to test and confirm if htis is still an issue? Thanks. We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!