From owner-freebsd-stable@FreeBSD.ORG Sat Oct 14 04:40:17 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D9E516A403 for ; Sat, 14 Oct 2006 04:40:17 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF54743D45 for ; Sat, 14 Oct 2006 04:40:16 +0000 (GMT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost2.sentex.ca (8.13.8/8.13.8) with ESMTP id k9E4eGFI079798; Sat, 14 Oct 2006 00:40:16 -0400 (EDT) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.6/8.13.3) with ESMTP id k9E4eFpF050522 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 14 Oct 2006 00:40:15 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <7.0.1.0.0.20061014003259.165ea280@sentex.net> X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0 Date: Sat, 14 Oct 2006 00:38:19 -0400 To: Scott Long From: Mike Tancsa In-Reply-To: <45306837.4010100@samsco.org> References: <45244053.6030706@samsco.org> <20061005200552.GA80162@xor.obsecurity.org> <20061006023424.GA86250@xor.obsecurity.org> <7.0.1.0.0.20061014002001.124d6120@sentex.net> <45306837.4010100@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: Patch available for shared em interrupts (Re: em, bge, network problems survey.) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Oct 2006 04:40:17 -0000 At 12:31 AM 10/14/2006, Scott Long wrote: >Mike, > >I have a new patch that I hope addresses the actual bug, instead of >shuffling the timing. Would you be willing to test it? I can't >guarantee that it's safe for production use yet, though. It seems >to work, but it might set your dog on fire too. Yes, for sure as the box is just for testing mysql right now..... I dont think we will end up even using it in production as the whole MB runs insanely hot. ---Mike