From: "Bret Towe" <magnade@gmail.com>
To: "Florin Iucha" <florin@iucha.net>
Cc: "Trond Myklebust" <trond.myklebust@fys.uio.no>,
"Jiri Kosina" <jikos@jikos.cz>,
linux-usb-devel@lists.sourceforge.net,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
Subject: Re: NFS woes again Was: [linux-usb-devel] USB-related oops in sysfs with linux v2.6.23-rc3-50-g28e8351
Date: Thu, 23 Aug 2007 10:14:38 -0700 [thread overview]
Message-ID: <dda83e780708231014x66093dafj83263a2a1c8203bb@mail.gmail.com> (raw)
In-Reply-To: <20070823125210.GQ10422@iucha.net>
On 8/23/07, Florin Iucha <florin@iucha.net> wrote:
> 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@zeus $ git bisect bad
> Bisecting: 5 revisions left to test after this
> florin@zeus $ 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
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFGzYL6ND0rFCN2b1sRAqMlAJ9hvBi5oVBeRYZfNwXDG3EmJNgQ4ACbB4V8
> koRJC/8+P1x600SSS51NvZE=
> =+Adv
> -----END PGP SIGNATURE-----
this sounds alot like the post i did yesterday titled 'nfs4 hang regression'
i tracked it down to commit 3d39c691ff486142dd9aaeac12f553f4476b7a6
next prev parent reply other threads:[~2007-08-23 17:14 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 13:31 Florin Iucha
2007-08-15 14:38 ` [linux-usb-devel] " Alan Stern
2007-08-15 14:50 ` Florin Iucha
2007-08-15 15:24 ` Alan Stern
2007-08-15 14:54 ` Tejun Heo
2007-08-15 15:21 ` Cornelia Huck
2007-08-15 15:30 ` Tejun Heo
2007-08-15 15:33 ` Alan Stern
2007-08-15 14:49 ` Jiri Kosina
2007-08-15 14:53 ` Florin Iucha
2007-08-15 14:58 ` Jiri Kosina
2007-08-21 11:51 ` Florin Iucha
2007-08-21 12:04 ` Jiri Kosina
2007-08-21 12:28 ` Florin Iucha
2007-08-21 14:51 ` Alan Stern
2007-08-21 12:06 ` Oliver Neukum
2007-08-21 12:09 ` Jiri Kosina
2007-08-21 12:19 ` Oliver Neukum
2007-08-21 12:57 ` Florin Iucha
2007-08-21 13:05 ` Jiri Kosina
2007-08-21 13:17 ` Florin Iucha
2007-08-21 13:27 ` Florin Iucha
2007-08-21 13:42 ` Jiri Kosina
2007-08-22 13:22 ` Florin Iucha
2007-08-23 12:52 ` NFS woes again Was: " Florin Iucha
2007-08-23 17:14 ` Bret Towe [this message]
2007-08-23 17:36 ` Florin Iucha
2007-08-27 13:17 ` Trond Myklebust
2007-08-28 1:19 ` Bret Towe
2007-08-28 1:35 ` NFS woes again Florin Iucha
2007-08-28 13:28 ` Trond Myklebust
2007-08-29 3:27 ` Florin Iucha
2007-08-29 5:52 ` Bret Towe
2007-08-30 22:18 ` Bret Towe
2007-08-30 23:14 ` Florin Iucha
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=dda83e780708231014x66093dafj83263a2a1c8203bb@mail.gmail.com \
--to=magnade@gmail.com \
--cc=florin@iucha.net \
--cc=jikos@jikos.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=trond.myklebust@fys.uio.no \
/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
Powered by JetHome