Date: Wed, 23 Nov 2005 18:56:15 -0700 From: Scott Long <scottl@samsco.org> To: Darren Pilgrim <dmp@bitfreak.org> Cc: freebsd-current@freebsd.org Subject: Re: em interrupt storm Message-ID: <43851DBF.9060702@samsco.org> In-Reply-To: <000401c5f099$f1ae1f30$642a15ac@smiley> References: <000401c5f099$f1ae1f30$642a15ac@smiley>
next in thread | previous in thread | raw e-mail | index | archive | help
Darren Pilgrim wrote: > From: Scott Long [mailto:scottl@samsco.org] > >>Darren Pilgrim wrote: >> >>>Until this gets "fixed" in FreeBSD, what should those of us who are >>>effectively stuck with this hardware do to avoid the problem? >> >>What I've done is vacated the use of irq16 on my machines by disabling >>things like usb and if_em. > > > Do the devices have to be really turned off (meaning disabled in the BIOS) > or do I just not load the corresponding driver? I think that either works. > > If nothing is using irq16, does the aliasing not occur or does it just > become transparent to FreeBSD? > > If no drivers request a particular interrupt vector, then it gets masked. The chipset probably still tries to deliver the interrupt, but it never makes it to the CPU and thus is transparent. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43851DBF.9060702>