The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Kasper Sandberg <lkml@metanurb.dk>
To: Justin Mattock <justinmattock@gmail.com>
Cc: Jacek Luczak <difrost.kernel@gmail.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: BIOS bug, APIC version if 0 for CPU#0
Date: Tue, 22 Apr 2008 15:49:05 +0200	[thread overview]
Message-ID: <1208872145.14146.103.camel@localhost> (raw)
In-Reply-To: <dd18b0c30804212310h29938c02r86aaab49b327b550@mail.gmail.com>

On Tue, 2008-04-22 at 06:10 +0000, Justin Mattock wrote:
> On Tue, Apr 22, 2008 at 5:21 AM, Jacek Luczak <difrost.kernel@gmail.com> wrote:
> > Hi,
> >
> >
> >  > Hello;
> >  > with the latest git on a macbook the system can barely boot without
> >  > freezing, a work around for me at leat is either disable smp, or once
> >  > booted  turn on glxgears,or compiling the kernel i.g. when using the
> >  > processors I'm not receiving a freeze, only when everything starts
> >  > lowering down. in dmesg I'm noticing BIOS bug, APIC version is 0 for
> >  > CPU#0! fixing up to 0x10. (tell you're hw vendor) could this be the
> >  > reason for the system freezes?,
> >
> >  I don't think so. On my machine there's no freezes with latest git and:
> >  ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
> >  BIOS bug, APIC version is 0 for CPU#0! fixing up to 0x10. (tell your hw vendor)
> >  ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
> >  BIOS bug, APIC version is 0 for CPU#0! fixing up to 0x10. (tell your hw vendor)
> >
> >  I've got exactly the same messages.
> 
> Are you using a macbook aswell?
> 
> >
> >
> >  > also I didnt have a camera handy on me
> >  > but the screen spit out = Bug spinlock lockup on CPU#0
> >  > swapper/0. c17fa7c0 PID 0, comm: swapper not tainted.
> >
> >  Can you try to write down more of those bug messages?
> 
> Yeah,
> 
> >
> >
> >  > I dont have a problem disabling smp, except when I cat /proc/cpuinfo I
> >  > don't see anything about my cores.
> >
> >  What exactly you expect to see in /proc/cpuinfp while smp is disabled?
> 
> under smp I see cpu cores. disabling smp I dont see cpu cores, under
> cat /proc/cpuinfo.

well.. SMP is kindof support for multiple processors, be it in one
socket, or multiple sockets.. without SMP you will only be able to use 1
of your X cores.
> 
> 
> >
> >
> >  > I know this is a stupid question
> >  > but will it hurt the system if smp is disabled
> >  > for the macbook pro ati chipset.?
> >
> >  No it won't.
> >
> >  -Jacek
> >
> 
> Cool as long as the system Is o.k. disabling smp.
It is.. but with the limitations outlined above.
>   What about x86: PAT
> support is disabled. how do I enable this option?
> regards;
> 


  reply	other threads:[~2008-04-22 13:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-22  5:13 BIOS bug, APIC version if 0 for CPU#0 Justin Mattock
2008-04-22  5:21 ` Jacek Luczak
2008-04-22  6:10   ` Justin Mattock
2008-04-22 13:49     ` Kasper Sandberg [this message]
2008-04-22 14:36       ` Justin Mattock
2008-05-06 22:37         ` Rafael J. Wysocki
2008-05-06 22:46           ` Justin Mattock
2008-05-07  1:40           ` Gabriel C
2008-05-07  3:08             ` Justin Mattock
2008-05-07 21:47             ` Rafael J. Wysocki
2008-05-07 21:56               ` Justin Mattock

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=1208872145.14146.103.camel@localhost \
    --to=lkml@metanurb.dk \
    --cc=difrost.kernel@gmail.com \
    --cc=justinmattock@gmail.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