>http://lkml.org/lkml/2003/5/18/64 (the problem we are having)
>on it's way out. Try running with 'noapic' to see if it's the IOAPIC or
>local APICs (my bet is on the IOAPIC which would be on your motherboard
>chipset)"
I have the same problem, throughout 2.6.11 to 2.6.13-rc1, maybe before.
I
On Tue, 19 Jul 2005, Piszcz, Justin wrote:
> Is my box/motherboard "on its way out" as well?
> Is there any additional tests I can run to debug the problem?
> Please cc me as I am not on the list.
Check the PSU.
Maciej
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
>From the archives:
---
http://lkml.org/lkml/2003/5/18/64 (the problem we are having)
The response to him:
"You're getting a lot of receive and send (checksum and accept) errors
and
as a result invalid vectors being sent to your processors, your APIC bus
is seeing a lot of data corrup
Andy Arvai wrote:
>
> Hi,
>
> I'm having IO-APIC errors with 2.4.4. I spent some time searching the
> web to understand more about this problem and I'm still not sure if
> it is a hardware problem on the motherboard or a problem with the
> kernel. I will try
Hi,
I'm having IO-APIC errors with 2.4.4. I spent some time searching the
web to understand more about this problem and I'm still not sure if
it is a hardware problem on the motherboard or a problem with the
kernel. I will try the noapic boot option, but are there any
patches that migh
On Sun, Apr 22, 2001 at 11:22:24AM +0200, Hermann Himmelbauer wrote:
> Karsten Keil wrote:
> >
> > I have here the same board with 2*233 MMX and don't see this kind of ISDN
> > error on recent 2.2 kernels, but got also lot of APIC errors with the
> > 2.3/2.4,
pp0 dialstate 0
> Jan 27 00:41:28 violin kernel: ippp0: dialing 2 194040...
> Jan 27 00:41:28 violin kernel: isdn: HiSax,ch0 cause: E001B
>
> Although there is no direct hint to an APIC problem, I read in several
> newsgroup articles that these two errors refer to APIC errors.
For the
hint to an APIC problem, I read in several
newsgroup articles that these two errors refer to APIC errors.
They system is still usable after such an error, only that eth0/isdn is
not accessible, even if I reload the modules. The only solution
is a reboot.
Well - some days ago I tried to switch to
Chris Wedgwood wrote:
>
> On Wed, Apr 18, 2001 at 09:27:12PM -0500, Rico Tudor wrote:
>
> Another problem area is ECC monitoring. I'm still waiting for
> info from ServerWorks, and so is Dan Hollis. Alexander Stohr has
> even submitted code to Jim Foster for approval, without evide
Another problem area is ECC monitoring. I'm still waiting for info from
ServerWorks, and so is Dan Hollis. Alexander Stohr has even submitted
code to Jim Foster for approval, without evident effect. I have 18GB of
RAM divided among five ServerWorks boxes, so the matter is not academic.
-
To uns
On Wed, Apr 18, 2001 at 03:21:17PM -0700, Dr. Kelsey Hudson wrote:
> Um... Looks like when you clock the BX-chipset out of spec (>100MHz FSB)
> you get the error. Since BX wasn't ever designed to be run at >100MHz
> these errors are *expected*.
No, the APIC errors also occ
> Er... I believe there was some discussion on l-k some while ago regarding a
> certain lack of forthcomingness by Serverworks and the resultant general
> flakiness of Linux support for their chipsets...
Serverworks stuff is pretty well supported now - they've been working to make
some stuff avai
On Wed, 18 Apr 2001 15:21:17 -0700 (PDT)
"Dr. Kelsey Hudson" <[EMAIL PROTECTED]> wrote:
*snip*
> You have a couple solutions: Upgrade the motherboard to one of the VIA
> 133MHz chipsets (I dont care for the VIA chipset so this really doesn't
> strike my fancy) or upgrade to that other Intel chip
Linux did not support; I created a fix and sent it to LKML. It worked
> perfectly, i.e. without the problems described below.
>
> Now, I have two iPIII-850, but I run into different kind of troubles:
> (a) The BIOS will sometimes not recognize the second CPU
> (b) Linux reports API
.
Now, I have two iPIII-850, but I run into different kind of troubles:
(a) The BIOS will sometimes not recognize the second CPU
(b) Linux reports APIC errors and occasionally stops to process IRQs on the
second CPU or crashes (2.4.x kernel).
Some details: DFI P2XBL/D, i440BX, BIOS Award
1: One line summary of the problem:
Logfile is full of APIC errors
2: Full description of the problem/report:
My logfile for kernel-errors is full of messages like that:
Mar 27 20:57:27 E-Werk kernel: APIC error on CPU0: 02(04)
Mar 27 20:57:27 E-Werk kernel: APIC error on CPU1: 08(08)
Mar 27
OK, talked with someone who knows a little more about this than i do.
According to him, one reason I may be getting these errors is due to the
fact that the HPT370 controller is using IRQ18 which falls in the APIC
extended IRQ range (16 - 31).
If this is a problem is there a work-around? I don't
First off, here's something from my dmesg.
mapped APIC to e000 (fee0)
mapped IOAPIC to d000 (fec0)
CALLIN, before setup_local_APIC().
ENABLING IO-APIC IRQs
...changing IO-APIC physical APIC ID to 2 ... ok.
init IO_APIC IRQs
IO-APIC (apicid-pin) 2-0, 2-9, 2-10, 2-11, 2-20, 2-21,
On Thu, 18 Jan 2001, Jorge Nerin wrote:
> > It's the first report of APIC errors on a P5 system I have seen, so it's
> > probably not a result of a bad motherboard design. I'd recommend to check
> > if the system doesn't get overheated. You may also
error might pass
> unnoticed leading to a system unstability under certain conditions. At
> such a low volume of errors double-bit ones are not likely to happen.
>
> It's the first report of APIC errors on a P5 system I have seen, so it's
> probably not a result of a
On Wed, 17 Jan 2001, Dominik Kubla wrote:
> Just switched to 2.4.0-ac9 (+crypto patches) on our Dual-Pentium MMX
> webserver yesterday. Works fine so far, except i keep seeing those
> APIC erros (about 14 in 12 hrs) indicating receive, send and CS errors.
Make sure your system is free of dust..
a low volume of errors double-bit ones are not likely to happen.
It's the first report of APIC errors on a P5 system I have seen, so it's
probably not a result of a bad motherboard design. I'd recommend to check
if the system doesn't get overheated. You may also be unlucky
Hi there.
I have a Dual Pentium-233MMX Machine, which throws lots of Errors like
this one:
Dec 5 10:56:04 tyr kernel: APIC error on CPU0: 02(00)
Dec 5 10:56:20 tyr kernel: APIC error on CPU0: 04(00)
The Machine has a Gigabyte 586DX Board with onboard SCSI (AIC7xxx),
ISA 3c509 Network Card,
Rogier Wolff wrote:
>
> > I have seen the same problem on the same motherboard. It appears to
> > be a motherboard bug that 2.4 exposes and 2.2 doesn't.
>
> This PRINT was added in 2.4.
>
> You're seeing noise on the apic lines. The APICs notice, but every now
> and then you may see a lockup d
H. Peter Anvin wrote:
> Followup to: <[EMAIL PROTECTED]>
> By author:Bernhard Rosenkraenzer <[EMAIL PROTECTED]>
> In newsgroup: linux.dev.kernel
> >
> > Hi,
> > after booting a 2.4.0 (any testx-release I've tried so far, including
> > test11-pre2) on a Dual-Pentium III box, the system works o
Followup to: <[EMAIL PROTECTED]>
By author:Bernhard Rosenkraenzer <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> Hi,
> after booting a 2.4.0 (any testx-release I've tried so far, including
> test11-pre2) on a Dual-Pentium III box, the system works ok, but the
> console gets filled wit
Hi,
after booting a 2.4.0 (any testx-release I've tried so far, including
test11-pre2) on a Dual-Pentium III box, the system works ok, but the
console gets filled with
APIC error on CPU0: 08(08)
every couple of seconds, occasionally some lines in between say
APIC error on CPU0: 08(02)
and
API
Seth R Arnold wrote:
[...]
> APIC error on CPU1: 02(02)
> APIC error on CPU1: 02(08)
[...]
> Is this something I should be worried about?
No. The APIC retries the stuff that go wrong, so all
you get is a very slight performance degradation.
Nothing to worry about unless it happens hundreds of
tim
Greetings everyone.
I have been running Linux kernel 2.4.0-test7 for some time now on my
dual celeron (BP6) system. I have an AGP video card, one ethernet card,
one IDE sound card, ps/2 keyboard and mouse, and two IDE hard drives.
(No floppy, no CD.)
I get errors of this sort on a regular basis
29 matches
Mail list logo
