mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arnaud Patard <apatard@mandrakesoft.com>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org, wli@holomorphy.com
Subject: Re: 2.6.x BUGs at boot time (APIC related)
Date: Thu, 23 Dec 2004 10:33:28 +0100	[thread overview]
Message-ID: <m2u0qdgxzr.fsf@anduin.mandrakesoft.com> (raw)
In-Reply-To: <200412231102.10171.vda@port.imtp.ilyichevsk.odessa.ua> (Denis Vlasenko's message of "Thu, 23 Dec 2004 11:02:09 +0000")

Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua> writes:

> On Wednesday 22 December 2004 17:31, Denis Vlasenko wrote:
>> This is happening on a "HP Compaq dc7100 CMT"
>> (I believe it is a model number - taken from the label on the box).

iirc, dc7100 is the name of the minitower box, not of the computer :)

>>
>> Both 2.6.9 and 2.6.10-rc3 are dying this way:
>>
>> [top of visible screen]
>> I/O APIC #1 Version 17 at 0xFEC00000
>> Enabled APIC mode: Flat. Using 1 I/O APICs
>> ...
>> [unrelated stuff (dentry cache size etc...)]
>> ...
>> Enabling fast FPU save & restore ...done
>> Enabling unmasked SIMD FPU exception support ...done
>> Checking 'hlt' instruction ..OK
>> ------------------------
>> kernel BUG at arch/i386/kernel/apic.c:388! [:366! for 2.6.9]

I've taken a look at your .config for 2.6.10 and you don't have acpi
enabled (see below). Please try with acpi enabled


  parent reply	other threads:[~2004-12-23  9:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-22 17:31 Denis Vlasenko
2004-12-23 11:02 ` Denis Vlasenko
2004-12-23  9:12   ` William Lee Irwin III
2004-12-23 14:57     ` Denis Vlasenko
2004-12-23  9:33   ` Arnaud Patard [this message]
2004-12-23 16:11 Mikael Pettersson
2004-12-23 16:22 ` William Lee Irwin III
2004-12-23 16:59 Chuck Ebbert

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=m2u0qdgxzr.fsf@anduin.mandrakesoft.com \
    --to=apatard@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    --cc=wli@holomorphy.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

Powered by JetHome