From: Jens Axboe <axboe@suse.de>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: "Gregory T. Norris" <haphazard@socket.net>
Subject: Re: vmware 2.0.3, kernel 2.4.0 and a cdrom
Date: Tue, 6 Feb 2001 02:27:22 +0100 [thread overview]
Message-ID: <20010206022722.D9025@suse.de> (raw)
In-Reply-To: <20010205192235.A1567@glitch.snoozer.net>
In-Reply-To: <20010205192235.A1567@glitch.snoozer.net>; from haphazard@socket.net on Mon, Feb 05, 2001 at 07:22:35PM -0600
On Mon, Feb 05 2001, Gregory T. Norris wrote:
> On Mon, Jan 15 2001, Jens Axboe wrote:
> > Could you try with this patch, so maybe we can get some hints as to
> > what is going on?
>
> Here's what I got after applying your patch to 2.4.1:
>
> ----- SNIP -----
> Feb 5 17:25:26 glitch kernel: VFS: Disk change detected on device sr(11,0)
> Feb 5 17:25:26 glitch kernel: VFS: Disk change detected on device sr(11,0)
> Feb 5 17:25:26 glitch kernel: sr0: CDROM (ioctl) reports ILLEGAL REQUEST.
> Feb 5 17:25:26 glitch kernel: Mode Sense (10) 00 0e 00 00 00 00 00 18 00
> Feb 5 17:25:26 glitch kernel: [valid=0] Info fld=0x0, Current sr00:00: sense key Illegal Request
> Feb 5 17:25:26 glitch kernel: Additional sense indicates Invalid command operation code
> ----- SNIP -----
Interesting, does audio volume control work if you play an audio cd?
--
Jens Axboe
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-06 1:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-06 1:22 vmware 2.0.3, kernel 2.4.0 and a cdrom Gregory T. Norris
2001-02-06 1:27 ` Jens Axboe [this message]
2001-02-06 1:29 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2001-02-25 0:42 Rick Richardson
2001-01-14 19:49 Martin Maciaszek
2001-01-14 20:29 ` Martin Tessun
2001-01-15 21:15 ` 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=20010206022722.D9025@suse.de \
--to=axboe@suse.de \
--cc=haphazard@socket.net \
--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 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.