From: Alistair J Strachan <alistair@devzero.co.uk>
To: Clock <clock@twibright.com>, kenton.groombridge@us.army.mil
Cc: linux-kernel@vger.kernel.org
Subject: Re: nforce2 lockups
Date: Fri, 15 Aug 2003 17:38:08 +0100 [thread overview]
Message-ID: <200308151738.08965.alistair@devzero.co.uk> (raw)
In-Reply-To: <20030815171521.A683@beton.cybernet.src>
On Friday 15 August 2003 16:15, Clock wrote:
> On Fri, Aug 15, 2003 at 09:12:17PM +0900, kenton.groombridge@us.army.mil
wrote:
> > Hi,
> >
> > I found your post looking for a solution to my lockups. I bet if you do
> > a dmesg, you will find that your nforce2 chipset revision is 162.
>
> Yeah! Look:
>
> NFORCE2: chipset revision 162
[alistair] 05:37 PM [~] dmesg | grep "NFORCE2: chipset"
NFORCE2: chipset revision 162
A quick google for "NFORCE2: chipset revision" reveals no chipset revision
dmesg except 162. It seems likely most manufactures are using the same
revision.
I use APIC and ACPI on my EPoX 8RDA+, and I've never had any IO problems. So
it seems unlikely that it is tied to a chipset revision.
[snip]
>
> It looks like the problem is in APIC. When you disable it, it vanishes.
> And, when you enable NMI watchdog, which is handled by APIC,
> it doesn't work - it couts up to 15 in /proc/interrupts and then stops!
I have not noticed any such APIC issues.
[alistair] 05:36 PM [~] uname -r
2.6.0-test3-mm2
[alistair] 05:37 PM [~] cat /proc/interrupts
CPU0
0: 4582940 XT-PIC timer
1: 22830 IO-APIC-edge i8042
2: 0 XT-PIC cascade
4: 340689 IO-APIC-edge serial
7: 4881 IO-APIC-edge parport0
8: 1 IO-APIC-edge rtc
9: 0 IO-APIC-level acpi
14: 12942 IO-APIC-edge ide0
15: 10 IO-APIC-edge ide1
16: 4 IO-APIC-level bttv0
19: 504114 IO-APIC-level EMU10K1, nvidia
20: 45043 IO-APIC-level ohci-hcd
21: 0 IO-APIC-level ehci_hcd
22: 82 IO-APIC-level ohci-hcd
NMI: 0
LOC: 4582946
ERR: 0
MIS: 0
Sounds suspiciously like software to me.
Cheers,
Alistair.
next prev parent reply other threads:[~2003-08-15 16:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <df962fdf9006.df9006df962f@us.army.mil>
2003-08-15 15:15 ` nforce2 lockups Clock
2003-08-15 16:38 ` Alistair J Strachan [this message]
2003-08-15 19:06 ` Clock
2003-08-15 17:47 ` Alistair J Strachan
2003-08-15 21:15 ` Clock
2003-08-17 19:27 ` Jussi Laako
2003-08-17 20:02 ` Patrick Dreker
2003-08-18 13:28 ` Pavel Machek
[not found] <fa.ih2vscq.35m1rs@ifi.uio.no>
[not found] ` <fa.gbe06ic.1ki851c@ifi.uio.no>
2003-08-17 13:00 ` walt
[not found] <20030817233306.CC67A2D0074@beton.cybernet.src>
2003-08-17 23:41 ` Karel Kulhavý
2003-08-18 8:04 kenton.groombridge
2003-08-18 9:31 ` Ookhoi
2003-08-18 11:00 ` Karel Kulhavý
-- strict thread matches above, loose matches on Subject: below --
2003-08-21 1:39 kenton.groombridge
2003-08-21 11:05 ` Patrick Dreker
2003-08-23 1:41 kenton.groombridge
2003-08-23 12:20 Mikael Pettersson
2003-08-23 12:48 ` Patrick Dreker
2003-08-23 15:50 Mikael Pettersson
2003-08-23 18:52 ` Patrick Dreker
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=200308151738.08965.alistair@devzero.co.uk \
--to=alistair@devzero.co.uk \
--cc=clock@twibright.com \
--cc=kenton.groombridge@us.army.mil \
--cc=linux-kernel@vger.kernel.org \
/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.