Description of problem: Serial consoles use "break" in place of the sysrq key. Sending a break on my HP Integrity servers via the remote console hangs the system to the point where the system does not even respond to ping. This makes it nearly impossible to debug hang situations. If the system is alive sending a character to /proc/sysrq-trigger still does work OK so this appears to be a serial console issue rather than a sysrq issue. Version-Release number of selected component (if applicable): kernel-2.6.16-1.2203_FC6 (note, this is the first I have tried this on rawhide so I do not know when this last worked) How reproducible: 100% Steps to Reproduce: 1. connect to an HP Integrity server via telnet to the MP 2. log in to the MP 3. type "co" to connect to the console 4. send a break using telnet: <ctrl>-] then "send break" Actual results: system hangs Expected results: Additional info:
I think this was due to the kgdb patches I was experimenting with. It's likely this is fixed now, as they've been reverted.
Appears that this is a different problem. I am still seeing the hang on 2.6.16-1.2289_FC6. Please let me know if there is something I can do to provide more info that would be useful.
FYI, a little more info... If you do not have the sysrq key enabled a "break" does not cause the hang. But, if sysrq key is enabled (i.e. by adding kernel.sysrq = 1 to /etc/sysctl.conf) we get then hang when we send a "break".
This appears to be working now. Verified in 2.6.17-1.2600.fc6.