Gareth, Thanks for the quick following up. I have to moderate my earlier complain about kernel 2.6. Doing further tests, I noticed that firefox was able to cause trouble (wild CPU and disk usage and I am becoming a little quick to force a computer shutdown because of the freezes).
Nevertheless, I still experience freezes. Here are the data: 1- "uname" Linux localhost 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 GNU/Linux 2- dmesg (see file attached - done right after a freeze-forced reboot; doing dmesg during a freeze does not let me save the output anywhere on the disk, neither on a thumbdrive, and email software is frozen - all IO on storage seem unavailable) 3- lspci (see file attached) 4- dmidecode (see file attached) Notes: I have found nothing that seemed relevant in either syslog, kern.log, or messages. log/messages says ata2.00: ATAPI: TSSTcorpCD/DVDW TS-L632D, SC04, max UDMA/33 about the optical drive. All the above was done while booting with the kernel parameter combined_mode=libata 2008/4/23 Gareth Fitzworthington <[EMAIL PROTECTED]>: > Lau, > OK we've checked some likely causes with no success. I think we need to move > this issue along to the Kernel Team. > > However, we need to re-establish the baseline data for this bug report since > the problem was originally reported under Feisty and you now appear to be > using Hardy. The Kernel Team will need this. > Can you supply the following information for your present system [Hardy]: > 1. Please include the output of the command "uname -a" in your next response. > 2. Please run the command "dmesg > dmesg.log" which includes the freeze > point and attach the resulting file "dmesg.log" to this bug report. > 3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the > resulting file "lspci-vvnn.log" to this bug report. > 4. Please run the command "sudo dmidecode > dmidecode.txt" and attach the > resulting file "dmidecode.txt" to this bug report. > Thanks. > > Note1: Point (2) above should include the freeze point. If you can get it to > freeze again and then reboot the dmesg should contain the freeze point. > Note2: Also, after a freeze & reboot can you check syslog and kernel.log to > see if anything useful is recorded such as a kernel oops. > Note3: Your TSSTcorpCD/DVDW TS-L632D optical drive still concerns me. Can > you check & report the present firmware version [AS05, SC03, SC04, something > else?] just to put our minds at ease. > > Thanks again. > > ** Also affects: linux-source-2.6.22 (Ubuntu) > Importance: Undecided > Status: New > > ** Changed in: linux-source-2.6.22 (Ubuntu) > Status: New => Incomplete > > ** Also affects: linux-source-2.6.24 (Ubuntu) > Importance: Undecided > Status: New > > ** Changed in: linux (Ubuntu) > Sourcepackagename: linux-source-2.6.24 => linux > Status: New => Incomplete > > ** Also affects: linux-source-2.6.17 (Ubuntu) > Importance: Undecided > Status: New > > ** Changed in: linux-source-2.6.17 (Ubuntu) > Status: New => Incomplete > > -- > > > system locking up (forcing a hard reboot) > https://bugs.launchpad.net/bugs/89362 > You received this bug notification because you are a direct subscriber > of the bug. > ** Attachment added: "dmesg_postfreeze.txt" http://launchpadlibrarian.net/14189341/dmesg_postfreeze.txt ** Attachment added: "lspci-vvnn.log" http://launchpadlibrarian.net/14189342/lspci-vvnn.log ** Attachment added: "dmidecode.txt" http://launchpadlibrarian.net/14189343/dmidecode.txt -- system locking up (forcing a hard reboot) https://bugs.launchpad.net/bugs/89362 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
