From: Manfred Spraul <manfred@colorfullife.com>
To: Bob Matthews <bmatthews@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.14-pre8 stress testing
Date: Tue, 06 Nov 2001 22:09:28 +0100 [thread overview]
Message-ID: <3BE85187.B9454EA2@colorfullife.com> (raw)
> 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
next reply other threads:[~2001-11-06 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-06 21:09 Manfred Spraul [this message]
2001-11-06 21:27 ` 2.4.14-pre8 stress testing Bob Matthews
-- strict thread matches above, loose matches on Subject: below --
2001-11-06 19:40 Bob Matthews
2001-11-07 15:58 ` Bob Matthews
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3BE85187.B9454EA2@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=bmatthews@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox