Date: 12 Jun 2004 01:25:28 +0200 From: "Arno J. Klaassen" <arno@heho.snv.jussieu.fr> To: Stijn Hoop <stijn@win.tue.nl> Cc: freebsd-current@freebsd.org Subject: Re: lockups Message-ID: <wp1xklhe3b.fsf@heho.snv.jussieu.fr> In-Reply-To: <20040611222951.GA45873@pcwin002.win.tue.nl> References: <40A43E86.6040504@sbcglobal.net> <200405250831.20795.jhb@FreeBSD.org> <40B3D034.1000308@sbcglobal.net> <200405261040.33384.jhb@FreeBSD.org> <40B5339F.7090709@sbcglobal.net> <20040527202315.L10115@gamplex.bde.org> <20040611222951.GA45873@pcwin002.win.tue.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Hoi, > Hi, > > On Thu, May 27, 2004 at 09:08:58PM +1000, Bruce Evans wrote: > > Interesting. It seems that the problems handling nForce2 APICs are mainly > > in FreeBSD. My A7N8X-E system behaves similarly, except I fixed the > > interrupt storm detection in -current so that the system is almost > > usable. > > While installing FreeBSD on my new & shiny A7N8X-Deluxe I also ran into > this problem. Enabling the APIC triggers an interrupt storm on IRQ's > 16. > While -CURRENT at least boots (an older -CURRENT that I first tried to > install hung after determining the TSC), it still is unusable over the > network because the built-in xl0 keeps getting watchdog timeout's (it's > at irq20). I worked around this problem by assiging a free irq in the BIOS (MB A7N266, not a A7N8, dunno if the A7N8 BIOS gives you this possibility) > Disabling the APIC in the BIOS works around the problem (ACPI still enabled), > but unfortunately Windows won't boot in that case :/ xl0 is rock-solid since with APIC and ACPI enabled YMMV, Arno NB, I still get the interrupt storm on irq7 when attaching a scratch P200 notebook by plip ... NB-II, for Windows I use Samba and whatever I find a PC thrown on the street; but then, I dont like computer games ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?wp1xklhe3b.fsf>