From: Jeff Garzik <jgarzik@pobox.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Andi Kleen <ak@suse.de>, Andrew Morton <akpm@osdl.org>,
Jens Axboe <axboe@suse.de>
Subject: Hang on x86-64, 2.6.9-rc3-bk4
Date: Sat, 16 Oct 2004 17:40:07 -0400 [thread overview]
Message-ID: <41719537.1080505@pobox.com> (raw)
A reproducible, hard hang on x86-64, during bootup's fsck ("touch
/forcefsck"). Athlon64, VIA motherboard, Promise SATA, VIA SATA, 512MB,
r8169. Hang begins in 2.6.9-rc3-bk4, everything works in 2.6.9-rc3-bk3.
Hang persists in 2.6.9-rc4 and 2.6.9-final.
Symptoms: touch /forcefsck and reboot. fsck will successfully check
all partitions of the WD drive attached to Promise, then fail precisely
54% through the fsck on the Maxtor drive attached to VIA SATA. SysRq
will print out the command header, but no output, for sysrq-[tps].
sysrq-m works... for a little while. then the machine completely
hangs, no sysrq or anything.
This is 100% reproducible.
There are -no- SATA driver changes between -bk3 and -bk4 AFAICS, which
leads me to guess at VM, or x86-64 platform?
The diff between -bk3 and -bk4 is pretty small, if you ignore the ARM
and m32r arch changes.
Jeff
next reply other threads:[~2004-10-16 21:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-16 21:40 Jeff Garzik [this message]
2004-10-16 21:46 ` Hang on x86-64, 2.6.9-rc3-bk4 Jeff Garzik
2004-10-16 22:48 ` Andrew Morton
2004-10-16 23:43 ` Jeff Garzik
2004-10-17 0:14 ` Andrew Morton
2004-10-17 0:25 ` Jeff Garzik
2004-10-17 0:28 ` Andrew Morton
2004-10-17 0:51 ` Jeff Garzik
2004-10-17 1:21 ` Andrew Morton
2004-10-17 3:39 ` Jeff Garzik
2004-10-17 5:46 ` Nick Piggin
2004-10-17 13:30 ` Jeff Garzik
2004-10-17 13:49 ` Nick Piggin
2004-10-17 14:00 ` Jeff Garzik
2004-10-17 14:19 ` Nick Piggin
2004-10-17 13:31 ` Jeff Garzik
2004-10-17 1:24 ` Nick Piggin
2004-10-17 2:16 ` Jeff Garzik
2004-10-17 2:19 ` Nick Piggin
2004-10-17 2:31 ` Nick Piggin
2004-10-17 3:10 ` Jeff Garzik
2004-10-17 3:20 ` Nick Piggin
2004-10-17 3:05 ` Jeff Garzik
2004-10-17 3:07 ` Nick Piggin
2004-10-17 3:13 ` Jeff Garzik
2004-10-18 18:45 ` Jeff Garzik
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=41719537.1080505@pobox.com \
--to=jgarzik@pobox.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--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.