On Mon, 2008-02-04 at 12:05 -0800, Andrew Morton wrote:
> On Mon, 4 Feb 2008 15:24:55 +0100 Bartlomiej Zolnierkiewicz <[EMAIL 
> PROTECTED]> 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 <[EMAIL PROTECTED]>
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 <[EMAIL PROTECTED]>
 
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


-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to