From: Charles Shannon Hendrix <shannon@widomaker.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: kernel 2.6.1 and cdrecord on ATAPI bus
Date: Sat, 17 Jan 2004 13:54:39 -0500 [thread overview]
Message-ID: <20040117185439.GB4496@widomaker.com> (raw)
In-Reply-To: <jevfna5vg7.fsf@sykes.suse.de>
Sat, 17 Jan 2004 @ 18:36 +0100, Andreas Schwab said:
> > % cdrecord -version
> > Cdrecord 2.00.3 (i686-pc-linux-gnu) Copyright (C) 1995-2002 J?rg Schilling
> >
> > I can try an alpha version, but from running strace on cdrecord, it
> > seems like Linux is the problem. Several ioctl() calls are failing just
> > before cdrecord prints an error message and exits.
>
> I see similar problems on ppc, with these messages in the log:
>
> Jan 17 16:15:43 whitebox kernel: ide0, timeout waiting for dbdma command stop
> Jan 17 16:15:43 whitebox kernel: ide-cd: dma error
> Jan 17 16:15:43 whitebox kernel: hdb: DMA disabled
> Jan 17 16:15:43 whitebox kernel: hdb: dma error: status=0x50 { DriveReady SeekComplete }
> Jan 17 16:15:43 whitebox kernel: hdb: dma error: error=0x00
> Jan 17 16:15:43 whitebox kernel: cdrom_newpc_intr: 180 residual after xfer
That's odd because it wasn't that way in 2.4 and the beta 2.6 kernels.
I did see an error trying to load sr_mod when cdrecord runs, presumably
because it is trying to scan my external SCSI burner, which is turned
off.
But "modprobe sr_mod" works fine.
In case it matters, I have a VIA 82Cxxx chipset and an Asus K7V
motherboard, one of those KT133 Pro models.
--
UNIX/Perl/C/Pizza____________________s h a n n o n@wido !SPAM maker.com
next prev parent reply other threads:[~2004-01-17 19:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-17 3:19 kernel 2.6.1 and cdrecord on ATAPI bus Charles Shannon Hendrix
2004-01-17 4:08 ` Måns Rullgård
2004-01-17 4:22 ` Matthias Andree
2004-01-17 15:49 ` Charles Shannon Hendrix
2004-01-17 17:36 ` Andreas Schwab
2004-01-17 18:54 ` Charles Shannon Hendrix [this message]
2004-01-17 22:45 ` Gene Heskett
2004-01-25 17:44 ` Jens Axboe
2004-01-26 2:17 ` Bill Davidsen
2004-01-26 15:38 ` Ken Moffat
2004-01-27 0:59 ` Charles Shannon Hendrix
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=20040117185439.GB4496@widomaker.com \
--to=shannon@widomaker.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