All of lore.kernel.org
 help / color / mirror / Atom feed
From: Earle Nietzel <earle.nietzel@rhinobox.org>
To: Tim Day <timday@bottlenose.demon.co.uk>
Cc: linux-smp@vger.kernel.org
Subject: Re: Gigabyte 6VXDC7 mobo (Via 694X chipset) SMP instability
Date: Wed, 04 May 2005 22:23:16 -0400	[thread overview]
Message-ID: <42798394.8020302@rhinobox.org> (raw)
In-Reply-To: <1115238927.6560.36.camel@basecamp.bottlenose.demon.co.uk>

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"?

> 
> Googling around, there seem to be plenty of reports of similar behaviour
> in 694X systems, but little in the way of definite solutions (with the
> possible exception of someone who claimed to have fixed it by lowering a
> voltage setting in their BIOS; my board's BIOS doesn't my give any
> control of that unfortunately).
> 
> Anyway, my question is this: is this chipset simply broken at the
> hardware level (and I should just resign myself to uniprocessing) or is
> there is some cunning combination of boot options and/or kernel compile
> flag gnosis which will let me SMP with confidence ?
> 
> Thanks for any advice
> Tim
> 


  reply	other threads:[~2005-05-05  2:23 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 [this message]
2005-05-06  7:48   ` Tim Day
2005-05-07 21:22     ` Earle Nietzel
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=42798394.8020302@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.