Re: 2.4.14-pre8 stress testing

Bob Matthews (bmatthews@redhat.com)
Tue, 06 Nov 2001 16:27:50 -0500

Manfred Spraul wrote:
>
> > 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.

>
> 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.

-- 
Bob Matthews
Red Hat, Inc.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/