From: David van Hoose <davidvh@cox.net>
To: linux-kernel@vger.kernel.org
Subject: [2.4.21-rc1] Zipdrive messages too much
Date: Wed, 23 Apr 2003 12:02:42 -0500 [thread overview]
Message-ID: <3EA6C732.2060504@cox.net> (raw)
I included ppa and scsi in my kernel since I have a parallel port
zipdrive. Problem I am having is that it keeps scanning the drive for
too much too often. Anytime I mount/unmount, plug/unplug USB and
firewire devices, or at random times, I get the following messages on my
console and in my messages file.
Apr 23 11:41:35 aeon kernel: sda : READ CAPACITY failed.
Apr 23 11:41:35 aeon kernel: sda : status = 1, message = 00, host = 0,
driver = 08
Apr 23 11:41:35 aeon kernel: Current sd00:00: sns = 70 2
Apr 23 11:41:35 aeon kernel: ASC=3a ASCQ= 0
Apr 23 11:41:35 aeon kernel: Raw sense data:0x70 0x00 0x02 0x00 0x00
0x00 0x00 0x11 0x00 0x00 0x00 0x00 0x3a 0x00 0x00 0x00 0x00 0x00 0xff
0xfe 0x01 0x00 0x00 0x00 0x00
Apr 23 11:41:35 aeon kernel: sda : block size assumed to be 512 bytes,
disk size 1GB.
Apr 23 11:41:35 aeon kernel: sda: Write Protect is off
Apr 23 11:41:35 aeon kernel: sda: I/O error: dev 08:00, sector 0
Apr 23 11:41:35 aeon kernel: I/O error: dev 08:00, sector 0
Apr 23 11:41:35 aeon kernel: unable to read partition table
Apr 23 11:41:35 aeon kernel: Device not ready. Make sure there is a
disc in the drive.
This gets really annoying, but I like to use my zipdrive.
Let me know if more information is needed.
Thanks,
David
next reply other threads:[~2003-04-23 16:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 17:02 David van Hoose [this message]
2003-05-06 18:20 ` [2.4.21-rc1] Zipdrive messages too much Bill Davidsen
2003-05-06 18:53 ` David van Hoose
2003-05-06 19:08 ` David van Hoose
[not found] <BKEGKPICNAKILKJKMHCAEENJCKAA.Riley@Williams.Name>
2003-05-06 21:18 ` David van Hoose
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=3EA6C732.2060504@cox.net \
--to=davidvh@cox.net \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.