OnStream DI30: undescriptive message: CoD != 0 in idescsi_pc_intr
OnStream Di30 (using ide-scsi and osst drivers), when reading or writing I regularly get these kernel messages:
<3>ide-scsi: CoD != 0 in idescsi_pc_intr
Let's assume flaky hardware; nothing we can hold the kernel to blame for (which is 2.6.19.1) -- it's a good thing it's calling our attention. There's no data corruption, btw.
However, said message is quite useless because undescriptive and too terse.
bjd
Quoted 11 lines · On Sun, 21 Jan 2007 03:14:33 +0100 Bauke Jan Douma wrote:
OnStream Di30 (using ide-scsi and osst drivers), when reading or writing I regularly get these kernel messages:
<3>ide-scsi: CoD != 0 in
idescsi_pc_intrLet's assume flaky hardware; nothing we can hold the kernel to blame for (which is 2.6.19.1) -- it's a good thing it's calling our attention. There's no data corruption, btw.
However, said message is quite useless because undescriptive and too terse.
Not sure that this helps much.
---
From: Randy Dunlap <[email protected]>
Expand on a terse ide-scsi message.
Something is confused.
--- drivers/scsi/ide-scsi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/scsi/ide-scsi.c +1 -1
@@ -528,7 +528,7 @@ static ide_startstop_t idescsi_pc_intr ( ireason.all =HWIF (drive)->INB (IDE_IREASON_REG );if (ireason.b.cod) { -printk (KERN_ERR "ide-scsi: CoD != 0 in idescsi_pc_intr\n" ); +printk (KERN_ERR "ide-scsi: CoD(Command/Data flag) != 0(Data) in idescsi_pc_intr\n" );return ide_do_reset (drive); }if (ireason.b.io) {