From: Ross Dickson <ross@datscreative.com.au>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: recbo@nishanet.com, linux-kernel@vger.kernel.org
Subject: Re: Fwd: Re: Working nforce2, was Re: Fixes for nforce2 hard lockup, apic, io-apic, udma133 covered
Date: Tue, 16 Dec 2003 00:30:30 +1000 [thread overview]
Message-ID: <200312160030.30511.ross@datscreative.com.au> (raw)
>> APIC error on CPU0: 02(02)
> > what?? no crash though.
> [...]
> > bob@where cat /proc/interrupts
> > CPU0
> > 0: 3350153 IO-APIC-edge timer
> > 1: 5775 IO-APIC-edge i8042
> > 2: 0 XT-PIC cascade
> > 8: 1 IO-APIC-edge rtc
> > 9: 0 IO-APIC-level acpi
> > 12: 5385 IO-APIC-edge i8042
> > 14: 10 IO-APIC-edge ide0
> > 15: 10 IO-APIC-edge ide1
> > 16: 1717957 IO-APIC-level ide2, ide3, eth0
> > 19: 472929 IO-APIC-level ide4, ide5
> > 21: 0 IO-APIC-level NVidia nForce2
> > NMI: 822
> > LOC: 3350073
> > ERR: 35
> > MIS: 15818
>It looks like the infamous APIC delivery bug -- the "MIS" counter shows
>how many level-triggered interrupts has been erronously delivered as
>edge-triggered ones. No wonder the system shows instability -- you have
>noise problems at the APIC bus.
Thanks Maciej
I was wondering about those, I had seen the work around code and would not
have thought it need apply to recent athlon chipsets?
For comparison here is my proc/interrupts
CPU0
0: 50462204 IO-APIC-edge timer
1: 49153 IO-APIC-edge keyboard
2: 0 XT-PIC cascade
9: 0 IO-APIC-level acpi
12: 395912 IO-APIC-edge PS/2 Mouse
14: 995872 IO-APIC-edge ide0
15: 283 IO-APIC-edge ide1
16: 3921102 IO-APIC-level nvidia
18: 2 IO-APIC-level bttv
20: 136325 IO-APIC-level eth0, usb-ohci
21: 146903 IO-APIC-level ehci_hcd, NVIDIA nForce Audio
22: 0 IO-APIC-level usb-ohci
NMI: 0
LOC: 50457798
ERR: 0
MIS: 0
Albatron KM18G-Pro, nforce2, pheonix bios, 2200XP, 255fsb, ddr400,
ide0 is hard drive, ide1 is cdrom, nmi watchdog off
Report seems OK but this machine locks up hard without the apic delay patch.
I am currently trying the simpler v1 (always add a delay) patch but on all apic
acks as per this posting
http://linux.derkeiler.com/Mailing-Lists/Kernel/2003-12/3291.html
which is a reply to an earlier posting of the same name but I accidently
omitted the Re in the subject.
Regards,
Ross.
next reply other threads:[~2003-12-15 14:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-15 14:30 Ross Dickson [this message]
2003-12-15 15:02 ` Fwd: Re: Working nforce2, was Re: Fixes for nforce2 hard lockup, apic, io-apic, udma133 covered Craig Bradney
2003-12-15 15:56 ` Maciej W. Rozycki
2003-12-15 16:54 ` Ross Dickson
2003-12-16 6:07 ` Bob
[not found] <200312132040.00875.ross@datscreative.com.au>
2003-12-13 12:00 ` Fwd: " Bob
2003-12-15 13:11 ` Maciej W. Rozycki
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=200312160030.30511.ross@datscreative.com.au \
--to=ross@datscreative.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@ds2.pg.gda.pl \
--cc=recbo@nishanet.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox