From: Emre Tezel <emre.tezel@verizon.net>
To: linux-kernel@vger.kernel.org
Subject: ide-floppy problem - 2.4.19-pre10
Date: Sat, 22 Jun 2002 13:25:37 -0400 [thread overview]
Message-ID: <3D14B311.80802@verizon.net> (raw)
Dear Kernel Hackers,
I am running kernel 2.4.19-pre10. I am experiencing a problem with my
internal ATAPI Zip 100 Drive. Currently I am using the ide-floppy
driver. The device is attached to my secondry slave (/dev/hdd). Whenever
I try to do any I/O, my system eventually comes to a full stop. I
managed to extract the following kernel log messages.
Jun 21 01:17:09 hori kernel: ide-scsi: CoD != 0 in idescsi_pc_intr
Jun 21 01:17:09 hori kernel: hdd: ATAPI reset complete
Jun 21 01:17:09 hori kernel: hdd: lost interrupt
Jun 21 01:17:09 hori kernel: ide-scsi: CoD != 0 in idescsi_pc_intr
Jun 21 01:17:09 hori kernel: hdd: ATAPI reset complete
Jun 21 01:17:11 hori kernel: hdd: lost interrupt
Jun 21 01:17:11 hori kernel: ide-scsi: CoD != 0 in idescsi_pc_intr
Jun 21 01:17:11 hori kernel: scsi : aborting command due to timeout :
pid 4498, scsi0, channel 0, id 0, lun 0 Write (10) 00 00 00 00 df 00 00
07 00
Jun 21 01:17:11 hori kernel: SCSI host 0 abort (pid 4498) timed out -
resetting
Jun 21 01:17:11 hori kernel: SCSI bus is being reset for host 0 channel 0.
Jun 21 01:17:11 hori kernel: scsi : aborting command due to timeout :
pid 4499, scsi0, channel 0, id 0, lun 0 Write (10) 00 00 00 01 04 00 00
03 00
Jun 21 01:17:11 hori kernel: SCSI host 0 abort (pid 4499) timed out -
resetting
Jun 21 01:17:11 hori kernel: SCSI bus is being reset for host 0 channel 0.
Jun 21 01:17:11 hori kernel: hdd: ATAPI reset complete
Jun 21 01:17:11 hori kernel: hdd: lost interrupt
Jun 21 01:17:11 hori kernel: ide-scsi: CoD != 0 in idescsi_pc_intr
Jun 21 01:17:11 hori kernel: hdd: ATAPI reset complete
Jun 21 01:17:11 hori kernel: hdd: lost interrupt
Jun 22 02:18:04 hori syslogd 1.4.1: restart.
These messages keep repeating itself until forever.
I also tried to use the ide-scsi driver instead, but I am running into
the same problem. Is this a known bug in the latest stable kernel or am
I having a bad hardware ?
Thank You,
Emre
reply other threads:[~2002-06-22 17:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3D14B311.80802@verizon.net \
--to=emre.tezel@verizon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox