From: Andreas Dilger <adilger@turbolinux.com>
To: Vibol Hou <vhou@khmer.cc>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: kernel BUG doing sysrq-t on 2.4.2-ac14
Date: Thu, 8 Mar 2001 12:34:15 -0700 (MST) [thread overview]
Message-ID: <200103081934.f28JYGS05891@webber.adilger.net> (raw)
In-Reply-To: <NDBBKKONDOBLNCIOPCGHCEEBFEAA.vhou@khmer.cc> from Vibol Hou at "Mar 8, 2001 11:06:08 am"
Vibol writes:
> While testing to see if SYSRQ-T would print the entire tasklist, a kernel
> bug popped up. All I have is the tasklist up to the point where the bug
> showed up.
Actually, if you look closely, there is an OOPS report in there at the
end as well. Unfortunately, since the tasklist output also looks like
an OOPS, it is basically impossible to extract.
> SNIP
> [<c01e071d>] [<c01e079b>] [<c013cd93>] [<c013NceMIf5 W>]a tch<4d>og[<
> cde
> 01t0ec95t5ed7> L]O CK
> UPh ottnp Cd PU 0 , reSg is7FteFFrsF:FF
You can see it says "NMI Watchdog detected LOCKUP on CPU 0, registers:"
> [< c0109557>] kernel BUG at printk.c:327!
It may be that if the tasklist is too long, and it runs with interrupts
disabled, that this will trigger the NMI watchdog timer. Since I don't
know anything about the console, I can't help.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
next prev parent reply other threads:[~2001-03-08 19:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-08 19:06 Vibol Hou
2001-03-08 19:34 ` Andreas Dilger [this message]
2001-03-08 23:32 ` Andrew Morton
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=200103081934.f28JYGS05891@webber.adilger.net \
--to=adilger@turbolinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vhou@khmer.cc \
/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®