Re: NMI lockup, 2.6.26 release

[Jarek Poplawski <jarkao2@gmail.com>]

On Thu, Jul 24, 2008 at 05:56:43PM +0300, denys@visp.net.lb wrote:
> Nothing yet. Still waiting, in 6 hours i will have "peak time".
> But yesterday with same settings(without patch) it crashed 3 times.

OK, so let's better wait to be sure of something here.

Jarek P.

(Btw., could try in the meantime to do something to shorten your lines?
It's not the most popular format on kernel lists...) 

> It is Core2Duo E6750 CPU, clocksource is TSC.
> TSC synchronization is always passed. HPET is available, so in case... i can try it too.
> It was crashing with nmi_watchdog=1(at least it brings crash message) and without it (hard lockup).
> Fishy point is ifb, but i have few hundreds of NAS servers with ifb + htb 
> (but sure not 300-400 Mbps like on this host) and i check weekly log on all of them - none of them crashed.
> 
> So it is or hardware specific (but it is crashing always in same point), 
> even maybe memory corruption, it is not a server-grade equipment, but it crashes always in same place, same way.
> I have running MCE, so if there is thermal events - it must catch it.
> But sure there is large list of errata for this hardware :-)
> 
> 
> On Thursday 24 July 2008, denys@visp.net.lb wrote:
> > I dont have any problem to restart :-)
> > Build system and restart (over kexec) is automated..
> > Rebooting now.
> 
>