From: Andreas Dilger <adilger@clusterfs.com>
To: Robert White <rwhite@casabyte.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: continuous backtrace ... ?
Date: Mon, 16 Jun 2003 15:55:07 -0600 [thread overview]
Message-ID: <20030616155507.L26944@schatzie.adilger.int> (raw)
In-Reply-To: <PEEPIDHAKMCGHDBJLHKGCEPICPAA.rwhite@casabyte.com>; from rwhite@casabyte.com on Mon, Jun 16, 2003 at 12:15:41PM -0700
On Jun 16, 2003 12:15 -0700, Robert White wrote:
> I have a 2.5.70 kernel image which, at boot, goes into a continuously
> looping backtrace. It scrolls up the screen too fast and continuously to
> read but it is clearly a backtrace. If I just relax and watch I can see the
> [bracketed hex] and routine name shape of it whizzing by.
>
> This happens while the file systems are read only and the system doesn't
> respond to the keyboard at all.
>
> Is there any good way to capture this stream of data in any kind of useful
> way? or at least pause the spew so that I can find the general locus of the
> problem?
>
> Given the immediacy of the problem (it appears just-about-concurrently with
> attempt to draw the boot logo) I suspect that it has something to do with
> the console driver (radeon frame buffer VGA console in normal mode)
> interacting with my All-In-Wonder 9700 pro and the very new P4-3ghz in
> hyperthreading mode.
Probably a stack overflow. Once you hit the do_IRQ() stack overflow
detection code, you get stuck in a loop because your console output is
slow enough that you immediately get another IRQ, rinse, repeat.
I fixed this locally by adding a static jiffies counter to rate-limit
the overflow stack dump to once per 5 seconds. If you overflow your
stack more often than that, well too bad. At least you have a chance
to look at your console instead of the machine essentially being wedged.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
prev parent reply other threads:[~2003-06-16 21:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-16 19:15 Robert White
2003-06-16 21:55 ` Andreas Dilger [this message]
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=20030616155507.L26944@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rwhite@casabyte.com \
/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®