From: Kevin Brosius <cobra@compuserve.com>
To: kernel <linux-kernel@vger.kernel.org>
Subject: 2.5.49+ and sysrq (may lock with modules loaded)?
Date: Sun, 24 Nov 2002 23:37:51 -0500 [thread overview]
Message-ID: <3DE1A91F.8871C2D4@compuserve.com> (raw)
I was trying to use sysrq tonight and had a couple problems. While the
Doc/sysrq.txt file says it is enabled by default, it does not appear to
be any longer. After enabling sysrq with an echo "1" to the sysrq /proc
entry, I tried an alt-sysrq-t, and promptly had a kernel oops in the
print routine, for a failed kernel paging request. The machine is hard
locked at this point and must be reset (sysrq no longer responds.)
I tried to repeat this, to write down some of the oops, but on reboot
(prior to loading any modules) I could not get any printout from sysrq
other than the HELP message. In response to alt-sysrq-t I only see the
first "SysRq : " printout with no task info.
The first run had some modules I had manually loaded, so I went ahead
and insmod'd sound.o and usbcore.o. After that, alt-sysrq-t causes an
oops. Here's a snippet (by hand):
Oops
EIP 0060:c0134c48
__print_symbol+0x48/0x120
process swapper
Call Trace
e094ae89 Unable to handle kernel paging request
An EIP lookup on my vmlinux yields:
(gdb) l *0xc0134c48
Line 190 of "include/asm/string.h" starts at address 0xc0134c3f
<__print_symbol+63> and ends at 0xc0134c5c <__print_symbol+92>.
\x1a\x1a/usr/src/linux-bk/include/asm-i386/string.h:190:4260:beg:0xc0134c3f
I'm using a recent bk tree (a day or two old), so the relevant portion
from string.h appears to be:
#define __HAVE_ARCH_STRLEN
static inline size_t strlen(const char * s)
{
int d0;
register int __res;
__asm__ __volatile__(
"repne\n\t"
"scasb\n\t"
"notl %0\n\t"
"decl %0"
:"=c" (__res), "=&D" (d0) :"1" (s),"a" (0), "0" (0xffffffff));
return __res;
}
with the
__asm__ __volatile__(
line being pointed out by my debugger.
--
Kevin
reply other threads:[~2002-11-25 4:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3DE1A91F.8871C2D4@compuserve.com \
--to=cobra@compuserve.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
all inboxes | Powered by JetHome®