public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <gilbertd@treblig.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: logs full of chatty IDE cdrom
Date: Sat, 10 May 2003 23:47:34 +0100	[thread overview]
Message-ID: <20030510224734.GF662@gallifrey> (raw)
In-Reply-To: <1052599284.19351.2.camel@dhcp22.swansea.linux.org.uk>

* Alan Cox (alan@lxorguk.ukuu.org.uk) wrote:
> On Sad, 2003-05-10 at 21:17, Dr. David Alan Gilbert wrote:
     ^^^
Are you running with a Welsh locale there?

> > Hi,
> >   I'm not sure but this seems to be a lot worse in 2.5.x for some
> > reason; my logs are full of I/O errors, not ready's and other errors from
> > my CDROM drive that is playing audio CDs; I suspect at least some of it
> > is due to kscd trying to figure out if there is a CD in an empty drive.
> 
> That shouldnt be generating messages. Its more important to know why or
> to see wtf its doing that generates them

OK, the full messages on starting kscd up are:

May 10 23:37:32 gallifrey kernel: end_request: I/O error, dev hde,
sector 0
May 10 23:37:32 gallifrey last message repeated 3 times
May 10 23:37:32 gallifrey kernel: hde: packet command error: status=0x51
{ DriveReady SeekComplete Error }
May 10 23:37:32 gallifrey kernel: hde: packet command error: error=0x50
May 10 23:37:32 gallifrey kernel: end_request: I/O error, dev hde, sector 0
May 10 23:37:32 gallifrey kernel: ATAPI device hde:
May 10 23:37:32 gallifrey kernel:   Error: Illegal request -- (Sense
key=0x05)
May 10 23:37:32 gallifrey kernel:   Parameter list length error --
(asc=0x1a, ascq=0x00)
May 10 23:37:32 gallifrey kernel:   The failed "Mode Select 10" packet
command was:
May 10 23:37:32 gallifrey kernel:   "55 10 00 00 00 00 00 00 00 00 00 00
00 00 00 00 "
May 10 23:37:33 gallifrey kernel: end_request: I/O error, dev hde, sector 0
May 10 23:38:04 gallifrey last message repeated 31 times

That is with no disc in the drive; the drive identifies itself as:
'Pioneer DVD-ROM ATAPIModel DVD-116 0109' and driver is 
'ide-cdrom version 4.59-ac1' (in 2.5.69)

But to be honest, my observation is more general - I'm sure I've seen
similar messages from VMware on systems (this system does not have it)
and other things rattling the CD drive on older kernels.  In general I
think I'd just like to tell IDE to be quiet about certain drives so it
makes it easier to spot serious errors in the logs.

Dave
 ---------------- Have a happy GNU millennium! ----------------------   
/ Dr. David Alan Gilbert    | Running GNU/Linux on Alpha,68K| Happy  \ 
\ gro.gilbert @ treblig.org | MIPS,x86,ARM,SPARC,PPC & HPPA | In Hex /
 \ _________________________|_____ http://www.treblig.org   |_______/

  reply	other threads:[~2003-05-10 22:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-10 20:17 logs full of chatty IDE cdrom Dr. David Alan Gilbert
2003-05-10 20:41 ` Alan Cox
2003-05-10 22:47   ` Dr. David Alan Gilbert [this message]
2003-05-10 22:18     ` Alan Cox
2003-05-10 23:58       ` Dr. David Alan Gilbert
2003-05-12 10:43   ` Martin Schlemmer
2003-05-14  8:16 ` Jens Axboe

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=20030510224734.GF662@gallifrey \
    --to=gilbertd@treblig.org \
    --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