Deadlock detected on CPU #1 (2.3.32-pre3)
Petr Vandrovec Ing. VTEI (VANDROVE@vc.cvut.cz)
Mon, 13 Dec 1999 16:50:12 MET-1
I 'fixed' pre3 patch so that pgd_quick is handled same way as pmd_quick
is (ie. per-cpu thing; I have < 1GB so this probably does not matter
anyway). It worked fine for some time, but then I got error CPU #1
deadlock detected... in (almost) same place as I reported last week,
but with different call trace. Code is looping again in irq_enter() !
io_virt_debug+1/51 (it is probably place where IRQ came)
0xc020dad2 (probably fb_info for putcs; points to .data)
ide_spin_wait_hwgroup+158/291 (probably garbage on stack)
set_cursor+110/127 (probably garbage on stack)
write_chan+0/953 (address of proc...)
I do not see anything wrong with it; except that other CPU probably
holds global_irq_lock indefinitely... Is there some patch which allow
me to get also call trace from non-deadlocked CPU when deadlock occur?
Hardware is dual PIII/450, IDE (18GB UDMA2), AHA1542 (driver not loaded),
2x bttv (bt848+bt878), matroxfb + matroxfb_dh (G400 dualhead), ess-solo1,
tulip 10Mbps, 256MB RAM.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
Please read the FAQ at http://www.tux.org/lkml/