All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	linux-scsi@vger.kernel.org, Jens Axboe <jens.axboe@oracle.com>,
	Jeff Garzik <jeff@garzik.org>
Subject: Re: dmesg spam
Date: Mon, 04 Feb 2008 14:15:00 -0600	[thread overview]
Message-ID: <1202156101.3096.102.camel@localhost.localdomain> (raw)
In-Reply-To: <20080204120548.79f3fe57.akpm@linux-foundation.org>

On Mon, 2008-02-04 at 12:05 -0800, Andrew Morton wrote:
> On Mon, 4 Feb 2008 15:24:55 +0100 Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> wrote:
> 
> > On Sunday 03 February 2008, Andrew Morton wrote:
> > > 
> > > With latest -mm, running fc8 I am getting this in the logs,
> >                            ^^^
> > => SCSI/libata
> > 
> > cc:ing Jeff
> > 
> > > once per second.
> > > 
> > > sr0: CDROM not ready.  Make sure there is a disc in the drive.
> > > sr0: CDROM not ready.  Make sure there is a disc in the drive.
> > > sr0: CDROM not ready.  Make sure there is a disc in the drive.
> > > sr0: CDROM not ready.  Make sure there is a disc in the drive.
> > > sr0: CDROM not ready.  Make sure there is a disc in the drive.
> > > sr0: CDROM not ready.  Make sure there is a disc in the drive.
> > > sr0: CDROM not ready.  Make sure there is a disc in the drive.
> > > sr0: CDROM not ready.  Make sure there is a disc in the drive.
> > > sr0: CDROM not ready.  Make sure there is a disc in the drive.
> 
> Well..  it's coming out of the kernel.  Presumably it's that cdrom polling
> thing in KDE.  James recently made changes to sr_ioctl.c but I've been
> buried in more terminal regressions than this one.

You're thinking of this one?

commit 210ba1d1724f5c4ed87a2ab1a21ca861a915f734
Author: James Bottomley <James.Bottomley@HansenPartnership.com>
Date:   Sat Jan 5 10:39:51 2008 -0600

    [SCSI] sr: update to follow tray status correctly
    
    Based on an original patch from: David Martin <tasio@tasio.net>
 
You could try reversing it if you want, but I'm not certain that's the
problem (the patch only affected sr_do_status, which is a cdrom internal
thing).

The message comes from sr_ioctl.c:sr_do_ioctl().  Which means some user
level application is poking the drive with a command that's returning
NOT_READY.  Apparently it will shut up if quiet is set in the packet
command structure.

It could be the application is getting the wrong idea of the status from
sr_do_staus() which leads it to send commands which require a medium?
But we'll need a bit of debugging to determine this.

James



  parent reply	other threads:[~2008-02-04 20:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-03 22:30 dmesg spam Andrew Morton
2008-02-04 14:24 ` Bartlomiej Zolnierkiewicz
2008-02-04 20:05   ` Andrew Morton
2008-02-04 20:14     ` Jeff Garzik
2008-02-04 20:20       ` James Bottomley
2008-02-04 20:24         ` Jeff Garzik
2008-02-04 20:44           ` James Bottomley
2008-02-05  3:59             ` Andrew Morton
2008-02-04 20:15     ` James Bottomley [this message]
2008-02-04 20:21       ` Jeff Garzik
2008-02-04 21:07         ` Andrew Morton

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=1202156101.3096.102.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=bzolnier@gmail.com \
    --cc=jeff@garzik.org \
    --cc=jens.axboe@oracle.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.