From: Bill Huey (hui) <billh@gnuppy.monkey.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
"Bill Huey (hui)" <billh@gnuppy.monkey.org>
Subject: Re: 2.6.17-rt8 crash amd64
Date: Tue, 1 Aug 2006 19:25:39 -0700 [thread overview]
Message-ID: <20060802022539.GA26799@gnuppy.monkey.org> (raw)
In-Reply-To: <20060802021956.GC26364@gnuppy.monkey.org>
On Tue, Aug 01, 2006 at 07:19:56PM -0700, Bill Huey wrote:
> On Tue, Aug 01, 2006 at 09:31:42PM -0400, Steven Rostedt wrote:
> > On Tue, 2006-08-01 at 18:18 -0700, Bill Huey wrote:
> > > [ 42.124525] <ffffffff8029ae98>{atomic_dec_and_spin_lock+21}
> > > [ 42.131032] <ffffffff8025fd89>{schedule+236}
> > > [ 42.136195] <ffffffff8026078f>{rt_lock_slowlock+351}
> > > [ 42.142086] <ffffffff8026117d>{__lock_text_start+13}
> > > [ 42.147966] <ffffffff8029ae98>{atomic_dec_and_spin_lock+21}
> > > [ 42.154476] <ffffffff8020c4e9>{dput+57}
> > > [ 42.159194] <ffffffff802093f3>{__link_path_walk+1710}
> > > [ 42.165166] <ffffffff802617ad>{_raw_spin_unlock+46}
> > > [ 42.170961] <ffffffff8020db81>{link_path_walk+103}
> > > [ 42.176672] <ffffffff8020be5a>{do_path_lookup+644}
> > > [ 42.182379] <ffffffff80223829>{__user_walk_fd+63}
> > > [ 42.187994] <ffffffff8023fce4>{vfs_lstat_fd+33}
> > > [ 42.193434] <ffffffff8022b3e4>{sys_newlstat+34}
> > > [ 42.198871] <ffffffff8025ce3d>{error_exit+0}
> > > [ 42.204040] <ffffffff8025bf22>{system_call+126}
> >
> > This back trace is definitely ugly. Do you get this all the time? And
> > if so, could you compile in frame pointers and try again. (I'll dig
> > through this in the mean time.)
>
> Not sure, I'm getting hard reboots as well from what looks like more
> atomic scheduling violations. I'll tweek my kernel config to be more
> friendly about these things. It looked like it was in the rtmutex code,
> which is why I CCed you.
>
> Any other configuration suggestions ?
It's already compiling with frame pointers. Unfortunately, this is about
as good it gets for a stack trace unless you've got another suggestion.
bill
next prev parent reply other threads:[~2006-08-02 2:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-02 1:18 2.6.17-rt8 crash amd64 Bill Huey
2006-08-02 1:31 ` Steven Rostedt
2006-08-02 2:19 ` Bill Huey
2006-08-02 2:25 ` Bill Huey [this message]
2006-08-02 7:13 ` Bill Huey
2006-08-02 17:16 ` Daniel Walker
2006-08-02 17:35 ` Bill Huey
2006-08-02 19:58 ` Bill Huey
2006-08-03 1:20 ` Mark Knecht
2006-08-03 1:41 ` Bill Huey
2006-08-03 1:56 ` Mark Knecht
2006-08-03 2:07 ` Mark Knecht
2006-08-03 2:34 ` Bill Huey
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=20060802022539.GA26799@gnuppy.monkey.org \
--to=billh@gnuppy.monkey.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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