public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Albert Cahalan <albert@users.sf.net>
To: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Cc: jgarzik@pobox.com, mikpe@csd.uu.se, m.c.p@wolk-project.de
Subject: Re: [patch 2.4 1/2] backport 2.6 x86 cpu capabilities
Date: 10 Aug 2003 19:59:03 -0400	[thread overview]
Message-ID: <1060559943.948.121.camel@cube> (raw)

Mikael Pettersson writes:

> 2.4.21-rc1 with NCAPINTS==6 hangs at boot in the local
> APIC timer calibration step; before that it detected a
> 0MHz bus clock and the local APIC NMI watchdog was stuck.
> Correcting head.S:X86_VENDOR_ID fixes these problems.
> 
> Without correcting head.S:X86_VENDOR_ID, head.S will store
> the vendor id partly in the capabilities array. This breaks
> both the capabilities and the vendor id. I can't say why 2.6
> works, but obviously the CPU setup code has changed since 2.4.

I may be stating the obvious, but in case not...

If Jeff Garzik missed this, others will too. I hope
that a big comment gets added in both places, assuming
that automatic offset generation isn't practical.



             reply	other threads:[~2003-08-11  0:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-10 23:59 Albert Cahalan [this message]
2003-08-11  0:28 ` [patch 2.4 1/2] backport 2.6 x86 cpu capabilities Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2003-08-08 19:41 Mikael Pettersson
2003-08-09 14:05 ` Jeff Garzik
2003-08-08 11:19 Mikael Pettersson
2003-08-08 13:15 ` Jeff Garzik
2003-08-09  9:51   ` Marc-Christian Petersen
2003-08-08  2:54 Jeff Garzik

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=1060559943.948.121.camel@cube \
    --to=albert@users.sf.net \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.c.p@wolk-project.de \
    --cc=mikpe@csd.uu.se \
    /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