From owner-freebsd-bugs@FreeBSD.ORG Tue Jan 27 07:38:15 2004 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8DA6416A4CE; Tue, 27 Jan 2004 07:38:15 -0800 (PST) Received: from mailrelay01.tugraz.at (mailrelay.tu-graz.ac.at [129.27.3.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id F2A4943D39; Tue, 27 Jan 2004 07:38:10 -0800 (PST) (envelope-from dada@sbox.tugraz.at) Received: from localhost (webmail02.tu-graz.ac.at [129.27.3.144]) i0RFc8Bd005872; Tue, 27 Jan 2004 16:38:08 +0100 (CET) Received: from ABRZ205.kfunigraz.ac.at (ABRZ205.kfunigraz.ac.at ; Tue, 27 Jan 2004 16:38:08 +0100 Message-ID: <20040127163808.qzcg88444ggsw04k@webmail.tugraz.at> X-Priority: 3 (Normal) Date: Tue, 27 Jan 2004 16:38:08 +0100 From: dada@sbox.tugraz.at To: Andy Farkas MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) 4.0-cvs X-Originating-IP: 143.50.106.205 X-Organization: Graz University of Technology / Austria X-Scanned-By: MIMEDefang 2.39 cc: freebsd-bugs@freebsd.org cc: freebsd-gnats-submit@freebsd.org 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 List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jan 2004 15:38:15 -0000 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.