From: Jeff Garzik <jeff@garzik.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
linux-scsi@vger.kernel.org, Jens Axboe <jens.axboe@oracle.com>
Subject: Re: dmesg spam
Date: Mon, 04 Feb 2008 15:21:54 -0500 [thread overview]
Message-ID: <47A773E2.2090803@garzik.org> (raw)
In-Reply-To: <1202156101.3096.102.camel@localhost.localdomain>
James Bottomley wrote:
> 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.
Userland polling of the cdrom is quite normal (if unfortunately),
regardless of medium presence. Probably HAL or dbus.
In theory, the userland app should (a) set quiet and (b) handle
not-ready condition just fine.
I presume that (b) is ok, since not-ready just means to continue polling
the cdrom ad infinitum, until media appears.
A useful experiment, if only to confirm the obvious, would be to insert
some media.
What controller and device is in use?
Jeff
next prev parent reply other threads:[~2008-02-04 20:21 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
2008-02-04 20:21 ` Jeff Garzik [this message]
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=47A773E2.2090803@garzik.org \
--to=jeff@garzik.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=bzolnier@gmail.com \
--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.