From: Wakko Warner <wakko@animx.eu.org>
To: Joshua Hudson <joshudson@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cdrom: a dirty CD can freeze your system
Date: Thu, 4 May 2006 20:20:09 -0400 [thread overview]
Message-ID: <20060505002009.GA24014@animx.eu.org> (raw)
In-Reply-To: <bda6d13a0605041710v480b4c0ci999fcf4b0cffa1b@mail.gmail.com>
Joshua Hudson wrote:
> On 5/4/06, Wakko Warner <wakko@animx.eu.org> wrote:
> >Joshua Hudson wrote:
> >> I've seen this a few times. It never actually hung my system, only one
> >> virtual console. I wonder if preemptable kernel had something to do
> >> with that <g>
> >
> >I don't believe pre-empt has anything to do eith it. I have a specialized
> >boot system (vairous types of boot media) w/o preempt turned on because I
> >want this as small as possible. It also has this problem.
>
> Uuhhh. I though preempt might be the reason the who system *wasn't* hanging.
One of those "didn't read the whole message" errors. Oops. All of my
systems (not the speciallized one) are preemptable. I have not noticed any
lockups on those.
--
Lab tests show that use of micro$oft causes cancer in lab animals
Got Gas???
next prev parent reply other threads:[~2006-05-05 0:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-04 12:32 cdrom: a dirty CD can freeze your system Herbert Rosmanith
2006-05-04 12:45 ` Michael Tokarev
2006-05-04 12:56 ` Herbert Rosmanith
2006-05-04 14:41 ` Joseph Cheek
2006-05-04 13:48 ` Alan Cox
2006-05-04 14:14 ` Christian Trefzer
2006-05-04 15:28 ` Alan Cox
2006-05-04 17:54 ` Christian Trefzer
2006-05-04 16:50 ` Wakko Warner
2006-05-04 17:10 ` Alan Cox
2006-05-04 17:27 ` Joshua Hudson
2006-05-04 20:47 ` Wakko Warner
2006-05-05 0:10 ` Joshua Hudson
2006-05-05 0:20 ` Wakko Warner [this message]
2006-05-04 20:56 ` kernel keeps empty CDROM(DVD)-drive "busy"; (was Re: cdrom: a dirty CD can freeze your system) Linda Walsh
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=20060505002009.GA24014@animx.eu.org \
--to=wakko@animx.eu.org \
--cc=joshudson@gmail.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 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.