On Tue, 2011-08-23 at 16:17 +0200, Sandro Tosi wrote: > Package: linux-2.6 > Version: 2.6.32-35 > Severity: important > > Hello, > we've had several server-class machine (G6 and G7 HP Proliant blades) affected > by the kernel bug mentioned in the subject. > > On the console we can see several several instances of the message: > > BUG: soft lockup - CPU#1 stuck for 61s! [kswapd0:188] > > and then the machine is freezed and need a hard reset. > > I've cut&pasted what's left from the kern.log (remotely logged on another > machine) since I don't have access anymore to those files (plus a bit of > anonymization about the network :)). > > It's an high priority for us to get it fixed so we can provide all the help you > might need: just ask about it. > > I've googled a bit about the problem and found these references: > > http://kerneltrap.org/mailarchive/linux-kernel/2010/11/16/4646082/thread > https://bugzilla.redhat.com/show_bug.cgi?id=649694 [...] The error message you are seeing is not at all specific, so we should not assume it has anything to do with the Red Hat bug report. Unfortunately your log shows almost no useful information; the call traces have been lost. The only function that is mentioned in your log is find_get_pages(), which is not present in any of the call traces in the Red Hat bug report. It may be that serial logging will be more reliable; could you enable a serial console and try to capture the error log on another system? Ben.
Attachment:
signature.asc
Description: This is a digitally signed message part