public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@digeo.com>
Subject: Re: 2.5.64-mm6: oops in elv_remove_request
Date: Fri, 14 Mar 2003 12:37:32 +0100	[thread overview]
Message-ID: <20030314113732.GC791@suse.de> (raw)
In-Reply-To: <1047637870.1147.27.camel@ixodes.goop.org>

On Fri, Mar 14 2003, Jeremy Fitzhardinge wrote:
> On Fri, 2003-03-14 at 02:42, Jens Axboe wrote:
> > Looks much better. Somehow the 'random' rpm you had didn't do SG_IO,
> > odd.
> 
> Hm, not better enough.  When I test a burn, I get this:
> 
> # cdrecord -dummy -data -isosize perforce.iso
> Cdrecord 2.01a05 (i686-pc-linux-gnu) Copyright (C) 1995-2002 J?rg Schilling
> scsidev: '/dev/hdc'
> devname: '/dev/hdc'
> scsibus: -2 target: -2 lun: -2
> Warning: Open by 'devname' is unintentional and not supported.
> Linux sg driver version: 3.5.27
> Using libscg version 'schily-0.7'
> Device type    : Removable CD-ROM
> Version        : 0
> Response Format: 1
> Vendor_info    : 'PLEXTOR '
> Identifikation : 'CD-R   PX-W4824A'
> Revision       : '1.04'
> Device seems to be: Generic mmc CD-RW.
> Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
> Driver flags   : MMC-3 SWABAUDIO BURNFREE VARIREC
> Supported modes:
> cdrecord: Drive does not support TAO recording.
> cdrecord: Illegal write mode for this drive.
> exit status 255
> 
> I'm guessing the "Supported modes:" line should have something on it
> (TAO, at least).  With ide-scsi it does print many modes.

I've seen this bug reported before. But that's interesting, will try it
on my test box. Linus reported some problem with single byte commands
months ago, maybe this is related.

Can you send me the output of -prcap?

-- 
Jens Axboe


  reply	other threads:[~2003-03-14 10:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-13 17:22 2.5.64-mm6: kernel BUG at kernel/timer.c:155! Jeremy Fitzhardinge
2003-03-13 17:45 ` Jeremy Fitzhardinge
2003-03-13 17:54 ` Jens Axboe
2003-03-13 18:04   ` Jeremy Fitzhardinge
2003-03-13 19:02     ` Jens Axboe
2003-03-14  9:24       ` 2.5.64-mm6: oops in elv_remove_request Jeremy Fitzhardinge
2003-03-14 10:42         ` Jens Axboe
2003-03-14 10:06           ` Jeremy Fitzhardinge
2003-03-14 10:31           ` Jeremy Fitzhardinge
2003-03-14 11:37             ` Jens Axboe [this message]
2003-03-14 17:59               ` Jeremy Fitzhardinge
2003-03-14 18:07                 ` Jens Axboe
2003-03-14 22:19                   ` Jeremy Fitzhardinge
2003-03-15  8:15                     ` Jens Axboe
2003-03-16  2:54                       ` Jeremy Fitzhardinge
2003-03-17  8:05                         ` Jens Axboe
2003-03-17 16:56                           ` Jeremy Fitzhardinge
2003-03-24 13:14                             ` Jens Axboe
2003-03-14 20:33         ` Jens Axboe
2003-03-14 22:15           ` Jeremy Fitzhardinge
2003-03-15  8:15             ` Jens Axboe
2003-03-13 20:52 ` 2.5.64-mm6: kernel BUG at kernel/timer.c:155! Aravind

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=20030314113732.GC791@suse.de \
    --to=axboe@suse.de \
    --cc=akpm@digeo.com \
    --cc=jeremy@goop.org \
    --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