Date: Wed, 20 Nov 2002 14:57:37 -0500 (EST) From: Robert Watson <rwatson@FreeBSD.ORG> To: Petri Helenius <pete@he.iki.fi> Cc: David Schultz <dschultz@uclink.Berkeley.EDU>, freebsd-questions@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: panic: kmem_map too small Message-ID: <Pine.NEB.3.96L.1021120145647.44513P-100000@fledge.watson.org> In-Reply-To: <3DDBDE2B.6050407@he.iki.fi>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 20 Nov 2002, Petri Helenius wrote: > David Schultz wrote: > > >Thus spake Petri Helenius <pete@he.iki.fi>: > > > > > >>I seem to get kmem_map too small panics when using large buffers with > >>bpf. Is there a tunable I should be increasing? > >> > >> > > > >Yes, increase KVA_PAGES in your kernel config. > > > > > I put in KVA_PAGES=1024 > with following results on next boot: > > Fatal trap 12: page fault while in kernel mode > cpuid = 1; lapic.id = 06000000 > fault virtual address = 0x1 > fault code = supervisor write, page not present > instruction pointer = 0x8:0xc01efc88 > stack pointer = 0x10:0xdf0ccbcc > frame pointer = 0x10:0xdf0ccbf0 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 15 (swi1: net) > trap number lastlog: Permission denied > > Removing the option and recompiling kernel from the same sources makes > it work fine. Looks like some network stack code is responding poorly to malloc() failing (which it can). Any chance you can generate a stack trace for this by compiling DDB into your kernel, then using the trace command to generate the trace? Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1021120145647.44513P-100000>