Date: Thu, 23 Nov 2006 17:26:35 -0500 From: Kris Kennaway <kris@obsecurity.org> To: Bakul Shah <bakul@bitblocks.com> Cc: Anders Troback <freebsd@troback.com>, FreeBSD Ports <freebsd-ports@freebsd.org>, Kris Kennaway <kris@obsecurity.org> Subject: Re: Qemu crash... Message-ID: <20061123222635.GA85752@xor.obsecurity.org> In-Reply-To: <20061123221951.484A85B3E@mail.bitblocks.com> References: <20061123214220.GA84447@xor.obsecurity.org> <20061123221951.484A85B3E@mail.bitblocks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--VbJkn9YxBvnuCH5J Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 23, 2006 at 02:19:51PM -0800, Bakul Shah wrote: > > It "should" work, but people sometimes report that it doesn't > > (i.e. when they get the resulting panic). It at least needs to be > > investigated. >=20 > What I suggested works for qemu since kldstat -m works for > aio and kqemu. May be people tried kldload without checking > if the module existed? kldload should do the equiv. of > kldstat -m. The conditions of the panic are that a user has a module already compiled in statically to their kernel, and mistakenly tries to kldload a second copy of it. Beyond this I do not remember details other than that it is still being reported from time to time. >=20 > > There's still the "stale module" problem. >=20 > You mean an old module that you want to replace? No, a module compiled for a different kernel version (e.g. the user ran cvsup and rebuilt modules but has not yet built or booted the new kernel). Modules are notoriously fragile things, even in -stable. > > No, it only works for things that are modules: > > > > > grep -i compat /usr/src/sys/i386/conf/XOR > > options COMPAT_43 # Compatible with BSD 4.3 [KEEP= THIS!] > > options COMPAT_FREEBSD4 # Compatible with FreeBSD4 > > options COMPAT_LINUX >=20 > Ah, I see what you mean... The quick way is to default to > options INCLUDE_CONFIG_FILE but the DEFAULTS file has muddied > the situation as its contents are not shown. May be it is > better for config(8) to generate necessary sysctl glue for > options, makeoptions etc. Even better if sysctl kern.config > can used to recreate the config file of a running system.... That's more or less what I was suggesting. There should be a one stop shop for user programs to figure out the full set of running kernel features. Kris --VbJkn9YxBvnuCH5J Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFZiAbWry0BWjoQKURAtnfAJ9g3bcfobEKbsvNk1zmq5U6K5DuBwCfTamT IJOTcqCIOgVpK6FA2m/aSq0= =0Uat -----END PGP SIGNATURE----- --VbJkn9YxBvnuCH5J--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061123222635.GA85752>