[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPed3OE0YSedYVfQvEkzdqpeaQWDNdiGHBSKYR1PcqVsHE26VA@mail.gmail.com>
Date: Wed, 26 Oct 2011 20:21:53 +0200
From: Ruben Kerkhof <ruben@...enkerkhof.com>
To: john stultz <johnstul@...ibm.com>
Cc: Greg KH <greg@...ah.com>, linux-kernel@...r.kernel.org,
seto.hidetoshi@...fujitsu.com,
Peter Zijlstra <peterz@...radead.org>,
MINOURA Makoto <minoura@...inux.co.jp>,
Ingo Molnar <mingo@...e.hu>, stable@...nel.org,
Hervé Commowick <hcommowick@...sec.fr>,
Rand@...per.es, Andrew Morton <akpm@...ux-foundation.org>,
Willy Tarreau <w@....eu>,
Faidon Liambotis <paravoid@...ian.org>
Subject: Re: [stable] 2.6.32.21 - uptime related crashes?
On Wed, Oct 26, 2011 at 00:44, john stultz <johnstul@...ibm.com> wrote:
> On Sun, 2011-10-23 at 20:31 +0200, Ruben Kerkhof wrote:
>> I just had two crashes on two different machines, both with an uptime
>> of 208 days.
>> Both were 5520's running 2.6.34.8, but with a CONFIG_HZ of 1000
>>
>> 2011-10-23T16:49:18.618029+02:00 phy001 kernel: BUG: soft lockup -
>> CPU#0 stuck for 17163091968s! [qemu-kvm:16949]
>
> So were these actual crashes, or just softlockup false positives?
Just softlockups, I haven't seen the divide_by_zero crash.
Thanks,
Ruben
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists