I've noticed a similar problem to this as well, and it only seems to happen when I'm using the 2.6.24 kernel. BUG: soft lockup - CPU#1 stuck for 11s! [net.agent:2138] BUG: soft lockup - CPU#0 stuck for 11s! [mount:2115] BUG: soft lockup - CPU#1 stuck for 11s! [net.agent:2138] BUG: soft lockup - CPU#0 stuck for 11s! [mount:2115] BUG: soft lockup - CPU#1 stuck for 11s! [cat:2138] BUG: soft lockup - CPU#0 stuck for 11s! [mount:2115] BUG: soft lockup - CPU#1 stuck for 11s! [cat:2138] BUG: soft lockup - CPU#0 stuck for 11s! [mount:2115] BUG: soft lockup - CPU#1 stuck for 11s! [cat:2138] BUG: soft lockup - CPU#0 stuck for 11s! [mount:2115] BUG: soft lockup - CPU#1 stuck for 11s! [cat:2138] BUG: soft lockup - CPU#0 stuck for 11s! [mount:2115] BUG: soft lockup - CPU#1 stuck for 11s! [cat:2138] BUG: soft lockup - CPU#0 stuck for 11s! [mount:2115] [and a few times previous to that before the logs started] I've attached my dmesg from a boot of this kernel, as well as the output of lshal. It actually stopped me from booting into the new kernel until today, when I disabled the bootsplash and noticed that the computer hadn't locked up completely and was just taking much longer to boot than for the 2.6.22 kernel. I'm wondering if it may have something to do with the 'failed opcode' messages for my primary hard drive (80.0 GB, model 'WDC WD800JD-75MS', came with my Dell OPTIPLEX GX620), but that's just because there seems to be many of those messages in the log. I'll have a go at doing the memtest and see if anything comes of it. David
Attachment:
cpu_lockup_2.6.24-1.dmesg.log.gz
Description: GNU Zip compressed data
Attachment:
lshal_dump.txt.gz
Description: GNU Zip compressed data