Date: Thu, 18 May 2006 14:02:48 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Kris Kennaway <kris@obsecurity.org>, FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: kernel panic on kldload in 6.1 Message-ID: <20060518180248.GA59768@xor.obsecurity.org> In-Reply-To: <20060518085751.87254B845@shodan.nognu.de> References: <BC02D4C2-2968-462C-AFE1-58B4C5A1E1C3@netmusician.org> <20060518043629.GA29966@xor.obsecurity.org> <20060518085751.87254B845@shodan.nognu.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--sm4nu43k4a2Rpi4c Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 18, 2006 at 10:57:51AM +0200, Frank Steinborn wrote: > Kris Kennaway wrote: > > It sounds like you have an old (6.0) module you're still trying to > > load. Things like the nvidia driver and other ports are prime > > candidates. > >=20 > > Kris >=20 > Does that mean that all the panic-issues with kld(un)load are fixed in > 6.1? I crashed an important 6.0-STABLE box several times by trying to > unload procfs for example and I don't want to run in such nightmares > again by fiddling with klds unless I'm sure it's safe now. No, it means that modules are not cross-compatible between releases. Please retest your problem with 6.1 and file a PR if you encounter it again; it's the only way it will get fixed. Kris --sm4nu43k4a2Rpi4c Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEbLbIWry0BWjoQKURArsBAKC24RU3FZ1ckwDTUncCW4p0vur/UACfainn qxGYgKH1M3pk11xoS54yE7U= =pC0w -----END PGP SIGNATURE----- --sm4nu43k4a2Rpi4c--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060518180248.GA59768>