Date: Tue, 27 Jan 2004 07:40:04 -0800 (PST) From: dada@sbox.tugraz.at To: freebsd-bugs@FreeBSD.org Subject: Re: kern/61733: panic: resource_list_release: resource entry is not busy Message-ID: <200401271540.i0RFe4Ew083330@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/61733; it has been noted by GNATS. From: dada@sbox.tugraz.at To: Andy Farkas <andyf@speednet.com.au> 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 <andyf@speednet.com.au>: > 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 > > <http://www.freebsd.org/cgi/query-pr.cgi?pr=3D20803>; > The PR you cited (as well as <a href=3D"http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/18200">PR kern/18200</a>) 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 <a href=3D"http://www.freebsd.org/cgi/query-pr.cgi?pr=3Di386/26344">PR i386/26344</a>, 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200401271540.i0RFe4Ew083330>