Re: ide-scsi bug hard locks machine
Alan Cox (alan@lxorguk.ukuu.org.uk)
13 Jan 2003 15:02:53 +0000
On Mon, 2003-01-13 at 03:07, Jason Thomas wrote:
> ide-scsi: abort called for 2
> bad: scheduling while atomic!
> Call Trace: [<c0116941>] [<c0109b76>] [<c01169b0>] [<c011a5db>] [<c0109d8c>] [<c0263100>] [<c0262730>] [<c026848c>] [<c0268390>] [<c0261e63>] [<c0261cc0>] [<c0261c80>] [<c026225d>] [<c02622d7>] [<c0262b65>] [<c0109d97>] [<c0262c89>] [<c0262bb0>] [<c0108be9>]
> hde: lost interrupt
> ide-scsi: CoD != 0 in idescsi_pc_intr
> hde: ATAPI reset complete
> hde: irq timeout: status=0xc0 { Busy }
> hde: ATAPI reset complete
> hde: irq timeout: status=0xc0 { Busy }
> hde: ATAPI reset complete
> hde: irq timeout: status=0xc0 { Busy }
> ide-scsi: reset called for 2
Someone broke ide-scsi in 2.5. I've not had time to investigate why yet. If you
need ide-scsi use 2.4.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/