Date: Wed, 23 Nov 2005 08:48:15 -0500 From: John Baldwin <jhb@freebsd.org> To: freebsd-current@freebsd.org Cc: Massimo Lusetti <massimo@cedoc.mo.it>, Kris Kennaway <kris@obsecurity.org> Subject: Re: em interrupt storm Message-ID: <200511230848.16963.jhb@freebsd.org> In-Reply-To: <1132736116.4305.8.camel@massimo.datacode.it> References: <20051123030304.GA84202@xor.obsecurity.org> <20051123083118.GA90686@xor.obsecurity.org> <1132736116.4305.8.camel@massimo.datacode.it>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 23 November 2005 03:55 am, Massimo Lusetti wrote: > On Wed, 2005-11-23 at 03:31 -0500, Kris Kennaway wrote: > > Maybe it'll be OK if you disable the onboard NIC and use a different > > one. > > Sure, I'll try that, did you have any suggestion for the replacement > nic? > > And do you think something could change if the arch is 64bit? > http://www.supermicro.com/products/system/2U/6024/SYS-6024H-82R.cfm No, I've seen the same interrupt aliasing with a FreeBSD/amd64 kernel. Giv= en=20 that FreeBSD/i386 and FreeBSD/amd64 have nearly identical interrupt code th= is=20 is to be expected. =2D-=20 John Baldwin <jhb@FreeBSD.org> =A0<>< =A0http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =A0=3D =A0http://www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200511230848.16963.jhb>