From owner-freebsd-ports@FreeBSD.ORG Thu Nov 23 22:26:52 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 481C416A40F for ; Thu, 23 Nov 2006 22:26:52 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id A36BF43D46 for ; Thu, 23 Nov 2006 22:26:14 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id E10591A3C19; Thu, 23 Nov 2006 14:26:51 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id AC30151A00; Thu, 23 Nov 2006 17:26:36 -0500 (EST) Date: Thu, 23 Nov 2006 17:26:35 -0500 From: Kris Kennaway To: Bakul Shah Message-ID: <20061123222635.GA85752@xor.obsecurity.org> References: <20061123214220.GA84447@xor.obsecurity.org> <20061123221951.484A85B3E@mail.bitblocks.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="VbJkn9YxBvnuCH5J" Content-Disposition: inline In-Reply-To: <20061123221951.484A85B3E@mail.bitblocks.com> User-Agent: Mutt/1.4.2.2i Cc: Anders Troback , FreeBSD Ports , Kris Kennaway Subject: Re: Qemu crash... X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Nov 2006 22:26:52 -0000 --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--