Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 6 Sep 2008 18:29:30 +0300
From:      Kostik Belousov <kostikbel@gmail.com>
To:        "Sean C. Farley" <scf@freebsd.org>, freebsd-emulation@freebsd.org
Subject:   Re: Linux applications core if running (k)qemu
Message-ID:  <20080906152929.GB2038@deviant.kiev.zoral.com.ua>
In-Reply-To: <20080906104659.GA2113@dchagin.dialup.corbina.ru>
References:  <alpine.BSF.1.10.0808291711580.5866@thor.farley.org> <20080830113448.GA2152@dchagin.dialup.corbina.ru> <alpine.BSF.2.00.0809021552040.7934@thor.farley.org> <20080906104659.GA2113@dchagin.dialup.corbina.ru>

next in thread | previous in thread | raw e-mail | index | archive | help

--FG2vzoPGYsbT0vfz
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Sep 06, 2008 at 02:46:59PM +0400, Chagin Dmitry wrote:
> On Tue, Sep 02, 2008 at 03:56:33PM -0500, Sean C. Farley wrote:
> > On Sat, 30 Aug 2008, Chagin Dmitry wrote:
> >=20
> > >On Fri, Aug 29, 2008 at 05:29:09PM -0500, Sean C. Farley wrote:
> > >>I am having trouble with kqemu.ko and linux.ko.  If I run qemu with
> > >>the following command, Linux applications (chroot, acroread, ls) will
> > >>start core dumping:
> > >>    qemu-system-x86_64 -m 512 \
> > >>    -drive file=3D/usr/QEMU/WinXP/c.img,if=3Dide,media=3Ddisk -boot c=
 \
> > >>    -std-vga -parallel none -serial none -monitor stdio \
> > >>    -net nic,model=3De1000 -net tap,ifname=3Dtap0,script=3Dno -localt=
ime
> > >>
> > >>Loading kqemu.ko does not cause the problem, but the cores start a
> > >>little after WinXP starts running.  Unloading kqemu.ko does not help;
> > >>the cores still happen but more randomly.  I even tried unloading all
> > >>linux modules and reloading them without luck.  It takes a reboot.
> > >>
> > >>Packages:
> > >>qemu-devel-0.9.1s.20080620_1
> > >>kqemu-kmod-devel-1.4.0.p1
> > >>linux_base-f8-8_4
> > >>
> > >>sysctl:
> > >>compat.linux.osrelease: 2.6.16
> > >>
> > >>dmesg:
> > >>kqemu version 0x00010400
> > >>kqemu: KQEMU installed, max_locked_mem=3D1792492kB.
> > >>
> > >>System is 7-STABLE as of r181963 with or without the patch to fix RT
> > >>signals from Chagin.
> > >
> > >Interestingly... Sean, can you provide ktrace/kdump log of coring
> > >apps?  thnx!
> >=20
> > Here they are (good and bad):
> > http://www.farley.org/freebsd/tmp/linuxulator_vs_kqemu/
> >=20
> > The good trace is after the bad trace.  I just kept running ktrace
> > /compat/linux/bin/date over and over until I got a good trace.  Before
> > loading kqemu and running qemu, there were no core dumps.  Also, I
> > compared two bad traces and they were basically the same except for PID
> > and a couple of addresses (still very close in value).
> >=20
>=20
> Most likely it is a tls problem again, some days ago kib@ has made MFC
> r182684, probably it will help..

I doubt it. This seems to be an ingenious kqemu bug. As far as I remember,
it tries to use GDT/LDT. This probably has unwanted interaction with
PCB_GS32BIT.

--FG2vzoPGYsbT0vfz
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (FreeBSD)

iEYEARECAAYFAkjCodkACgkQC3+MBN1Mb4iYxACg0d0rGWlatJiR9+2E1ztZhq61
nsoAn2J3SrQL1vvW+9ChYKoaFTheHtfA
=mfmx
-----END PGP SIGNATURE-----

--FG2vzoPGYsbT0vfz--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080906152929.GB2038>