From: Bauke Jan Douma <bjdouma@xs4all.nl>
To: linux-kernel@vger.kernel.org, osst@riede.org,
osst-users@lists.sourceforge.net
Subject: OnStream DI30: undescriptive message: CoD != 0 in idescsi_pc_intr
Date: Sun, 21 Jan 2007 03:14:33 +0100 [thread overview]
Message-ID: <45B2CC89.1020305@xs4all.nl> (raw)
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
next reply other threads:[~2007-01-21 2:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-21 2:14 Bauke Jan Douma [this message]
2007-01-22 0:37 ` OnStream DI30: undescriptive message: CoD != 0 in idescsi_pc_intr Randy Dunlap
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=45B2CC89.1020305@xs4all.nl \
--to=bjdouma@xs4all.nl \
--cc=linux-kernel@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