From: john stultz <johnstul@us.ibm.com>
To: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
rt-users <linux-rt-users@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Nick Piggin <npiggin@suse.de>
Subject: Re: 2.6.33.5 rt23: machine lockup (nfs/autofs related?)
Date: Mon, 12 Jul 2010 18:40:31 -0700 [thread overview]
Message-ID: <1278985231.2404.60.camel@localhost.localdomain> (raw)
In-Reply-To: <1278983426.6489.57.camel@localhost.localdomain>
On Mon, 2010-07-12 at 18:10 -0700, Fernando Lopez-Lezcano wrote:
> On Mon, 2010-07-12 at 16:53 -0700, john stultz wrote:
> >
> > Hrm. Ok.. I think the line 2100 above gives us a hint: (aparent == anon)
> > So if that were the case, we would have already locked aparent and that
> > would explain the blowup.
> >
> > How does it do with the following change?
>
> Ok, you are on to something. The machine did not crash hard!
> But the serial console printed this:
Sigh. Its never easy, is it? :)
> --------
> BUG: unable to handle kernel NULL pointer dereference at 0000008c
> IP: [<c045e50a>] rt_spin_lock_fastunlock.clone.2+0x6/0x3e
...
> Pid: 2855, comm: nautilus Not tainted
> 2.6.33.6-147.rt23.3.fc12.ccrma.i686.rt #3 P5K/EPU/P5K/EPU
> EIP: 0060:[<c045e50a>] EFLAGS: 00210246 CPU: 0
> EIP is at rt_spin_lock_fastunlock.clone.2+0x6/0x3e
> EAX: 00000078 EBX: ef45393c ECX: 00000000 EDX: 00000078
> ESI: ef716edc EDI: 00000000 EBP: f1977c8c ESP: f1977c88
> DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 preempt:00000000
> Process nautilus (pid: 2855, ti=f1976000 task=f2347130 task.ti=f1976000)
> Stack:
> ef45393c f1977c94 c0781206 f1977cc8 c04d842e 00000000 ef703e54 faadd5bc
> <0> f1977cdc 126bc87a ef703ddc 00000000 ef45393c ef716edc ef6f5494
> faafdc6c
> <0> f1977df8 faad9041 c3604b5c faafdc6c ef452bfc 00007e7f f5eb41e8
> 00000007
> Call Trace:
> [<c0781206>] ? rt_spin_unlock+0x8/0xa
> [<c04d842e>] ? d_materialise_unique+0x210/0x2aa
Can you gdb list *0xc04d842e ?
Thanks again for all the testing here! Its really appreciated!
-john
next prev parent reply other threads:[~2010-07-13 1:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 17:19 2.6.33.5 rt23: machine lockup (nfs/autofs related?) Fernando Lopez-Lezcano
2010-07-08 22:33 ` john stultz
2010-07-08 22:44 ` Fernando Lopez-Lezcano
2010-07-08 23:00 ` john stultz
2010-07-09 19:02 ` Fernando Lopez-Lezcano
2010-07-09 19:13 ` Fernando Lopez-Lezcano
2010-07-09 19:54 ` john stultz
2010-07-09 22:13 ` Fernando Lopez-Lezcano
2010-07-09 22:31 ` john stultz
2010-07-09 23:07 ` Fernando Lopez-Lezcano
2010-07-09 23:24 ` Fernando Lopez-Lezcano
2010-07-09 22:57 ` john stultz
2010-07-09 23:13 ` Fernando Lopez-Lezcano
2010-07-12 23:37 ` Fernando Lopez-Lezcano
2010-07-12 23:53 ` john stultz
2010-07-13 1:10 ` Fernando Lopez-Lezcano
2010-07-13 1:40 ` john stultz [this message]
2010-07-13 3:06 ` Fernando Lopez-Lezcano
2010-07-14 21:32 ` Fernando Lopez-Lezcano
2010-07-14 21:36 ` john stultz
2010-07-14 22:02 ` Fernando Lopez-Lezcano
[not found] <f4357-SJ-15@gated-at.bofh.it>
[not found] ` <f47V8-84x-17@gated-at.bofh.it>
[not found] ` <f484O-8hq-5@gated-at.bofh.it>
[not found] ` <f48o9-rG-1@gated-at.bofh.it>
2010-07-10 6:32 ` A D
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=1278985231.2404.60.camel@localhost.localdomain \
--to=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=nando@ccrma.Stanford.EDU \
--cc=npiggin@suse.de \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.