From owner-freebsd-bugs@FreeBSD.ORG Fri Apr 27 17:40:14 2007 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 32E2116A400 for ; Fri, 27 Apr 2007 17:40:14 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 260E513C457 for ; Fri, 27 Apr 2007 17:40:14 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l3RHeD2J059290 for ; Fri, 27 Apr 2007 17:40:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l3RHeD1t059286; Fri, 27 Apr 2007 17:40:13 GMT (envelope-from gnats) Date: Fri, 27 Apr 2007 17:40:13 GMT Message-Id: <200704271740.l3RHeD1t059286@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: John Hood Cc: Subject: Re: kern/94196: [dc] if_dc panics on bad hardware X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John Hood List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Apr 2007 17:40:14 -0000 The following reply was made to PR kern/94196; it has been noted by GNATS. From: John Hood To: Gleb Smirnoff Cc: Gavin Atkinson , bug-followup@FreeBSD.org, cgull@glup.org, marius@FreeBSD.org Subject: Re: kern/94196: [dc] if_dc panics on bad hardware Date: Fri, 27 Apr 2007 13:37:39 -0400 On Thu, Apr 26, 2007 at 07:00:16PM +0400, Gleb Smirnoff wrote: > On Thu, Apr 26, 2007 at 03:01:02PM +0100, Gavin Atkinson wrote: > G> This appears to have been fixed by glebius in src/sys/dev/dc/if_dc.c > G> 1.185, although there was no plan to MFC it mentioned in the commit. > G> Gleb, is this worth MFCing so that this PR can be closed? > > It was already MFC'ed by marius in revision 1.160.2.12. > > Can you please confirm, that fresh RELENG_6 doesn't panic? Sorry to not respond earlier, I was out yesterday. Sorry-- as I said, the bug depended on an unseated connector, now reseated, that would be hard to reproduce. I can't reproduce the machine's config anyway. I agree that the bug appears to be fixed after inspecting the code. --jh