[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070823125210.GQ10422@iucha.net>
Date: Thu, 23 Aug 2007 07:52:10 -0500
From: Florin Iucha <florin@...ha.net>
To: Trond Myklebust <trond.myklebust@....uio.no>
Cc: Jiri Kosina <jikos@...os.cz>,
linux-usb-devel@...ts.sourceforge.net,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Michal Piotrowski <michal.k.k.piotrowski@...il.com>
Subject: NFS woes again Was: [linux-usb-devel] USB-related oops in sysfs
with linux v2.6.23-rc3-50-g28e8351
Trond,
Fess up... I'm closing in:
http://iucha.net/2.6.23-rc3/2.6.23-rc-bisect.png
[Dropping Jiri and linux-usb-devel from future postings. You are
included now just for communicating the conclusion of this thread.]
On Wed, Aug 22, 2007 at 08:22:00AM -0500, Florin Iucha wrote:
> On Tue, Aug 21, 2007 at 03:42:26PM +0200, Jiri Kosina wrote:
> > On Tue, 21 Aug 2007, Florin Iucha wrote:
> >
> > > There is another interesting angle to this: in the past, every time I
> > > had keyboard problems, it used to be caused by the VFS and/or NFS...
> > > after much wrangling, a bunch of bugs were fixed (Hi Trond, Peter,
> > > Alan!). Now, after the keyboard "locked up", I used the mouse to close
> > > the gnome session, then I logged-in remotely to reboot. The reboot
> > > process locked up and I need to use the reset button! The second time
> > > the keyboard "locked up" I listed my processes, and I noticed that I had
> > > a couple of bash processes and a ssh process in "D" state. Something is
> > > fishy again in the VFS ;)
> >
> > Yes, there were some NFS updates in between -rc2 and
> > 28e8351ac22de25034e048c680014ad824323c65. I'd be now even more curious
> > what are you going to find by bisect, please let us know.
> >
> > I added Trond to CC, full thread to be found at
> > http://lkml.org/lkml/2007/8/21/151 for reference.
> >
> > Florin, it also might be useful to capture the states of stuck processess
> > via alt-sysrq-T (or better by echo t > /proc/sysrq-trigger), so that we
> > know better where are they stuck.
>
> This morning it took a bit longer to hang, but it happened. The
> backtraces are at http://iucha.net/2.6.23-rc3/backtraces.gz .
>
> I'll try a bisect session this weekend.
florin@...s $ git bisect bad
Bisecting: 5 revisions left to test after this
florin@...s $ git bisect log
git-bisect start
# good: [d4ac2477fad0f2680e84ec12e387ce67682c5c13] Linux 2.6.23-rc2
git-bisect good d4ac2477fad0f2680e84ec12e387ce67682c5c13
# bad: [28e8351ac22de25034e048c680014ad824323c65] Merge git://git.kernel.org/pub/scm/linux/kernel/git/steve/gfs2-2.6-fixes
git-bisect bad 28e8351ac22de25034e048c680014ad824323c65
# bad: [8f2ea1fd3f97ab7a809e939b5b9005a16f862439] [POWERPC] Fix initialization and usage of dma_mask
git-bisect bad 8f2ea1fd3f97ab7a809e939b5b9005a16f862439
# good: [ff95f3df54609d9d4b9572f8a67d09922a645043] sched: remove the 'u64 now' parameter from pick_next_task()
git-bisect good ff95f3df54609d9d4b9572f8a67d09922a645043
# good: [be12014dd7750648fde33e1e45cac24dc9a8be6d] Merge git://git.kernel.org/pub/scm/linux/kernel/git/mingo/linux-2.6-sched
git-bisect good be12014dd7750648fde33e1e45cac24dc9a8be6d
# good: [6a0ed91e361a93ee1efb4c20c4967024ed2a8dd7] hexdump: use const notation
git-bisect good 6a0ed91e361a93ee1efb4c20c4967024ed2a8dd7
# bad: [6adb31c90c47262c8a25bf5097de9b3426caf3ae] remove dubious legal statment from uio-howto
git-bisect bad 6adb31c90c47262c8a25bf5097de9b3426caf3ae
florin
--
Bruce Schneier expects the Spanish Inquisition.
http://geekz.co.uk/schneierfacts/fact/163
Download attachment "signature.asc" of type "application/pgp-signature" (190 bytes)
Powered by blists - more mailing lists