lkml.org 
[lkml]   [2005]   [May]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] check nmi watchdog is broken
Dave Jones writes:
> My EM64T Dell Precision 470 seems to have problems both before
> and after this change, though the behaviour changes.
>
> With -rc3..
> testing NMI watchdog ... CPU#1: NMI appears to be stuck (0)!
>
> With -rc4...
> Testing NMI watchdog ... CPU#4: NMI appears to be stuck (0)!
>
> The CPU #'s are consistent across reboots (Ie, they're always the same).
> Though the rc4 behaviour seems odd, as my CPUs are numbered 0-3.

There is known breakage in x86-64's nmi watchdog recently.
One of the problems is that the checking code inspects
all possible CPU numbers [0..NR_CPUS[ and not just the
ones actually present, which leads to false failure reports.

> Bill (Cc'd) also reports that with -rc4, he sees around
> a 10 second delay when it does that 'Testing NMI watchdog'
> message.

And that's another of the known x86-64 breakages.

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

\
 
 \ /
  Last update: 2005-05-11 13:37    [W:0.038 / U:9.080 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site