2.6.19: BUG: soft lockup detected on CPU#0!

Hi,

After a few days uptime on a 2.6.19 kernel, I see this:

http://devzero.co.uk/~alistair/2.6.19-softlockup.jpg

At which point magic sysrq doesn't work and the machine requires a hard 
reboot. Is there anything that can be done to produce a more verbose message 
when such a soft lockup occurs?

-- 
Cheers,
Alistair.

Final year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Prev by Date: Re: .version keeps being updated
• Next by Date: Re: [REGRESSION] 2.6.19/2.6.20-rc3 buffered write slowdown
• Previous by thread: [RFC PATCH 3/3] blk_end_request: caller change
• Next by thread: [PATCH] Revert nmi_known_cpu() check during boot option parsing
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]