From: Bret Towe <magnade@gmail.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Jesper Juhl <jesper.juhl@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: nfs4 client bug
Date: Thu, 8 Sep 2005 23:55:24 -0700 [thread overview]
Message-ID: <dda83e780509082355d28a8ef@mail.gmail.com> (raw)
In-Reply-To: <20050906181327.GE10632@fieldses.org>
On 9/6/05, J. Bruce Fields <bfields@fieldses.org> wrote:
> On Mon, Sep 05, 2005 at 08:40:53PM -0700, Bret Towe wrote:
> > Pid: 14169, comm: xmms Tainted: G M 2.6.13
>
> Hm, can someone explain what that means? A proprietary module was
> loaded then unloaded, maybe?
>
> You may also want to retest with
>
> http://www.citi.umich.edu/projects/nfsv4/linux/kernel-patches/2.6.13-1/linux-2.6.13-001-NFS_ALL_MODIFIED.dif
>
> applied, to make sure there isn't a patch in Trond's series that already
> fixes the bug.
>
> --b.
>
ive been running this since i got the url and so far i havent hit it
ive also been a bit busy so i havent been able to make sure its good
this weekend i should be able to test it and make sure its solved
next prev parent reply other threads:[~2005-09-09 6:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-04 0:15 nfs4 client bug Bret Towe
2005-09-04 3:05 ` Bret Towe
2005-09-04 10:35 ` Francois Romieu
2005-09-04 19:44 ` Bret Towe
2005-09-04 20:51 ` Bret Towe
2005-09-04 21:52 ` J. Bruce Fields
2005-09-05 3:08 ` Bret Towe
2005-09-05 3:18 ` J. Bruce Fields
2005-09-05 20:44 ` Bret Towe
2005-09-05 20:48 ` Jesper Juhl
2005-09-06 3:40 ` Bret Towe
2005-09-06 18:13 ` J. Bruce Fields
2005-09-06 18:21 ` Randy.Dunlap
2005-09-06 18:30 ` J. Bruce Fields
2005-09-06 18:40 ` Randy.Dunlap
2005-09-06 18:53 ` Valdis.Kletnieks
2005-09-09 4:56 ` [PATCH] Doc: update oops-tracing.txt (Tainted flags) Randy.Dunlap
2005-09-09 6:55 ` Bret Towe [this message]
2005-09-12 18:27 ` nfs4 client bug Bret Towe
2005-09-12 18:29 ` J. Bruce Fields
-- strict thread matches above, loose matches on Subject: below --
2005-09-05 16:24 Andreas Sundstrom
2005-09-06 5:10 Andreas Sundstrom
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=dda83e780509082355d28a8ef@mail.gmail.com \
--to=magnade@gmail.com \
--cc=bfields@fieldses.org \
--cc=jesper.juhl@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox