Re: nfs4 client bug

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 6 Sep 2005, J. Bruce Fields wrote:

> 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?

Not that I can see.

There should be a logged MCE (machine check exception) in there
somewhere AFAICT.

> > (/we needs to update Documentation/oops-tracing.txt)
>
> Oops, thanks, I overlooked that!
>
> --b.

-- 
~Randy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]
  Powered by Linux