From: "willy tarreau" <wtarreau@yahoo.fr>
To: linux-kernel@vger.kernel.org
Subject: Did someone try to boot 2.4.16 on a 386 ?
Date: Fri, 30 Nov 2001 10:28:53 +0100 (CET) [thread overview]
Message-ID: <20011130092853.20937.qmail@web20506.mail.yahoo.com> (raw)
Hi !
I just happened to test 2.4.16 on my 386 (firewall)
and
just after the message "Uncompressing kernel", the PC
reboots just as after an illegal op, or a triple
fault. I tried
to diff between 2.4.13-ac8 (which previously worked)
and 2.4.16, but I don't see many changes (except the
CR2 patch that I reverted in 2.4.13-ac8 anyway, and
which is still not present in 2.4.16).
I also checked for illegal instructions like there has
already been in the past (cmov, bswap, cmpxchg) but
couldn't find any. I could only find some rdmsr, wrmsr
and cpuid in functions which, to my knowledge, are not
called when an i386 boots.
I'm sorry I don't have the .config right here, but
it's
simply minimalistic : module, ide, iptables, serial
console. Of course, I've already checked there were no
accidental CONFIG_SMP nor MTRR ...
The system has 8 MB of RAM, and 16 MB of
CompactFlash connected to the IDE controller. The
onboard VGA is enabled and didn't cause any problem
before, but it may be possible that the reboots
happens
when the system tries to change the video mode.
Since I spent a long time recompiling with several
options, I didn't yet test if vanilla 2.4.13-2.4.15
could
boot on this PC. I didn't test with a serial console
either.
So my two questions are :
- does anybody happen to boot 2.4.16 on a 386 ?
- does someone have an idea of another change in the
kernel that could affect its boot on such a
machine ?
Regards,
Willy
___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Courrier : http://courrier.yahoo.fr
reply other threads:[~2001-11-30 9:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20011130092853.20937.qmail@web20506.mail.yahoo.com \
--to=wtarreau@yahoo.fr \
--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®