From: "Kristofer T. Karas" <ktk@enterprise.bidmc.harvard.edu>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Matthias Andree <matthias.andree@gmx.de>,
Dick Johnson <root@chaos.analogic.com>,
Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Subject: [Answer] Re: Linux 2.4.24-pre1: Instant reboot
Date: 17 Dec 2003 01:07:21 -0500 [thread overview]
Message-ID: <1071641243.5423.27.camel@ktkhome> (raw)
In-Reply-To: <20031216223833.GC12564@merlin.emma.line.org>
Short answer to my previous post on this subject:
CONFIG_EDD=y + Athlon + VIA KT266A = triple fault on boot.
Longer answer:
Dick Johnson asked,
> What CPU did you compile it for?
Compiled 2.4.24-pre1 for Athlon/K7. I also tried it with generic i386,
which made no difference.
Matthias Andree wrote:
> I've seen this, too, with XFS=y and OOM_KILLER=n,
If I didn't have 2 hours sleep, I would have hacked rc.sysinit to
auto-compile my linux kernel with a binary search looking for the
culprit, iterating if the BIOS rebooted an old kernel; but I was too
tired today for scriping foo. :-) So I did it the old fashioned way.
Turns out, after about a dozen compile/reboot loops, I narrowed it down
repeatably to the "x86 BIOS Enhanced Disk Drive support" (CONFIG_EDD)
option. I can turn off just about every .config option, turn that one
on, and the kernel triple faults upon boot. This is the first time that
a 2.4.x kernel has ever triple faulted on boot on my system. As
mentioned above, CPU choice makes no difference.
Marcelo: Perhaps have the author of whatever patch interacts with
CONFIG_EDD work a bit more on getting the patch right for various
platforms. The (EXPERIMENTAL) feature worked just fine for me on
2.4.22...24.2.23, but the current -pre1 bombs for athlon/via_kt266a.
Kris
next prev parent reply other threads:[~2003-12-17 6:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-16 19:57 Kristofer T. Karas
2003-12-16 20:16 ` Richard B. Johnson
2003-12-16 22:38 ` Matthias Andree
2003-12-17 6:07 ` Kristofer T. Karas [this message]
2003-12-17 12:45 ` [Answer] " Tomas Szepe
2003-12-17 18:20 ` Mike Fedyk
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=1071641243.5423.27.camel@ktkhome \
--to=ktk@enterprise.bidmc.harvard.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=matthias.andree@gmx.de \
--cc=root@chaos.analogic.com \
/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®