Date: Sun, 20 Jun 2010 20:44:03 +0100 From: Rui Paulo <rpaulo@lavabit.com> To: Fabian Keil <freebsd-listen@fabiankeil.de> Cc: Lawrence Stewart <lstewart@freebsd.org>, freebsd-current@freebsd.org Subject: Re: [CFT] SIFTR - Statistical Information For TCP Research: Uncle Lawrence needs YOU! Message-ID: <6CE5B32B-2C82-436D-82E3-489D2D22C7EA@lavabit.com> In-Reply-To: <20100620213601.050fcf3e@r500.local> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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=262144 > options KTR_COMPILE=(KTR_SCHED) > options KTR_MASK=(KTR_SCHED) > options KTR_CPUMASK=0x3 > options ALQ > options KTR_ALQ > > enabling siftr panics the system, too. That's probably because your module was built with different compile time options than the ones used in the kernel. These options may change structure sizes, function parameters, etc. and that easily causes panics. Regards, -- Rui Paulo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6CE5B32B-2C82-436D-82E3-489D2D22C7EA>