From: Phillip Susi <psusi@cfl.rr.com>
To: konstantin.sharlaimov@gmail.com
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.22.1: Enabling IO-APIC = APIC error on CPU0: 40(40)
Date: Tue, 18 Sep 2007 13:39:04 -0400 [thread overview]
Message-ID: <46F00D38.8090002@cfl.rr.com> (raw)
In-Reply-To: <1190034991.8152.14.camel@traveler>
Konstantin Sharlaimov wrote:
> I agree, this is probably somehow related with SiS chipset - my laptop
> has one of these SiS 760 host controllers inside.
>
> I'll probably do some digging to figure out if this is indeed chipset
> related. I wonder if this error occurs under Windows (Win does not
> report much, yet it's kernel must be aware of such error).
Windows does not use IO-APICs AFAIK.
prev parent reply other threads:[~2007-09-18 17:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-14 12:09 2.6.22.1: Enabling IO-APIC = APIC error on CPU0: 40(40) Justin Piszcz
2007-09-17 13:07 ` Konstantin Sharlaimov
2007-09-17 13:10 ` Justin Piszcz
2007-09-17 13:16 ` Konstantin Sharlaimov
2007-09-18 17:39 ` Phillip Susi [this message]
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=46F00D38.8090002@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=jpiszcz@lucidpixels.com \
--cc=konstantin.sharlaimov@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