From: Samuel Sieb <samuel@sieb.net>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: kernel won't boot on a Cyrix MediaGXm (Geode )
Date: Sun, 20 Jul 2008 22:11:46 -0700 [thread overview]
Message-ID: <48841A92.4020301@sieb.net> (raw)
I have a computer here with a CPU that the BIOS identifies as:
Cyrix MediaGXm/Cx5530 Unicorn Revision 1.19.3B
kernel 2.6.14 identifies it as:
vendor_id : Geode by NSC
cpu family : 5
model : 9
model name : Geode(TM) Integrated Processor by National Semi
stepping : 1
I can't boot any kernel later than 2.6.22 on it. Anything later either
hangs or gives random kernel panics while booting. I tracked down the
problem to a specific commit:
commit f25f64ed5bd3c2932493681bdfdb483ea707da0a
Author: Juergen Beisert <juergen@kreuzholzen.de>
Date: Sun Jul 22 11:12:38 2007 +0200
x86: Replace NSC/Cyrix specific chipset access macros by inlined
functions.
Reversing the patch (compensating for kernel changes) let me boot a
2.6.25 kernel. I realize the patch is supposed to fix something that
didn't work right, but I didn't have a problem before and I do now. :-)
next reply other threads:[~2008-07-21 5:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 5:11 Samuel Sieb [this message]
2008-07-21 6:28 ` kernel won't boot on a Cyrix MediaGXm (Geode ) Juergen Beisert
2008-07-22 5:16 ` Samuel Sieb
2008-07-22 8:08 ` Juergen Beisert
2008-07-23 7:13 ` Samuel Sieb
2008-07-21 6:36 ` Rafael C. de Almeida
2008-07-21 11:47 ` Ingo Molnar
2008-07-22 5:10 ` Samuel Sieb
2008-07-22 10:24 ` Ingo Molnar
2008-07-22 10:51 ` Juergen Beisert
2008-07-23 7:18 ` Samuel Sieb
2008-07-28 15:32 ` Ingo Molnar
2008-07-28 17:58 ` Samuel Sieb
2008-07-29 9:18 ` Ingo Molnar
2008-07-29 8:15 ` Juergen Beisert
2008-08-07 5:06 ` Samuel Sieb
2008-08-20 9:32 ` Ingo Molnar
2008-08-20 9:44 ` Juergen Beisert
2008-08-20 10:45 ` Ingo Molnar
2008-08-20 11:03 ` Juergen Beisert
2008-08-20 11:20 ` Ingo Molnar
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=48841A92.4020301@sieb.net \
--to=samuel@sieb.net \
--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