Adam Tauno Williams said the following on 03/18/2010 02:39 PM:
On Thu, 2010-03-18 at 14:24 -0400, Anton Aylward wrote:
Claudio Prono said the following on 03/18/2010 11:53 AM:
It's really annoying.. nothing in the logs anywhere... no clues as to what's going wrong... just sold hard lockup that only a full reset can recover from.
+1
Have you tried seeing is SysRq still works after the oops?
Maybe its these odd key combinations on the laptop but no, I haven't been able to get sysrq to work alt+[fn]+end,h 'end' is also labelled [sysrq] laptop, remember, so a dozen and a half keys have that additional labelling. And yes, I have tried alt+[fn]+home,h 'cos "home" is labelled [prtsc] That doesn't work either. And yes I checked that /proc/sys/kernel/sysrq was set to "1" What do you suggest now? -- "If you have only one layer of protection you are only as safe as the next bug-de-jour" - Brad M Powell, Snr Network Security Architect, Sun Microsystems -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org