From: William Lee Irwin III <wli@holomorphy.com>
To: Douglas Gilbert <dougg@torque.net>
Cc: linux-scsi@vger.kernel.org, gibbs@scsiguy.com
Subject: Re: Adaptec 39160 / Yamaha CRW8424S CD burning
Date: Mon, 13 Jan 2003 01:38:33 -0800 [thread overview]
Message-ID: <20030113093833.GD9558@holomorphy.com> (raw)
In-Reply-To: <20030113091635.GC9558@holomorphy.com>
On Mon, Jan 13, 2003 at 07:06:37PM +1100, Douglas Gilbert wrote:
>> Could you determine which one is happening? If the
>> sg route is being used then the individual SCSI
>> commands can be seen by observing 'cat /proc/scsi/sg/debug'
>> while the burn is in progress. What version of cdrecord
>> are you using and what does its output look like?
On Mon, Jan 13, 2003 at 01:16:35AM -0800, William Lee Irwin III wrote:
> I'm trying Jens' patched cdrecord from people/axboe/tools/ on kernel.org
> and got:
> $ cat /proc/scsi/sg/debug
> dev_max(currently)=6 max_active_device=3 (origin 1)
> def_reserved_size=32768
> >>> device=sg1 scsi0 chan=0 id=3 lun=0 em=0 sg_tablesize=128 excl=0
> FD(1): timeout=20500ms bufflen=129024 (res)sgat=4 low_dma=0
> cmd_q=1 f_packid=0 k_orphan=0 closed=0
> rb>> act: id=0 blen=63504 t_o/elap=40000/15ms sgat=2 op=0x2a
Okay, this spewed a coaster too. (2.5.49-mm2). Looks like I'll have to
reboot to have a chance of anything working. I'm going to take a shot
at 2.5.56-mm1 + your SG_IO fixes.
Bill
next prev parent reply other threads:[~2003-01-13 9:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-13 7:15 Adaptec 39160 / Yamaha CRW8424S CD burning William Lee Irwin III
2003-01-13 8:06 ` Douglas Gilbert
2003-01-13 8:11 ` William Lee Irwin III
2003-01-13 9:16 ` William Lee Irwin III
2003-01-13 9:38 ` William Lee Irwin III [this message]
2003-01-13 10:35 ` William Lee Irwin III
2003-01-13 12:57 ` William Lee Irwin III
2003-01-13 23:01 ` Douglas Gilbert
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=20030113093833.GD9558@holomorphy.com \
--to=wli@holomorphy.com \
--cc=dougg@torque.net \
--cc=gibbs@scsiguy.com \
--cc=linux-scsi@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.