From: Jan Knutar <jk-lkml@sci.fi>
To: linux-os@analogic.com
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>,
linux-kernel@vger.kernel.org,
Xavier Bestel <xavier.bestel@free.fr>
Subject: Re: Reading Bad DVD Under 2.6.10 freezes the box.
Date: Fri, 11 Feb 2005 05:25:19 +0200 [thread overview]
Message-ID: <200502110525.19433.jk-lkml@sci.fi> (raw)
In-Reply-To: <Pine.LNX.4.61.0502070939320.21570@chaos.analogic.com>
On Monday 07 February 2005 16:46, linux-os wrote:
> Basically, when you start getting the kernel error messages on
> linux-2.4.22, you can ^C out and everything will quiet down.
Not in my experience.
> With Linux-2.6.10, nothing entered from the keyboard will
> do anything. Since the Caps-Lock key still functions, interrupts
> are still active. However, it is likely the kernel-lock that
> prevents signals (like ^C or ^/) from being executed.
Speculations aside, I have found only one sure way of breaking
the eternal kernel-hang if you make the mistake of inserting a bad
CD into your drive; Needlehole eject.
Sure, the kernel will spit loads of error messages at you, but atleast
it wont be hung anymore, you can save work and reboot.
For eternal hangs when burning CDs though, I've found the only
reliable way of unhanging the system is to unplug power to the
CD burner and replug it. This seems to cause some amount of
disk corruption to the master device on the same IDE channel
though, so I guess if you have two harddrives, like me, it is a
hard choice between risking corruption on both, and risking
corruption on one.
HTH
next prev parent reply other threads:[~2005-02-11 3:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-07 12:32 Justin Piszcz
2005-02-07 13:05 ` linux-os
2005-02-07 13:46 ` Xavier Bestel
2005-02-07 14:17 ` Justin Piszcz
2005-02-07 14:25 ` Xavier Bestel
2005-02-07 14:46 ` linux-os
2005-02-11 3:25 ` Jan Knutar [this message]
2005-02-07 15:35 ` David Gómez
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=200502110525.19433.jk-lkml@sci.fi \
--to=jk-lkml@sci.fi \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=xavier.bestel@free.fr \
/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®