From: Theodore Tso <tytso@MIT.EDU>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org, mingo@elte.hu,
akpm@linux-foundation.org
Subject: Re: Make the 32 bit Frame Pointer backtracer fall back to traditional
Date: Fri, 11 Jan 2008 17:01:43 -0500 [thread overview]
Message-ID: <20080111220142.GA6751@mit.edu> (raw)
In-Reply-To: <alpine.LFD.1.00.0801111136520.3148@woody.linux-foundation.org>
On Fri, Jan 11, 2008 at 11:41:40AM -0800, Linus Torvalds wrote:
>
> (I also wonder if we should limit the number of entries we print out.
> Sometimes the stack frame ends up being so deep that we lose the
> *important* stuff. I think it might be good idea to have some rule like
> "the first 5 entries go to the screen, the rest will be KERN_DEBUG and
> only go to the logs by default" - so a "dmesg" would show it all, but if
> the machine is hung, the screen won't have been scrolled away from all
> the other things by a long backtrace!)
What might be useful is the first 5 and last 5. Sometimes if you have
a very deep call chain, the what was the original system call or
interrupt which got the kernel deep into la-la land can often be
useful. Just a thought.
- Ted
prev parent reply other threads:[~2008-01-11 22:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 6:05 Arjan van de Ven
2008-01-10 6:21 ` Harvey Harrison
2008-01-10 12:46 ` Ingo Molnar
2008-01-10 15:15 ` Arjan van de Ven
2008-01-10 6:55 ` Ingo Molnar
2008-01-10 16:36 ` Linus Torvalds
2008-01-10 16:49 ` Arjan van de Ven
2008-01-11 4:35 ` Arjan van de Ven
2008-01-11 11:54 ` Olaf Dietsche
2008-01-11 19:41 ` Linus Torvalds
2008-01-11 19:56 ` Arjan van de Ven
2008-01-11 22:01 ` Theodore Tso [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=20080111220142.GA6751@mit.edu \
--to=tytso@mit.edu \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.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®