Date: Fri, 07 May 2004 07:18:47 +0300 From: Petri Helenius <pete@he.iki.fi> To: Scott Long <scottl@freebsd.org> Cc: John Polstra <jdp@polstra.com> Subject: Re: em(4) problems. Message-ID: <409B0E27.5010203@he.iki.fi> In-Reply-To: <409AA44B.9010404@freebsd.org> References: <XFMail.20040505115403.jdp@polstra.com> <409938F7.2090603@DeepCore.dk> <409A8675.3080102@he.iki.fi> <409A92FA.6080104@DeepCore.dk> <409AA44B.9010404@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Scott Long wrote: > > I'm looking a t a similar system right now and it definitely looks > like an interrupt routing problem, not a driver problem. The > interesting thing is that (with 5.2-current as of two days ago) > disabling neither > ACPI nor APIC helps. I guess that we might want to get John Baldwin > involved. > I´ve also seen BIOS images which contain different information for interrupt routings for mptable and ACPI. Thankfully the vendor was quick to rectify that. Disabling APIC and HTT in the BIOS worked around the issues in my case but did not produce the performance I was looking for. Pete
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?409B0E27.5010203>