On Fri, 2004-09-24 at 16:13, jludwig wrote: snip > > c0381a8c 00000040 00000000 c01f908d 00000040 00000000 00000000 > > c7cdced8 > > Call Trace: > > [<c0203e75>] cdrom_start_read_continuation+0x0/0xb0 > > [<c02038dc>] cdrom_start_packet_command+0x110/0x134 > > [<c0203780>] cdrom_timer_expiry+0x0/0x4c > > [<c0204cf7>] ide_do_rw_cdrom+0xe3/0x14f > > [<c01f908d>] start_request+0x197/0x1b8 > > [<c01f9308>] ide_do_request+0x23f/0x27a > > [<c01f955b>] ide_timer_expiry+0x151/0x15d > > [<c01f940a>] ide_timer_expiry+0x0/0x15d > > [<c011f4fb>] run_timer_softirq+0x10b/0x12a > > [<c011c25d>] __do_softirq+0x35/0x73 > > [<c0107708>] do_softirq+0x46/0x4d > > ======================== > > [<c0107197>] do_IRQ+0x15d/0x169 > This is the secondary hard drive controller interrupt. > > [<c0287338>] common_interrupt+0x18/0x20 > > [<c0104018>] default_idle+0x0/0x26 > > [<c010403b>] default_idle+0x23/0x26 > > [<c010408a>] cpu_idle+0x1d/0x32 > > [<c03205fe>] start_kernel+0x174/0x176 > > > > Code: 0f 0b eb 03 c1 e4 2a c0 89 0a 8b 44 24 18 89 82 e4 00 00 00 > > <0>Kernel panic: Fatal exception in interrupt > > In interrupt handler - not syncing > I have seen something like with older CDROM drives. > -- > jludwig <wralphie@xxxxxxxxxxx> Oh yes, looking into it --- from my notes. Do you have the CDROM as master and the only device on the secondary channel? I have seen this when the CDROM drive and a hard drive conflict for some reason on a flakey BIOS, usually with the CDROM in the slave position. -- jludwig <wralphie@xxxxxxxxxxx>
