From owner-freebsd-current@FreeBSD.ORG Tue Nov 29 00:20:25 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 257DB16A432; Tue, 29 Nov 2005 00:20:25 +0000 (GMT) (envelope-from julian@elischer.org) Received: from delight.idiom.com (outbound.idiom.com [216.240.47.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8EEF043D73; Tue, 29 Nov 2005 00:20:07 +0000 (GMT) (envelope-from julian@elischer.org) Received: from idiom.com (idiom.com [216.240.32.1]) by delight.idiom.com (Postfix) with ESMTP id F413022956C; Mon, 28 Nov 2005 16:20:00 -0800 (PST) Received: from [10.251.23.117] (nat.ironport.com [63.251.108.100]) by idiom.com (8.12.11/8.12.11) with ESMTP id jAT0K0R9073182; Mon, 28 Nov 2005 16:20:00 -0800 (PST) (envelope-from julian@elischer.org) Message-ID: <438B9EA8.60703@elischer.org> Date: Mon, 28 Nov 2005 16:19:52 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.11) Gecko/20050727 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <43842D41.1050401@samsco.org> <002801c5f081$f01ff200$642a15ac@smiley> <20051124062711.GA15961@xor.obsecurity.org> <200511281626.33591.jhb@freebsd.org> In-Reply-To: <200511281626.33591.jhb@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Kris Kennaway , freebsd-current@freebsd.org, Darren Pilgrim Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Nov 2005 00:20:25 -0000 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.