From mboxrd@z Thu Jan  1 00:00:00 1970
From: cerise@armory.com
Subject: Re: Dual Core CPU on Abit NI8-Board
Date: Wed, 5 Apr 2006 09:57:01 -0700
Message-ID: <20060405165701.GA16152@boogeyman>
References: <200604050828.02444.f.vondaak@kpage.de> <20060405063941.GA16737@boogeyman> <200604050913.58378.f.vondaak@kpage.de>
Mime-Version: 1.0
Return-path: <linux-smp-owner@vger.kernel.org>
Content-Disposition: inline
In-Reply-To: <200604050913.58378.f.vondaak@kpage.de>
Sender: linux-smp-owner@vger.kernel.org
List-Id: <linux-smp.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: linux-smp@vger.kernel.org

On Wed, Apr 05, 2006 at 09:13:57AM +0200, Frank von Daak wrote:
> 
> I've build them myself with smp-support enabled. I've also tried a 
> debian-smp-kernel with the same behaviour...
 
   Well, so much for the easy answer 8) 
 
> >> My problem is, that a "cat /proc/cpuinfo" shows me just one cpu with one
> >> core. I've tested this with kernels 2.6.16.1 and 2.6.17-rc1 (x86 and
> >> x86_64)
> >>
> >> If I add the following line in my lilo.conf to the kernel, I can see both
> >> cpu's:
> >> append="pci=noacpi pci=routeirq noapic acpi=off"

   Probably the best step to take next is to take another pass through a kernel.
It seems like you have a lot of things built in which aren't necessary to boot
(your network card, for example).  I generally recommend putting as much as
possible into modules so that you can boot with the bare minimum of stuff.  If
it works that way, you can start slowly adding things and figure out with better
granularity what's causing it to freeze.
   You'll use a little more memory that way (modules load in on page boundaries,
so one could in theory be wasting n * ($PAGE_SIZE - 1) bytes in loading n
modules, but the flexibility is very well worth it when figuring out problems
like this.
   I have a few prejudices to begin with for your short list of what's causing
the box to die.  The first is DRI.  The second is one of the NFORCE drivers.
The fact that glxgears seems to trigger the problem and that I dislike DRI in
general sounds like a good place to start ; )

-Phil/CERisE