Date: Thu, 2 Oct 2003 08:50:19 -0700 (PDT) From: =?ISO-8859-1?Q?Mikko_Ty=F6l=E4j=E4rvi?= <mbsd@pacbell.net> To: freebsd-emulation@FreeBSD.org Subject: Re: ports/57465 kldunload rtc.ko causes a panic; yet it's in rc.d script Message-ID: <200310021550.h92FoJNF016776@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/57465; it has been noted by GNATS.
From: =?ISO-8859-1?Q?Mikko_Ty=F6l=E4j=E4rvi?= <mbsd@pacbell.net>
To: freebsd-gnats-submit@FreeBSD.org, w@expro.pl
Cc:
Subject: Re: ports/57465 kldunload rtc.ko causes a panic; yet it's in rc.d
script
Date: Thu, 2 Oct 2003 08:45:19 -0700 (PDT)
I ran into this some time ago, and found that you get different
results depending on whether the device has been opened or not.
Have you tried kldunloading "rtc" w/o using it first, e.g. directly
after boot?
I've been using the following patch for a while:
--- rtc.c.org Wed Aug 20 20:41:50 2003
+++ rtc.c Thu Oct 2 08:40:37 2003
@@ -299,7 +299,8 @@
DLog(Lfail, "%p busy", sc);
return error;
}
- destroy_dev(rtc_dev);
+ if (sc == NULL)
+ destroy_dev(rtc_dev);
#if __FreeBSD_version < 500104
error = cdevsw_remove(&rtc_cdevsw);
#endif
Which seems to work find for me in all cases. I made a mental note to
submit a PR once I've tested out the fix, and then of course, I forgot
all about it... :)
$.02,
/Mikko
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200310021550.h92FoJNF016776>