public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	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: Tue, 22 Jul 2008 13:10:59 -0400	[thread overview]
Message-ID: <488614A3.1060400@garzik.org> (raw)
In-Reply-To: <43e72e890807212147p5d19cfact17e719abb338378c@mail.gmail.com>

Luis R. Rodriguez wrote:
> On Mon, Jul 21, 2008 at 4:24 PM, H. Peter Anvin <hpa@zytor.com> wrote:
>> 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.
> 
> 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.

Well, it may be intentional -- some distros simply exclude support for 
the lower-volume VIA processors, since that might imply building their 
"generic 686 kernel" sans CMOV and some other instructions, and changing 
the compiler's instruction scheduling to something less optimal for the 
majority.  :/

	Jeff




  parent reply	other threads:[~2008-07-22 17:11 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
2008-07-22  4:47       ` Luis R. Rodriguez
2008-07-22 13:10         ` H. Peter Anvin
2008-07-22 17:10         ` Jeff Garzik [this message]
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=488614A3.1060400@garzik.org \
    --to=jeff@garzik.org \
    --cc=Seskar@winlab.rutgers.edu \
    --cc=hpa@kernel.org \
    --cc=hpa@zytor.com \
    --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