From: Andi Kleen <ak@suse.de>
To: Vladimir Dvorak <dvorakv@vdsoft.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: APIC error on CPUx
Date: Mon, 22 May 2006 14:03:16 +0200 [thread overview]
Message-ID: <200605221403.16464.ak@suse.de> (raw)
In-Reply-To: <4471A777.2020404@vdsoft.org>
On Monday 22 May 2006 13:58, Vladimir Dvorak wrote:
> Andi Kleen wrote:
>
> >Vladimir Dvorak <dvorakv@vdsoft.org> writes:
> >
> >
> >>Linux requisities:
> >>Debian 3.1
> >>Linux mailserver 2.6.8-3-686-smp #1 SMP Thu Feb 9 07:05:39 UTC 2006 i686
> >>
> >>
> >
> >That's an ancient kernel.
> >
> >
> Yes, I agree.
>
> ... but the latest in Debian/Sarge. :-)
>
> Do you, Andi, thing that upgrade to latest vanilla one ( from
> kernel.org ) should solve this problem ?
Probably not.
>
> >
> >
> >>GNU/Linux
> >>
> >>Hardware:
> >>Intel SR1200
> >>
> >>
> >
> >If it's an <=P3 class machine: most likely you have noise on the APIC bus.
> >
> >-Andi
> >
> >
> >
> Yes, you are right :
>
> cat /proc/cpuinfo
> ...
> model name : Intel(R) Pentium(R) III CPU family 1133MHz
> ...
>
>
> "Noise on APIC bus" means - " a lot of interrupts from devices" ?
Usually a crappy/broken/misdesigned motherboard.
-Andi
next prev parent reply other threads:[~2006-05-22 12:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-22 7:38 APIC error on CPUx Vladimir Dvorak
2006-05-22 11:15 ` Andi Kleen
2006-05-22 11:58 ` Vladimir Dvorak
2006-05-22 12:03 ` Andi Kleen [this message]
2006-05-22 12:19 ` Vladimir Dvorak
2006-05-22 12:31 ` Jan Engelhardt
2006-05-22 12:54 ` Andi Kleen
2006-05-22 13:13 ` Xavier Bestel
2006-05-22 19:44 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2006-05-24 5:15 Brown, Len
2006-05-24 8:10 ` Mikael Pettersson
2006-05-23 20:16 Brown, Len
2006-05-23 20:37 ` Vladimir Dvorak
2006-05-25 11:51 ` Jan Engelhardt
2006-05-22 14:47 Brown, Len
2006-05-22 14:50 ` Andi Kleen
2006-05-23 6:44 ` Vladimir Dvorak
2002-01-13 12:51 Teodor Iacob
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=200605221403.16464.ak@suse.de \
--to=ak@suse.de \
--cc=dvorakv@vdsoft.org \
--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