Date: Mon, 21 Jun 2010 20:52:28 +0200 From: Fabian Keil <freebsd-listen@fabiankeil.de> To: Lawrence Stewart <lstewart@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: [CFT] SIFTR - Statistical Information For TCP Research: Uncle Lawrence needs YOU! Message-ID: <20100621205228.0e5332cc@r500.local> In-Reply-To: <4C1EE644.3070105@freebsd.org> References: <4C1492D0.6020704@freebsd.org> <4C1C3922.2050102@freebsd.org> <20100619195823.53a7baaa@r500.local> <4C1DED16.8020209@freebsd.org> <20100620131544.495ddecd@r500.local> <4C1E019F.6060802@freebsd.org> <20100620142841.4803dac3@r500.local> <4C1E0E14.3090506@freebsd.org> <20100620151554.58e486db@r500.local> <20100620161242.59381341@r500.local> <20100620213601.050fcf3e@r500.local> <6CE5B32B-2C82-436D-82E3-489D2D22C7EA@lavabit.com> <4C1EE644.3070105@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/G66arsCBtb_DrBlKhgyKUd_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Lawrence Stewart <lstewart@freebsd.org> wrote: > On 06/21/10 05:44, Rui Paulo wrote: > > > > On 20 Jun 2010, at 20:36, Fabian Keil wrote: > > > >> Fabian Keil<freebsd-listen@fabiankeil.de> wrote: > >> > >>> Fabian Keil<freebsd-listen@fabiankeil.de> wrote: > >> > >>>> My custom kernel normally doesn't have INVARIANTS and WITNESS > >>>> enabled, so I'll try to enable them next. > >>> > >>> The culprit seem to be non-default KTR settings in the kernel > >>> while loading alq as a module. > >> > >> Actually whether or not alq is loaded as a module doesn't > >> seem to matter, with: > >> > >> options KTR > >> options KTR_ENTRIES=3D262144 > >> options KTR_COMPILE=3D(KTR_SCHED) > >> options KTR_MASK=3D(KTR_SCHED) > >> options KTR_CPUMASK=3D0x3 > >> options ALQ > >> options KTR_ALQ > >> > >> enabling siftr panics the system, too. > > > > That's probably because your module was built with different compile ti= me options than the ones used in the kernel. These options may change struc= ture sizes, function parameters, etc. and that easily causes panics. >=20 > hmm I wonder if my instructions to build SIFTR manually are causing your= =20 > problems. Fabian, is the siftr.ko module you're loading built as part of= =20 > a "make buildkernel", or did you follow my instructions and "cd=20 > </path/to/src>/sys/modules/siftr ; make ; kldload ./siftr.ko"? The latter. > If the latter is true, perhaps try and explicitly build SIFTR as part of= =20 > "make buildkernel" and see if loading the module built that way still=20 > triggers the panic when enabled (the module will be in=20 > /usr/obj/<path/to/src>/sys/<KERNCONF>/modules/<path/to/src>/sys/modules/s= iftr/siftr.ko=20 > or if you "make installkernel" it'll be in /boot/kernel/kernel/siftr.ko). That seems to work. Fabian --Sig_/G66arsCBtb_DrBlKhgyKUd_ Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkwftPEACgkQBYqIVf93VJ1ZjQCghr/4lTHsXky8y4KkctgsjJiy 4AcAniqqNaVSIuEIPKzCnbYuUetrk4TX =nwK5 -----END PGP SIGNATURE----- --Sig_/G66arsCBtb_DrBlKhgyKUd_--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100621205228.0e5332cc>