From: "Martin J. Bligh" <mbligh@aracnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [Bug 1156] New: Loose IRQ or fail SCSI Commands under heavy I/O
Date: Wed, 27 Aug 2003 10:11:53 -0700 [thread overview]
Message-ID: <75720000.1062004313@flay> (raw)
http://bugme.osdl.org/show_bug.cgi?id=1156
Summary: Loose IRQ or fail SCSI Commands under heavy I/O
Kernel Version: 2.6.0-test2 and test 3
Status: NEW
Severity: high
Owner: bzolnier@elka.pw.edu.pl
Submitter: dan@nerp.net
Distribution: Debian Testing
Hardware Environment: PIII 1 Gz on Intel 815ae2 mainboard
Software Environment: cdrecord or standard GNU commands
Problem Description: Under heavy I/O performance lags and one of the devices
(it changes every time) will loose it's IRQ. Sometimes the operation will
continue, sometimes it will seg fault and every once in a while it will lock
the PC, hard. When using SCSI emulation to a cd-rw drive cdrecord simply seg
faults. When I reboot to 2.4.21 SCSI emulation works perfect. I have swapped
out burners and tested on an Asus A7N8X based system with the same results.
Steps to reproduce:
Compile 2.6.0-test2 or 3 w/ SCSI emulation and appropriate support for hardware.
Copy large amounts of data, 1 GB or more, from one drive to another, wait for
IRQ to drop and lock-up the system or stop the transfer. Or merely attempt to
burn a CD, it fails 2 out of 3 when burning CDs. Both problems are very
consistent.
Device seems to be: Generic mmc CD-RW.
Current: 0x0002
Profile: 0x000A
Profile: 0x0009
Profile: 0x0008
Profile: 0x0002 (current)
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE FORCESPEED
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
FIFO size : 4194304 = 4096 KB
Track 01: data 404 MB
Total size: 464 MB (46:00.98) = 207074 sectors
Lout start: 464 MB (46:02/74) = 207074 sectors
cdrecord: Input/output error. test unit ready: scsi sendcmd: no error
Segmentation Fault
I cannot post a copy of the IRQ failure becuase it's lock-up every time now.
reply other threads:[~2003-08-27 17:22 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=75720000.1062004313@flay \
--to=mbligh@aracnet.com \
--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