From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: john stultz <johnstul@us.ibm.com>
Cc: nando@ccrma.Stanford.EDU, 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: Wed, 14 Jul 2010 14:32:09 -0700 [thread overview]
Message-ID: <1279143129.29524.39.camel@localhost.localdomain> (raw)
In-Reply-To: <1278990381.11165.3.camel@localhost.localdomain>
On Mon, 2010-07-12 at 20:06 -0700, Fernando Lopez-Lezcano wrote:
> > > --------
> > > 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 ?
>
> (gdb) list *0xc04d842e
> 0xc04d842e is in d_materialise_unique (fs/dcache.c:2073).
> 2068 out_unalias:
> 2069 d_move_locked(alias, dentry);
> 2070 ret = alias;
> 2071 out_err:
> 2072 spin_unlock(&inode->i_lock);
> 2073 if (m2)
> 2074 mutex_unlock(m2);
> 2075 if (m1)
> 2076 mutex_unlock(m1);
> 2077 return ret;
>
> > Thanks again for all the testing here! Its really appreciated!
I just tried building 2.6.33.6 rt26 (saw it this morning on the site)
and it does not exhibit this problem. Woohoo!
Thanks again!
-- Fernando
next prev parent reply other threads:[~2010-07-14 21:32 UTC|newest]
Thread overview: 21+ 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
2010-07-13 3:06 ` Fernando Lopez-Lezcano
2010-07-14 21:32 ` Fernando Lopez-Lezcano [this message]
2010-07-14 21:36 ` john stultz
2010-07-14 22:02 ` Fernando Lopez-Lezcano
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=1279143129.29524.39.camel@localhost.localdomain \
--to=nando@ccrma.stanford.edu \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).