Date: Mon, 28 Nov 2005 16:19:52 -0800 From: Julian Elischer <julian@elischer.org> To: John Baldwin <jhb@freebsd.org> Cc: Kris Kennaway <kris@obsecurity.org>, freebsd-current@freebsd.org, Darren Pilgrim <dmp@bitfreak.org> Subject: Re: em interrupt storm Message-ID: <438B9EA8.60703@elischer.org> In-Reply-To: <200511281626.33591.jhb@freebsd.org> References: <43842D41.1050401@samsco.org> <002801c5f081$f01ff200$642a15ac@smiley> <20051124062711.GA15961@xor.obsecurity.org> <200511281626.33591.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin wrote: >On Thursday 24 November 2005 01:27 am, Kris Kennaway wrote: > > >>On Wed, Nov 23, 2005 at 03:02:05PM -0800, 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? Does the >>>problem exist in RELENG_4? >>> >>> >>Yes, on the same machine I first mentioned. >> >> > >This is the first I've heard that the problem occurs on 4.x as well. :( > > As I said, I think it's hitting me on a dell 2850 running 4.10++ as well. and Matt is getting hit with it in dragonfly with 4.x roots.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?438B9EA8.60703>