public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Alessandro Suardi <ALESSANDRO.SUARDI@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: "Latitude with broken BIOS" ?
Date: Mon, 20 Jan 2003 13:19:58 +0000	[thread overview]
Message-ID: <20030120131958.GB27417@codemonkey.org.uk> (raw)
In-Reply-To: <7346727.1043065918456.JavaMail.nobody@web11.us.oracle.com>

On Mon, Jan 20, 2003 at 04:31:58AM -0800, Alessandro Suardi wrote:


 >   I was hoping to use HT on my new Latitude C640 (P4 @ 1.8Ghz) but at boot
 >   both 2.4.21-pre3 and 2.5.59 (obviously with a SMP kernel) tell me

I'd be surprised^Wamazed if your laptop has HT. AFAIK, no-one is
shipping such a system yet. Just because the CPU flags say 'ht' does
not mean it has >1 CPU thread per CPU package.

 >  "Dell Latitude with broken BIOS detected. Refusing to enable the local APIC."

Lots of Dell laptops (like other vendors) crash instantly when trying to
enable the APIC.

 >  Is this anything that can be played with ?

Nope.

		Dave

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

  reply	other threads:[~2003-01-20 13:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-20 12:31 "Latitude with broken BIOS" ? Alessandro Suardi
2003-01-20 13:19 ` Dave Jones [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-20 13:28 Alessandro Suardi
2003-01-20 13:41 ` Dave Jones
2003-01-20 13:49 Alessandro Suardi
2003-01-20 14:13 Mikael Pettersson
2003-01-20 14:38 Alessandro Suardi
2003-01-20 15:02 Mikael Pettersson
2003-01-20 15:23 Alessandro Suardi
2003-05-23  8:55 Brouard Nicolas
2003-05-23  9:02 ` mikpe
2003-05-23 21:04   ` Brouard Nicolas
2003-05-23 17:41 ` Mark Watts

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=20030120131958.GB27417@codemonkey.org.uk \
    --to=davej@codemonkey.org.uk \
    --cc=ALESSANDRO.SUARDI@oracle.com \
    --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