From: Jens Axboe <axboe@suse.de>
To: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
Cc: jeremy@goop.org, linux-kernel@vger.kernel.org
Subject: Re: 2.5.64-mm6: kernel BUG at kernel/timer.c:155!
Date: Thu, 13 Mar 2003 20:04:21 +0100 [thread overview]
Message-ID: <20030313190421.GR836@suse.de> (raw)
In-Reply-To: <20030313182812.7679.qmail@linuxmail.org>
On Thu, Mar 13 2003, Felipe Alfaro Solana wrote:
> ----- Original Message -----
> From: Jens Axboe <axboe@suse.de>
> Date: Thu, 13 Mar 2003 18:54:54 +0100
> To: Jeremy Fitzhardinge <jeremy@goop.org>
> Subject: Re: 2.5.64-mm6: kernel BUG at kernel/timer.c:155!
>
> > 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.
>
> There are still userspace CD burning programs that do not yet
> support ATAPI burning interface. "cdrecord" does support it,
> but K3B (a KDE burning frontend to cdrecord and company)
> only works with SCSI or IDE-SCSI burners (well, or at least
> I have been unable to convince it to use the ATAPI interface
> to my Sony burner).
That is quite possible. Maybe someone could compile a list of programs
that still use read/write to /dev/sg*?
I had at some point planned to allow arbitrary block device -> /dev/sg*
mapping, maybe it would be a good idea to finish that thought. Then you
wouldn't have to rely on programs using SG_IO ioctl, which does seem
like a bad idea.
--
Jens Axboe
next prev parent reply other threads:[~2003-03-13 18:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 18:28 2.5.64-mm6: kernel BUG at kernel/timer.c:155! Felipe Alfaro Solana
2003-03-13 19:04 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-13 17:22 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-13 20:52 ` 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=20030313190421.GR836@suse.de \
--to=axboe@suse.de \
--cc=felipe_alfaro@linuxmail.org \
--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 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.