From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: Bret Towe <magnade@gmail.com>,
Jesper Juhl <jesper.juhl@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: nfs4 client bug
Date: Tue, 6 Sep 2005 14:30:08 -0400 [thread overview]
Message-ID: <20050906183008.GG10632@fieldses.org> (raw)
In-Reply-To: <Pine.LNX.4.50.0509061119380.19596-100000@shark.he.net>
On Tue, Sep 06, 2005 at 11:21:09AM -0700, Randy.Dunlap wrote:
> On Tue, 6 Sep 2005, J. Bruce Fields 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?
>
> 'M' means Machine Check, which sets the Tainted flag.
> So the processor thought that there was some kind of problem.
Does this NMI watchdog event ("NMI Watchdog detected LOCKUP on CPU0CPU
0") set that flag?
> (/we needs to update Documentation/oops-tracing.txt)
Oops, thanks, I overlooked that!
--b.
next prev parent reply other threads:[~2005-09-06 18:30 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 [this message]
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=20050906183008.GG10632@fieldses.org \
--to=bfields@fieldses.org \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=magnade@gmail.com \
--cc=rdunlap@xenotime.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.