Re: nfs4 client bug

[Valdis.Kletnieks@vt.edu]

On Tue, 06 Sep 2005 14:30:08 EDT, "J. Bruce Fields" said:
> 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 directly - but if the MCE wedged a processor, that could cause the NMI
to fire complaining about a lockup.  You should have a MCE logged someplace.

Attachment: pgp1y3gbbDtd1.pgp
Description: PGP signature