From owner-freebsd-bugs@FreeBSD.ORG Tue Jan 27 07:40:37 2004 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3161916A4CE for ; Tue, 27 Jan 2004 07:40:37 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5669943D6D for ; Tue, 27 Jan 2004 07:40:15 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i0RFe4FR083331 for ; Tue, 27 Jan 2004 07:40:04 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i0RFe4Ew083330; Tue, 27 Jan 2004 07:40:04 -0800 (PST) (envelope-from gnats) Date: Tue, 27 Jan 2004 07:40:04 -0800 (PST) Message-Id: <200401271540.i0RFe4Ew083330@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: dada@sbox.tugraz.at Subject: Re: kern/61733: panic: resource_list_release: resource entry is not busy X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: dada@sbox.tugraz.at List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jan 2004 15:40:37 -0000 The following reply was made to PR kern/61733; it has been noted by GNATS. From: dada@sbox.tugraz.at To: Andy Farkas Cc: freebsd-bugs@freebsd.org, freebsd-gnats-submit@freebsd.org Subject: Re: kern/61733: panic: resource_list_release: resource entry is not busy Date: Tue, 27 Jan 2004 16:38:08 +0100 Zitat von Andy Farkas : > It seems this problem is fairly old and FreeBSD has been doing it since 4.= 1. > > This PR is a duplicate of PR i386/20803 > > > The PR you cited (as well as PR kern/18200) report a nuisance, this one is about a real showstopper. The cause seems the same, but the symptom is fatal now in FreeBSD 5. The suggestion to use 3c5x9cfg.exe will likely solve my problem (see PR i386/26344, I have not tried it yet) but I won=B4t report it here to hav= e this PR closed too. I do not care much about a misleading device probe message, but imho the panic should be fixed (or this problem added to the errata or hardware notes.) These old cards are not that exotic, people will stumble over this again and again.