From: Dave Jones <davej@redhat.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.17-rc6-mm1
Date: Wed, 21 Jun 2006 02:23:46 -0400 [thread overview]
Message-ID: <20060621062346.GA10637@redhat.com> (raw)
In-Reply-To: <1150825349.2891.219.camel@laptopd505.fenrus.org>
On Tue, Jun 20, 2006 at 07:42:29PM +0200, Arjan van de Ven wrote:
> On Thu, 2006-06-08 at 01:00 -0400, Dave Jones wrote:
> > On Wed, Jun 07, 2006 at 10:47:24AM -0700, Andrew Morton wrote:
> > >
> > > ftp://ftp.kernel.org/pub/linux/kernel/peopleD/akpm/patches/2.6/2.6.17-rc6/2.6.17-rc6-mm1/
> > >
> > > - Many more lockdep updates
> >
> > Needs more.
> >
> > ====================================
> > [ BUG: possible deadlock detected! ]
> > ------------------------------------
> > nfsd/11429 is trying to acquire lock:
> > (&inode->i_mutex){--..}, at: [<c032286a>] mutex_lock+0x21/0x24
> >
> > but task is already holding lock:
> > (&inode->i_mutex){--..}, at: [<c032286a>] mutex_lock+0x21/0x24
> >
> > which could potentially lead to deadlocks!
>
> Does this fix it for you? (it fixes the case for me)
Hmm. This makes things drastically worse for me. Now it hangs during NFS startup.
$ sudo service nfs start
Starting NFS services: [ OK ]
Starting NFS quotas:
and that's all she wrote.
ps axf..
2757 pts/0 S+ 0:00 | \_ /bin/sh /sbin/service nfs start
2760 pts/0 S+ 0:00 | \_ /bin/sh /etc/init.d/nfs start
2771 pts/0 S+ 0:00 | \_ /bin/bash -c ulimit -S -c 0 >/dev/null 2>&1 ; rpc.rquotad
2772 pts/0 S+ 0:00 | \_ rpc.rquotad
If I ssh into the box, and get sysrq-t output, I see..
http://people.redhat.com/davej/nfs
I've kicked off a clean build that I'll leave running overnight, as I'm not
100% sure that was a clean tree I built from. Odd behaviour for a miscompile though.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-06-21 6:24 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-07 17:47 2.6.17-rc6-mm1 Andrew Morton
2006-06-07 18:21 ` 2.6.17-rc6-mm1 Dave Jones
2006-06-07 21:23 ` 2.6.17-rc6-mm1 J.A. Magallón
2006-06-07 22:07 ` 2.6.17-rc6-mm1 Ingo Molnar
2006-06-07 22:36 ` 2.6.17-rc6-mm1 J.A. Magallón
2006-06-07 23:54 ` 2.6.17-rc6-mm1 Stefan Richter
2006-06-08 0:31 ` 2.6.17-rc6-mm1 Chris Wright
2006-06-08 6:30 ` 2.6.17-rc6-mm1 Stefan Richter
2006-06-08 7:26 ` 2.6.17-rc6-mm1 Ingo Molnar
2006-06-07 21:54 ` 2.6.17-rc6-mm1 Rafael J. Wysocki
2006-06-07 22:11 ` 2.6.17-rc6-mm1 Ingo Molnar
2006-06-08 3:19 ` 2.6.17-rc6-mm1 Valdis.Kletnieks
2006-06-08 15:13 ` lockdep wierdness - was 2.6.17-rc6-mm1 Valdis.Kletnieks
2006-06-08 10:06 ` NTFS possible circular locking deadlock (Was: Re: 2.6.17-rc6-mm1) Duncan Sands
2006-06-12 14:35 ` Ingo Molnar
2006-06-08 12:54 ` 2.6.17-rc6-mm1 Rafael J. Wysocki
2006-06-07 22:31 ` 2.6.17-rc6-mm1 J.A. Magallón
2006-06-07 22:40 ` 2.6.17-rc6-mm1 Andrew Morton
2006-06-07 23:23 ` [PATCH] ignore smp_locks section warnings from init/exit code Randy.Dunlap
2006-06-08 0:04 ` Randy.Dunlap
2006-06-08 2:11 ` Jeff Dike
2006-06-08 2:32 ` Randy.Dunlap
2006-06-08 4:21 ` Jeff Dike
2006-06-08 4:29 ` Randy.Dunlap
2006-06-08 15:44 ` Randy.Dunlap
2006-06-08 18:35 ` Sam Ravnborg
2006-06-11 23:25 ` Jeff Dike
2006-06-12 0:17 ` Randy.Dunlap
2006-06-12 2:29 ` Jeff Dike
2006-06-12 2:52 ` Randy.Dunlap
2006-06-08 2:25 ` 2.6.17-rc6-mm1 Andi Kleen
2006-06-08 2:46 ` 2.6.17-rc6-mm1 Randy.Dunlap
2006-06-08 5:43 ` 2.6.17-rc6-mm1 Andi Kleen
2006-06-08 6:46 ` 2.6.17-rc6-mm1 Gerd Hoffmann
2006-06-07 23:14 ` 2.6.17-rc6-mm1 Martin Bligh
2006-06-07 23:55 ` 2.6.17-rc6-mm1 Andrew Morton
2006-06-08 1:09 ` 2.6.17-rc6-mm1 Grant Coady
2006-06-08 5:00 ` 2.6.17-rc6-mm1 Dave Jones
2006-06-20 17:42 ` 2.6.17-rc6-mm1 Arjan van de Ven
2006-06-20 20:24 ` 2.6.17-rc6-mm1 Andrew Morton
2006-06-20 20:38 ` 2.6.17-rc6-mm1 Arjan van de Ven
2006-06-21 6:23 ` Dave Jones [this message]
2006-06-21 8:15 ` 2.6.17-rc6-mm1 Arjan van de Ven
2006-06-21 18:42 ` 2.6.17-rc6-mm1 Dave Jones
-- strict thread matches above, loose matches on Subject: below --
2006-06-07 17:47 2.6.17-rc6-mm1 Andrew Morton
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=20060621062346.GA10637@redhat.com \
--to=davej@redhat.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.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 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.