Date: Sat, 26 Jul 2003 23:02:49 +0200 From: Gary Jennejohn <garyj@jennejohn.org> To: Mark Blackman <mark@exonetric.com> Cc: freebsd-current@freebsd.org Subject: Re: device driver memory leak in 5.1-20030726? Message-ID: <200307262102.h6QL2nPD012268@peedub.jennejohn.org> In-Reply-To: Message from Mark Blackman <mark@exonetric.com> <95013A6C-BFA4-11D7-A23D-00039315D3FE@exonetric.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Mark Blackman writes: > I'm seeing the same 'kmem_malloc(4096): kmem_map too small: XXXXX total > allocated' > messages that a few other have reported. [snip] > From these symptoms, I'm speculating that one or more device drivers > are producing kernel memory leaks and either triggering the > 'kmem_map too small' messages or pushing all of the userland processes > out of the way. Is this a reasonable interpretation? > > Does anyone else see symptoms that might lead to this conclusion? > I'm seeing exactly the same thing when I try to access my Archos Jukebox (a USB 2.0 device). This didn't happen with a kernel made before July 20, although I can't say when exactly the leak (if there is one) was introduced, since I only make a new kernel every few weeks. Eventually usb_allocmem fails and shortly thereafter I get the ``kmem_map too small'' panic. Unfortunately, panicing in ddb results in a hang - no crashdump. --- Gary Jennejohn / garyj[at]jennejohn.org gj[at]freebsd.org gj[at]denx.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200307262102.h6QL2nPD012268>