From: "H. Peter Anvin" <hpa@zytor.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux kernel <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@kernel.org>,
Ivan Seskar <Seskar@winlab.rutgers.edu>,
jfm3 <jfm3@winlab.rutgers.edu>, Sujith <m.sujith@gmail.com>
Subject: Re: Bug on 2.6.26 - x86 VIA Nehemiah CentaurHauls processor cannot boot
Date: Mon, 21 Jul 2008 19:24:50 -0400 [thread overview]
Message-ID: <48851AC2.8030007@zytor.com> (raw)
In-Reply-To: <43e72e890807210701w6d7f5638w5fdbea76a1cf1c0b@mail.gmail.com>
Luis R. Rodriguez wrote:
> On Mon, Jul 21, 2008 at 6:23 AM, H. Peter Anvin <hpa@zytor.com> wrote:
>> Luis R. Rodriguez wrote:
>>> This bug seems to be present since 2.6.22 [1], so hope we can get this
>>> fixed ASAP. Let me know if you have patch suggestions I can test.
>>>
>>> This crashes very early, I had to use earlyprintk to get it.
>>>
>
> I've put extra spaces between the culprit.
>
> c0387ac2: 0f 1f 40 00 nopl 0x0(%eax)
>
Sure enough, our old friend.
You have in your configuration:
CONFIG_M686=y
# CONFIG_X86_GENERIC is not set
... so this is fully expected; CONFIG_M686 without CONFIG_X86_GENERIC is
not compatible with such processors.
Not a bug.
-hpa
next prev parent reply other threads:[~2008-07-21 23:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 13:14 Bug on 2.6.26 - x86 VIA Nehemiah CentaurHauls processor cannot boot Luis R. Rodriguez
2008-07-21 13:23 ` H. Peter Anvin
2008-07-21 14:01 ` Luis R. Rodriguez
2008-07-21 23:24 ` H. Peter Anvin [this message]
2008-07-22 4:47 ` Luis R. Rodriguez
2008-07-22 13:10 ` H. Peter Anvin
2008-07-22 17:10 ` Jeff Garzik
2008-07-22 18:21 ` H. Peter Anvin
2008-07-22 18:33 ` Jeff Garzik
2008-07-22 18:41 ` H. Peter Anvin
2008-07-22 23:28 ` Jeff Garzik
2008-07-23 0:31 ` H. Peter Anvin
2008-07-22 13:14 ` Ingo Molnar
2008-07-22 13:24 ` H. Peter Anvin
2008-07-22 13:46 ` Ingo Molnar
2008-07-22 13:54 ` H. Peter Anvin
2008-07-26 18:31 ` Andi Kleen
2008-07-26 18:35 ` H. Peter Anvin
2008-07-26 18:44 ` Andi Kleen
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=48851AC2.8030007@zytor.com \
--to=hpa@zytor.com \
--cc=Seskar@winlab.rutgers.edu \
--cc=hpa@kernel.org \
--cc=jfm3@winlab.rutgers.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=m.sujith@gmail.com \
--cc=mcgrof@gmail.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