From: Randy Dunlap <randy.dunlap@oracle.com>
To: bjdouma@xs4all.nl
Cc: linux-kernel@vger.kernel.org, osst@riede.org,
osst-users@lists.sourceforge.net,
scsi <linux-scsi@vger.kernel.org>
Subject: Re: OnStream DI30: undescriptive message: CoD != 0 in idescsi_pc_intr
Date: Sun, 21 Jan 2007 16:37:19 -0800 [thread overview]
Message-ID: <20070121163719.6c4defd8.randy.dunlap@oracle.com> (raw)
In-Reply-To: <45B2CC89.1020305@xs4all.nl>
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_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.
Not sure that this helps much.
---
From: Randy Dunlap <randy.dunlap@oracle.com>
Expand on a terse ide-scsi message.
Something is confused.
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
drivers/scsi/ide-scsi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-2619-work.orig/drivers/scsi/ide-scsi.c
+++ linux-2619-work/drivers/scsi/ide-scsi.c
@@ -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) {
prev parent reply other threads:[~2007-01-22 0:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-21 2:14 Bauke Jan Douma
2007-01-22 0:37 ` Randy Dunlap [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070121163719.6c4defd8.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=bjdouma@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=osst-users@lists.sourceforge.net \
--cc=osst@riede.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome