[Fwd: Dual Celery on BP6]

Jason Jordan (guru@swami.pcguru.com.au)
Thu, 16 Dec 1999 18:56:33 +0800

This is a multi-part message in MIME format.
--------------B065428D91474C9A7258CBC9
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I posted this on alt.comp.periphs.mainboard.abit where someone suggested
I forward it to this list.

I don't actually read the list so if any further information is required
please email me.

Cheers, Jas

-- 
Jason D. Jordan                    Perth, Western Australia
www.e3.com.au  -   e3 technology   -  the way of the future
...less than 13 months til the start of the 3rd Millennium!
--------------B065428D91474C9A7258CBC9
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


X-Mozilla-Status2: 00000000
Message-ID: <3858B30B.5EA7E398@swami.pcguru.com.au>
Date: Thu, 16 Dec 1999 17:38:19 +0800
From: Jason Jordan <guru@swami.pcguru.com.au>
Reply-To: guru@swami.pcguru.com.au
X-No-Archive: Yes
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.13 i686)
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: alt.comp.periphs.mainboard.abit
Subject: Re: Dual Celery on BP6
References: <837p5o$t3c$1@the-fly.zip.com.au> <RQtYONVwbCD+16Aqq2+kb4VA6M80@4ax.com> <38581877.45E63209@inreach.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


"Christopher R. Carlen" wrote:


> It seems they run well with "normal" (effectively light) loading, but
> when Linux users and some BSD people tax the hell out of the system,
> they lock.
> 
> The verdict seems to still be out though, if this is a kernel or other
> SMP bug in the OS, or a BX chip overheat problem, a Cel bug, or the
> board.


I'm getting the lockup problems and have tried everything I've seen in
here.


Yesterday, hoping that the problem might be related to 2.2 kernels, I
compiled 2.3.33 and booted.


Apparently 2.3.33 starts logging APIC errors for the first time:


I saw the following over & pver until I locked up after about 40
minutes.


Dec 15 23:24:10 swami kernel: APIC error interrupt on CPU#0, should
never happen. 
Dec 15 23:24:10 swami kernel: ... APIC ESR0: 00000000 
Dec 15 23:24:10 swami kernel: ... APIC ESR1: 00000008 
Dec 15 23:24:10 swami kernel: ... bit 3: APIC Receive Accept Error. 
Dec 15 23:24:55 swami kernel: APIC error interrupt on CPU#1, should
never happen. 
Dec 15 23:24:55 swami kernel: ... APIC ESR0: 00000000 
Dec 15 23:24:55 swami kernel: ... APIC ESR1: 00000008 
Dec 15 23:24:55 swami kernel: ... bit 3: APIC Receive Accept Error. 
Dec 15 23:25:15 swami kernel: APIC error interrupt on CPU#0, should
never happen. 
Dec 15 23:25:15 swami kernel: ... APIC ESR0: 00000008 
Dec 15 23:25:15 swami kernel: ... APIC ESR1: 0000000a 
Dec 15 23:25:15 swami kernel: ... bit 1: APIC Receive CS Error (hw
problem). 
Dec 15 23:25:15 swami kernel: ... bit 3: APIC Receive Accept Error. 
Dec 15 23:26:12 swami kernel: APIC error interrupt on CPU#1, should
never happen. 
Dec 15 23:26:12 swami kernel: ... APIC ESR0: 00000008 
Dec 15 23:26:12 swami kernel: ... APIC ESR1: 0000000a 
Dec 15 23:26:12 swami kernel: ... bit 1: APIC Receive CS Error (hw
problem). 
Dec 15 23:26:12 swami kernel: ... bit 3: APIC Receive Accept Error. 


This system is a Dual Celeron 400 - not overclocked - at 2.0v.  I also
tried 2.1v.


It is not overheating as I have the i2c stuff installed and can monitor
temperatures.


It seems to me that this is demonstrating a *real* hardware fault.


Least we have somewhere to start.


Cheers, Jas



-- 
Jason D. Jordan                    Perth, Western Australia
www.e3.com.au  -   e3 technology   -  the way of the future
...less than 13 months til the start of the 3rd Millennium!


--------------B065428D91474C9A7258CBC9--




-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/