Date: Sun, 05 Jan 2003 03:49:40 +0900 (JST) From: Hiroki Sato <hrs@eos.ocn.ne.jp> To: phk@FreeBSD.ORG Cc: wjw@withagen.nl, current@FreeBSD.ORG Subject: Re: panic with panic: kmem_malloc(4096): kmem_map too small... Message-ID: <20030105.034940.18284223.hrs@eos.ocn.ne.jp> In-Reply-To: <7651.1041670679@critter.freebsd.dk> References: <03a701c2b38c$8e3ad990$471b3dd4@dual> <7651.1041670679@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, phk@FreeBSD.ORG wrote in <7651.1041670679@critter.freebsd.dk>: phk> In message <03a701c2b38c$8e3ad990$471b3dd4@dual>, "Willem Jan Withagen" writes: phk> >Which seems a problem sticking up it's head once so often. phk> >I had it happen to me now 3 times over the last day. It just drops into the debugger. phk> >And I've foun little extra info in the archive. phk> > phk> >What dows this actually mean? Is something leaking in the kernel. phk> >IF so how do I help it go away. phk> > phk> >I'm copy 100G from a W2K system to my vinum file server with a 170G raid5. phk> >Current is as of 28 dec... phk> phk> Please try to move up to current as of today. On Dec 29th I commited phk> code to make the desiredvnodes a limit rather than a vague suggestion phk> and that should solve your problem I hope. I also had "kmem_malloc(4096): kmem_map too small: 275378176 total allocated" several times on -current as of Jan 4th. My -current box has 3GB memory, but when the memory size is explicitly specified as 2GB via MAXMEM option, the panic disappears (but I don't know why...). -- | Hiroki SATO <hrs@eos.ocn.ne.jp> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030105.034940.18284223.hrs>