From: Earle Nietzel <earle.nietzel@rhinobox.org>
To: Tim Day <timday@bottlenose.demon.co.uk>, linux-smp@vger.kernel.org
Subject: Re: Gigabyte 6VXDC7 mobo (Via 694X chipset) SMP instability
Date: Sat, 07 May 2005 17:22:11 -0400 [thread overview]
Message-ID: <427D3183.4030807@rhinobox.org> (raw)
In-Reply-To: <1115365709.4740.17.camel@basecamp.bottlenose.demon.co.uk>
Tim Day wrote:
> On Wed, 2005-05-04 at 22:23 -0400, Earle Nietzel wrote:
>
>>Tim Day wrote:
>>
>>>I have a machine with a Gigabyte 6VXDC7 mobo (Via 694X chipset) with a
>>>pair of 933MHz P3s and a couple of GB of RAM. I run Debian Sarge's
>>>stock -686-smp kernels (2.4 series or more recently 2.6.8).
>>>
>>>With a "nosmp" boot option (or using uniprocessor kernels) the box is
>>>rock solid. But when I run in SMP mode it generates sporadic
>>> "APIC error on CPUx: 0y(0z)"
>>>type messages, generally in pairs, every few minutes (or several per
>>>minute with the 2.6.8 kernel without a "noapic" boot option).
>>>Eventually the machine invariably locks up hard with no warning after an
>>>uptime of on the order of a few minutes or a few days (depending on
>>>kernel version, boot options, load and luck). I've tried just about
>>>every possible combination of BIOS settings and boot options, memchecked
>>>the RAM, rearranged PCI cards and upgraded the PSU. Nothing seems to
>>>help; the only way to get complete stability seems to be "nosmp" or a
>>>non-SMP kernel.
>>
>>Have you tried using "noapic"?
>
>
> Oh yes.
> It has the expected effect on /proc/interrupts:
> IO-APIC-edge/-level interrupts spread over both CPUs change
> into XT-PIC interrupts on CPU0 only.
> Nevertheless, the steady stream of "APIC error" kernel messages remains.
I remember the ABIT BP6 motherboards having a similar problem but it was
because one of the cpu's had a voltage difference large enough to cause
this type of error (though there were no stability issues).
>
> Is it possible to build an SMP kernel with the APIC hardware completely
> ignored/disabled (to an even greater extent than with "noapic"), or is
> the APIC hardware needed for some crucial aspect of inter-CPU
> communication ?
I pretty sure that is not possible. The "noapic" option often solved
problems on some buggy motherboards.
There does come to mind one other thing you might try and that is in
your BIOS if you can change the SMP compatibility between "MP 1.1" or
"MP 1.4". If you have this option try it out.
>
> Tim
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-smp" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
next prev parent reply other threads:[~2005-05-07 21:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-04 20:35 Gigabyte 6VXDC7 mobo (Via 694X chipset) SMP instability Tim Day
2005-05-05 2:23 ` Earle Nietzel
2005-05-06 7:48 ` Tim Day
2005-05-07 21:22 ` Earle Nietzel [this message]
2005-05-09 20:38 ` Tim Day
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=427D3183.4030807@rhinobox.org \
--to=earle.nietzel@rhinobox.org \
--cc=linux-smp@vger.kernel.org \
--cc=timday@bottlenose.demon.co.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.