From: Andrew Morton <akpm@osdl.org>
To: Jeff Wiegley <jeffw@cyte.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: amd64 cdrom access locks system
Date: Wed, 8 Jun 2005 05:23:54 -0700 [thread overview]
Message-ID: <20050608052354.7b70052c.akpm@osdl.org> (raw)
In-Reply-To: <42A64556.4060405@cyte.com>
Jeff Wiegley <jeffw@cyte.com> wrote:
>
> I've been having this problem in 2.6.12-rc2 and 2.6.12-rc6.
>
> Any continued access to /dev/hda causes a complete and total
> lock up of the system. Nothing is logged to /var/log/kernel
> or /var/log/messages. Just a solid freeze.
>
> This happens with at least cdparanoia and cdrecord as well.
>
> The machine is an AMD64 FX55 CPU running in a shuttle
> ST20G5 chassis.
Can you identify an earlier kernel which worked OK?
How locked up is it? Does sysrq-P not work? Is it pingable? Tried
enabling the nmi watchdog?
next prev parent reply other threads:[~2005-06-08 12:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-08 1:09 Jeff Wiegley
2005-06-08 12:23 ` Andrew Morton [this message]
2005-06-09 15:36 ` Jeff Wiegley
2005-06-09 23:00 ` Andrew Morton
2005-06-09 19:38 ` Jeff Wiegley
2005-06-09 21:58 ` Jeff Wiegley
2005-06-09 23:32 ` Venkatesh Pallipadi
2005-06-09 18:23 ` Jeff Wiegley
2005-06-13 16:35 ` Jeff Wiegley
2005-06-14 7:55 ` Bartlomiej Zolnierkiewicz
2005-06-14 10:35 ` Jeff Wiegley
2005-06-14 18:16 ` Bartlomiej Zolnierkiewicz
2005-12-15 9:15 ` Aric Cyr
[not found] <4d3Xi-33s-31@gated-at.bofh.it>
[not found] ` <4d7Rk-6fq-49@gated-at.bofh.it>
[not found] ` <4dE0F-77V-17@gated-at.bofh.it>
[not found] ` <4dEk0-7ua-1@gated-at.bofh.it>
[not found] ` <4dJWr-38Z-33@gated-at.bofh.it>
2005-06-11 16:02 ` Robert Hancock
2005-08-09 7:47 David C. Young
[not found] <S1750841AbWAQXWc/20060117232242Z+104@vger.kernel.org>
2006-01-18 0:31 ` Christer Bäckström
2006-01-18 9:18 ` Alan Cox
2006-01-18 12:15 ` Christer Bäckström
2006-01-18 10:01 ` Bartlomiej Zolnierkiewicz
2006-02-05 12:14 ` Erwin Rol
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=20050608052354.7b70052c.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=jeffw@cyte.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®