From: Bret Towe <magnade@gmail.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: nfs4 client bug
Date: Sun, 4 Sep 2005 12:44:05 -0700 [thread overview]
Message-ID: <dda83e78050904124454fc675a@mail.gmail.com> (raw)
In-Reply-To: <20050904103523.GA5613@electric-eye.fr.zoreil.com>
On 9/4/05, Francois Romieu <romieu@fr.zoreil.com> wrote:
> Bret Towe <magnade@gmail.com> :
> [...]
> > after moving some files on the server to a new location then trying to
> > add the files
> > to xmms playlist i found the following in dmesg after xmms froze
> > wonder how many more items i can find...
>
> The system includes some binary only stuff. Please contact your vendor
> or provide the traces for a configuration wherein the relevant module
> was not loaded after boot. It may make sense to get in touch with
> nfs@lists.sourceforge.net then.
the 'binary only stuff' is ati-drivers kernel module and it crashs
with or without it
ill provide a 'untainted' trace as soon as i can repeat the bug again
> --
> Ueimor
>
next prev parent reply other threads:[~2005-09-04 19:44 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 [this message]
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 ` nfs4 client bug Bret Towe
2005-09-12 18:27 ` 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=dda83e78050904124454fc675a@mail.gmail.com \
--to=magnade@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
/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