random system freeze with blinking caps lock led, Intrepid 8.10 beta

[jbrea]

kernel 2.6.27-7-generic

system locks randomly with blinking caps lock led on my lenovo X200 notebook.

[Chris Coulson (chrisccoulson)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.

Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot 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 try to recreate the crash and then attach /var/log/kern.log and /var/log/kern.log.0.
5. Please run a memory test, following the procedure at https://help.ubuntu.com/community/MemoryTest

For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance!

[jbrea (johannibrea)]

jb@schulnotebook:~$ uname -a
Linux schulnotebook 2.6.27-7-generic #1 SMP Fri Oct 24 06:42:44 UTC 2008 i686 GNU/Linux

[jbrea (johannibrea)]

my kern.log is approximately 1.7G large. I therefore just append the last 10000 lines

[jbrea (johannibrea)]

This might also be linked to the occurance of 100% CPU usage of dd, kslog and syslog.
After the last startup (and probably opening firefox), those processes used 100 % of CPU. Since I killed them, the system runs smoothly.

[Chris Coulson (chrisccoulson)]

jbrea - I think dd, klogd and syslog are running at 100% CPU usage as a side effect of the amount of errors being written to your logs. 1.7GB is not normal.

Anyway, this looks like a duplicate of bug 286285

[Tom Jaeger (thjaeger)]

jbrea, the original issue that you reported is bug #276990.