mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.10ac10, cdrecord 1.9-6, Mitsumi CR-4804TE: lock up burning too large image
Date: Mon, 22 Oct 2001 15:03:52 -0400	[thread overview]
Message-ID: <200110221903.f9MJ3qZ16095@deathstar.prodigy.com> (raw)
In-Reply-To: <20011021135455.C1598@niksula.cs.hut.fi>

In article <20011021135455.C1598@niksula.cs.hut.fi> vherva@niksula.hut.fi wrote:
| When (accidentally) trying to burn ~670MB onto a 74" cdr disk, I experienced
| a complete lock up.
|                                                                                 
| It went to 99% (as one would expect), and then drive began giving weird
| sounds - as if it was moving the head from start to end over and over. After
| a short while, the whole system locked up, no mouse, keyboard, caps lock,
| ctrl-alt-del, alt-sysrq-{s,u,b}.
|                                                                                 
| It used to give a nice error when disk size was exceeded with 2.2.18pre19
| and a tad older cdrecord (1.9-something (1.10-4 failed on 2.2 BTW, giving
| error on mmapping /dev/null)).
|                                                                                 
| I assume this is a kernel thing...

  You are probably correct, but you might try running as a user other
than root, with proper permissions on the device. cdwrite tries to run
with realtime priority, and I don't know just how tightly a realtime
process could lock the systems if it gets its knickers in a twist.

  You might also try software watchdog, I would expect it to reboot if
the kernel is up but the RT process is looping, such as waiting for a
status to change or some such.

-- 
bill davidsen <davidsen@tmr.com>
  His first management concern is not solving the problem, but covering
his ass. If he lived in the middle ages he'd wear his codpiece backward.

  reply	other threads:[~2001-10-22 19:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-21 10:54 Ville Herva
2001-10-22 19:03 ` bill davidsen [this message]
     [not found] <200110211137.f9LBb1w08887@burner.fokus.gmd.de>
2001-10-21 11:46 ` Ville Herva
2001-10-21 11:56 Joerg Schilling
2001-10-21 12:08 ` Ville Herva
2001-10-21 12:10 Joerg Schilling
2001-10-21 17:25 ` Ville Herva
2001-10-22  5:48 Paul Kreiner

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=200110221903.f9MJ3qZ16095@deathstar.prodigy.com \
    --to=davidsen@tmr.com \
    --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

all inboxes | Powered by JetHome®