public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Florin Iucha <florin@iucha.net>
To: Bret Towe <magnade@gmail.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
	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 12:36:37 -0500	[thread overview]
Message-ID: <20070823173637.GS10422@iucha.net> (raw)
In-Reply-To: <dda83e780708231014x66093dafj83263a2a1c8203bb@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 573 bytes --]

On Thu, Aug 23, 2007 at 10:14:38AM -0700, Bret Towe wrote:
> this sounds alot like the post i did yesterday titled 'nfs4 hang regression'
> i tracked it down to commit 3d39c691ff486142dd9aaeac12f553f4476b7a6

Yes, it certainly does -- all the symptoms match!

I'm not [alone in] seeing dead keyboards!

Now, if only somebody could clarify to me the connection between
the bad NFS4 shooting the keyboard but not the mouse, that would
be wonderful.

florin

-- 
Bruce Schneier expects the Spanish Inquisition.
      http://geekz.co.uk/schneierfacts/fact/163

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-08-23 17:36 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-15 13:31 USB-related oops in sysfs with linux v2.6.23-rc3-50-g28e8351 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
2007-08-23 17:36                         ` Florin Iucha [this message]
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=20070823173637.GS10422@iucha.net \
    --to=florin@iucha.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=magnade@gmail.com \
    --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