Hi jhansonxi,

First if you can confirm if Bryce's suggestions work or not that would
be great.  If the issue still exists, one thing you may want to give a
try is booting with the kernel parameter nmi_watchdog=1 .  I've included
a small explanation of what this parameter is used for:

"On many x86/x86-64 type hardware there is a feature that enables us to 
generate 'watchdog NMI interrupts'.  (NMI: Non Maskable Interrupt which get 
executed even if the system is otherwise locked up hard).  This can be used to 
debug hard kernel lockups.  By executing periodic NMI interrupts, the kernel 
can monitor whether any CPU has locked up, and print out debugging messages if 
so. . . .A 'lockup' is the following scenario: if any CPU in the system does 
not execute the period local timer interrupt for more than 5 seconds, then the 
NMI handler generates an oops and kills the process. This
'controlled crash' (and the resulting kernel messages) can be used to debug the 
lockup. Thus whenever the lockup happens, wait 5 seconds and the oops will show 
up automatically. If the kernel produces no messages then the system has 
crashed so hard (eg. hardware-wise) that either it cannot even accept NMI 
interrupts, or the crash has made the kernel unable to print messages."

Please let us know your results using this parameter.  If you could also
attach the output of 'cat /proc/version_signature' so we know the exact
kernel version you are running that would be great as well.

Additionally, I may also have you test an newer kernel available in the
kernel-ppa (personal package archive).  It is still however in the
process of being built so won't be available for the next day or so.
I'll be sure to update this report and provide instructions on how to
install when it is ready.  But, in the mean time if you could do the
above testing requested by Bryce as well as myself that would be great.
Thanks!

-- 
855GME system freezes when switching to external monitor
https://bugs.launchpad.net/bugs/213191
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

Reply via email to