[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <43e72e890807212147p5d19cfact17e719abb338378c@mail.gmail.com>
Date: Mon, 21 Jul 2008 21:47:44 -0700
From: "Luis R. Rodriguez" <mcgrof@...il.com>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: "linux kernel" <linux-kernel@...r.kernel.org>,
"H. Peter Anvin" <hpa@...nel.org>,
"Ivan Seskar" <Seskar@...lab.rutgers.edu>,
jfm3 <jfm3@...lab.rutgers.edu>, Sujith <m.sujith@...il.com>
Subject: Re: Bug on 2.6.26 - x86 VIA Nehemiah CentaurHauls processor cannot boot
On Mon, Jul 21, 2008 at 4:24 PM, H. Peter Anvin <hpa@...or.com> wrote:
> Luis R. Rodriguez wrote:
>>
>> On Mon, Jul 21, 2008 at 6:23 AM, H. Peter Anvin <hpa@...or.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.
Thanks for taking a look at this. So well, it would be a
misconfiguration bug by the distribution then to try to support a
generic 686 kernel wihtout GENERIC then.
Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists