Most recent kernel where this bug did *NOT* occur:2.6.18 (suse 10.2) Distribution:Gentoo Hardware Environment:HP DV9008NR with MCP51 chipset Software Environment:Sabayon Linux 3.26 (without nvidia module loaded) Problem Description: This laptop will hard lock up (with Caps Lock LED blinking) anywhere from 5 minutes to 48 hours of use with no output from dmesg or /var/log/messages. This happends with multiple distros and mutiple kernel versions, so I don't think it is a distro problem, but rather a kernel problem. There have been many forum threads on gentoo, linuxquestions, and fedora forums concerning this issue. Steps to reproduce: This has been reproduced with Fedora Core 6 x86_64, Kubuntu 6.10 x86_64, Knoppix 5.01 x86, and Sabayon Linux 3.26 x86_64 (without nvidia module). Using Sabayon, I recompiled the kernel using vanilla-sources-2.6.19 and the 2.6.19-r4 config. This had no effect. Suse 10.2 x86_64 seems to run smoothly without incident. I copied the Suse10.2 config and compiled it against the 2.6.19-r4 kernel on Sabayon. This hung at "Setting System Clock...". I also tried the 2.6.20-rc5 tree without sucess. What should I enable in the kernel config to allow for more debugging output before lockup? What other information is required?
Are you able to reproduce that bug on the shell without framebuffer enabled?
Please reopen this bug if: - it is still present with kernel 2.6.22 and - you can provide the requested information.