linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ethan Weinstein <lists@stinkfoot.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Tero Knuutila <tero1001@hotmail.com>, linux-kernel@vger.kernel.org
Subject: Re: cdrecord hangs my computer
Date: Sat, 06 Dec 2003 03:54:36 -0500	[thread overview]
Message-ID: <3FD1994C.10607@stinkfoot.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0312060011130.2092@home.osdl.org>

Linus Torvalds wrote:
> 
> On Sat, 6 Dec 2003, Tero Knuutila wrote:
> 
>>My system hangs everytime I try to  burn my .wav files to cd with cdrecord.
>>Usually few tracks go succesfully but then everything stops. Even the mouse
>>won't move and powerbutton does not affect.
> 
> 
> Is this with ide-scsi? If so, does the appended patch help?
> 
> If not, we really need a whole lot more information (hw config, messages
> etc).
> 
> 		Linus

I've noted this at boot several times with 2.6.0-test11

Dec  4 23:59:21 e-d0uble kernel: ide-scsi is deprecated for cd burning! 
Use ide-cd and give dev=/dev/hdX as device

Removing the ide-cd bootparams: (I didn't try the patch)

Cdrecord 2.00.3 seems to like the sony-dru500a, denoted as 
--dev=/dev/hdc, I burned several disks this way.
crdao and growisofs don't like to parse /dev/hdc as an argumenet, but 
I'm sure these are easily fixed.

Ethan

  reply	other threads:[~2003-12-06  8:51 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-06  8:01 cdrecord hangs my computer Tero Knuutila
2003-12-06  8:12 ` Linus Torvalds
2003-12-06  8:54   ` Ethan Weinstein [this message]
2003-12-06 11:59     ` Måns Rullgård
2003-12-06 13:40     ` Wakko Warner
2003-12-06 14:37       ` John Bradford
2003-12-06 21:57       ` Linus Torvalds
2003-12-06 22:02         ` Larry McVoy
2003-12-06 22:32           ` Linus Torvalds
2003-12-07 11:01             ` Eduard Bloch
2003-12-07 16:18               ` Linus Torvalds
2003-12-08 16:21                 ` bill davidsen
2003-12-08 17:46                   ` Linus Torvalds
2003-12-09 12:38                     ` Bill Davidsen
2003-12-08 17:53                   ` Valdis.Kletnieks
2003-12-08 18:53                     ` Linus Torvalds
2003-12-08 19:40                       ` Valdis.Kletnieks
2003-12-09 14:50                         ` Ian Soboroff
2003-12-09 20:42                           ` Mikael Pettersson
2003-12-08 16:24                 ` Martin J. Bligh
2003-12-08 19:22                   ` dialectical deprecation " Bob
2003-12-09 21:19                     ` bill davidsen
2003-12-09 22:31                     ` David Lang
2003-12-09 21:51                       ` Måns Rullgård
2003-12-08  4:36           ` Bob
2003-12-08  4:51             ` Larry McVoy
2003-12-07  0:16         ` Wakko Warner
2003-12-07  3:31           ` William Lee Irwin III
2003-12-07  4:49           ` Linus Torvalds
2003-12-08 16:13         ` bill davidsen
2003-12-08 17:38           ` Linus Torvalds
2003-12-08 19:41             ` bluefaceplate demographics " Bob
2003-12-06 16:42     ` Linus Torvalds
2003-12-06 12:39 Tero Knuutila
2003-12-06 18:27 Tero Knuutila
2003-12-06 19:08 Tero Knuutila
2003-12-08  9:31 Douglas Gilbert
2003-12-11 12:56 ` Jens Axboe
2003-12-11 16:15   ` Linus Torvalds
2003-12-15 13:29 Paul Marinceu

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=3FD1994C.10607@stinkfoot.org \
    --to=lists@stinkfoot.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tero1001@hotmail.com \
    --cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).