Skip to contentSkip to conversation

2.4.14-pre8 stress testing

DISCUSSION Manfred Spraul 2 participants 2 messages Nov 6, 2001

lore
Share & tools
lore
#0 lore raw
Quoted 3 lines

Magic Sysrq doesn't give me anything except the name of the
corresponding command. The machine does not appear to have generated any oops output.

Was just one command name printed, or multiple commands?
The sysrq handlers are protected by a spinlock.
If multiple command names were printed it means that the sysrq handlers themself returned, and that printk works.

I bet that the console loglevel got corrupted.
The sysrq handler should run with forced loglevel 7, like the print of the command name.

Did you try SysRQ+7?

--
Manfred

#1 lore raw
Quoted 9 lines · Manfred Spraul
Quoted 4 lines

Magic Sysrq doesn't give me anything except the name of the
corresponding command. The machine does not appear to have generated any oops output.

Was just one command name printed, or multiple commands?
The sysrq handlers are protected by a spinlock.
If multiple command names were printed it means that the sysrq handlers themself returned, and that printk works.

Multiple command names were printed, i.e.

<alt><SysRq>T produces SysRq: Show State, but nothing more <alt><SysRq>P produces SysRq: Show Regs, but nothing else, etc.

Quoted 6 lines

I bet that the console loglevel got corrupted.
The sysrq handler should run with forced loglevel 7, like the print of the command name.

Did you try SysRQ+7?

I tried resetting the loglevel to 7. Same results.

Signature · 2 lines
Bob Matthews
Red Hat, Inc.