From: Rene Herman <rene.herman@keyaccess.nl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: libata PATA patch update
Date: Wed, 24 May 2006 02:11:04 +0200 [thread overview]
Message-ID: <4473A498.4070101@keyaccess.nl> (raw)
In-Reply-To: <44739A36.90701@keyaccess.nl>
Rene Herman wrote:
>> CD and DVD ROMs are also working fine, including readcd and CDDA.
>
> Well, other than spamming the kernel message buffer into oblivion. Must
> have missed these last time around
Confirmed. Realised I was on 2.6.17-rc4-ide1 now, and 2.6.17-rc3-ide1 last
time, but I just downgraded and these messages are indeed also present on
2.6.17-rc3-ide1.
> but cdparanoia (regular cdparanoia) triggers tons and tons of these, with
> both sr0 (hdc, a CD-RW) and sr1 (hdd, DVD-ROM):
>
> sg_write: data in/out 56/56 bytes for SCSI command 0x12--guessing data in;
> program cdparanoia not setting count and/or reply_len properly
> sg_write: data in/out 26/26 bytes for SCSI command 0x5a--guessing data in;
> program cdparanoia not setting count and/or reply_len properly
> sg_write: data in/out 12/12 bytes for SCSI command 0x43--guessing data in;
> program cdparanoia not setting count and/or reply_len properly
> sg_write: data in/out 12/12 bytes for SCSI command 0x43--guessing data in;
> program cdparanoia not setting count and/or reply_len properly
> sg_write: data in/out 12/12 bytes for SCSI command 0x43--guessing data in;
> program cdparanoia not setting count and/or reply_len properly
> sg_write: data in/out 12/12 bytes for SCSI command 0x43--guessing data in;
> program cdparanoia not setting count and/or reply_len properly
> sg_write: data in/out 12/12 bytes for SCSI command 0x43--guessing data in;
> program cdparanoia not setting count and/or reply_len properly
> sg_write: data in/out 12/12 bytes for SCSI command 0x43--guessing data in;
> program cdparanoia not setting count and/or reply_len properly
> sg_write: data in/out 12/12 bytes for SCSI command 0x43--guessing data in;
> program cdparanoia not setting count and/or reply_len properly
> sg_write: data in/out 12/12 bytes for SCSI command 0x43--guessing data in;
> program cdparanoia not setting count and/or reply_len properly
> printk: 106 messages suppressed.
> sg_write: data in/out 30576/30576 bytes for SCSI command 0xbe--guessing
> data in;
> program cdparanoia not setting count and/or reply_len properly
> printk: 1087 messages suppressed.
> sg_write: data in/out 16464/16464 bytes for SCSI command 0xbe--guessing
> data in;
> program cdparanoia not setting count and/or reply_len properly
> printk: 1147 messages suppressed.
> sg_write: data in/out 30576/30576 bytes for SCSI command 0xbe--guessing
> data in;
> program cdparanoia not setting count and/or reply_len properly
Rene.
prev parent reply other threads:[~2006-05-24 0:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-08 16:06 libata PATA patch update Alan Cox
2006-05-08 16:54 ` Meelis Roos
2006-05-08 17:29 ` Kevin Radloff
2006-05-09 12:24 ` Alan Cox
2006-05-09 16:52 ` Kevin Radloff
2006-05-08 21:57 ` Matthieu CASTET
[not found] ` <1147178241.3172.74.camel@localhost.localdomain>
[not found] ` <4460D7D7.3070807@free.fr>
2006-05-10 21:24 ` matthieu castet
2006-05-08 23:48 ` Rene Herman
2006-05-09 12:30 ` Alan Cox
2006-05-09 20:05 ` Rene Herman
2006-05-23 23:26 ` Rene Herman
2006-05-24 0:11 ` Rene Herman [this message]
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=4473A498.4070101@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--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