From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jens Axboe <axboe@suse.de>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.64-mm6: kernel BUG at kernel/timer.c:155!
Date: 13 Mar 2003 10:04:50 -0800 [thread overview]
Message-ID: <1047578690.1322.17.camel@ixodes.goop.org> (raw)
In-Reply-To: <20030313175454.GP836@suse.de>
On Thu, 2003-03-13 at 09:54, Jens Axboe wrote:
> On Thu, Mar 13 2003, Jeremy Fitzhardinge wrote:
> > I was reading back a freshly burned CD from my shiny new Plexwriter
> > 48/24/48A. I'm using ide-scsi, so this is an iso9660 filesystem mounted
>
> out of curiousity, why? ide-cd should work much better than ide-scsi in
> 2.5, if it doesn't I'd like to know.
Mostly because I couldn't make cdrecord work properly with ide-cd - it
kept claiming I had an adaptec disk connected rather than the plextor
cdrom:
: root@ixodes:pts/2; cdrecord -scanbus 'dev=ATAPI:'
Cdrecord 2.01a05 (i686-pc-linux-gnu) Copyright (C) 1995-2002 J?rg Schilling
scsidev: 'ATAPI:'
devname: 'ATAPI'
scsibus: -1 target: -1 lun: -1
Warning: Using ATA Packet interface.
Warning: The related libscg interface code is in pre alpha.
Warning: There may be fatal problems.
Using libscg version 'schily-0.7'
scsibus0:
0,0,0 0) 'ADAPTEC ' 'ACB-5500 ' 'FAKE' NON CCS Disk
0,1,0 1) *
0,2,0 2) *
0,3,0 3) *
0,4,0 4) *
0,5,0 5) *
0,6,0 6) *
0,7,0 7) *
Maybe I just need to spend more effort on the user-space tools. Is
there something other than cdrecord I should be using?
J
next prev parent reply other threads:[~2003-03-13 17:54 UTC|newest]
Thread overview: 24+ 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 [this message]
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
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
-- strict thread matches above, loose matches on Subject: below --
2003-03-13 18:28 Felipe Alfaro Solana
2003-03-13 19:04 ` 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=1047578690.1322.17.camel@ixodes.goop.org \
--to=jeremy@goop.org \
--cc=axboe@suse.de \
--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