mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Frank <mflt1@micrologica.com.hk>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, Joshua Kwan <joshk@triplehelix.org>,
	"Zephaniah E. Hull" <warp@mercury.d2dc.net>
Subject: Re: 2.6.0-test2-mm3-1: Badness in class_dev_release followed by 5 NFS server hangs
Date: Thu, 7 Aug 2003 00:26:34 +0800	[thread overview]
Message-ID: <200308070026.34483.mflt1@micrologica.com.hk> (raw)
In-Reply-To: <200308040953.42110.mflt1@micrologica.com.hk>

On Monday 04 August 2003 11:10, Michael Frank wrote:
> On Monday 04 August 2003 04:56, Andrew Morton wrote:
> > All netdevices will generate this warning on unregistration.  The net
> > guys are cooking up a fix, but it is not available yet.
>
> OK, What about the NFS hangs there are more now, also some short in
> duration
>
> Aug  4 04:22:02 mhfl4 kernel: nfs: server mhfl2 not responding, still
> trying Aug  4 04:22:02 mhfl4 kernel: nfs: server mhfl2 OK
> Aug  4 04:23:59 mhfl4 kernel: nfs: server mhfl2 not responding, still
> trying Aug  4 04:23:59 mhfl4 kernel: nfs: server mhfl2 OK
>

Running -mm4 for 2 days, spurious NFS server hangs seem to have 
subsided in -mm4

Regards
Michael


-- 
Powered by linux-2.6-test2-mm4. Compiled with gcc-2.95-3 - mature and rock solid

2.4/2.6 kernel testing: ACPI PCI interrupt routing, PCI IRQ sharing, swsusp
2.6 kernel testing:     PCMCIA yenta_socket, Suspend to RAM with ACPI S1-S3

More info on swsusp: http://sourceforge.net/projects/swsusp/


      parent reply	other threads:[~2003-08-06 16:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-03 20:33 Michael Frank
2003-08-03 20:56 ` Andrew Morton
2003-08-04  3:10   ` Michael Frank
2003-08-04  4:47     ` Joshua Kwan
2003-08-04  6:42       ` Zephaniah E. Hull
2003-08-06 16:26     ` Michael Frank [this message]

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=200308070026.34483.mflt1@micrologica.com.hk \
    --to=mflt1@micrologica.com.hk \
    --cc=akpm@osdl.org \
    --cc=joshk@triplehelix.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=warp@mercury.d2dc.net \
    /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

all inboxes | Powered by JetHome®