Date: Sat, 4 Jan 2003 21:21:40 +0100 From: "Willem Jan Withagen" <wjw@withagen.nl> To: <phk@FreeBSD.ORG> Cc: <current@FreeBSD.ORG> Subject: VM page queue mutex not locked panic (WAS:Re: panic with panic: kmem_malloc(4096): kmem_map too small... ) Message-ID: <051f01c2b42e$e4651400$471b3dd4@dual> References: <7651.1041670679@critter.freebsd.dk>
index | next in thread | previous in thread | raw e-mail
> In message <03a701c2b38c$8e3ad990$471b3dd4@dual>, "Willem Jan Withagen" writes:
> >Which seems a problem sticking up it's head once so often.
> >I had it happen to me now 3 times over the last day. It just drops into the debugger.
> >And I've foun little extra info in the archive.
> >
> >What dows this actually mean? Is something leaking in the kernel.
> >IF so how do I help it go away.
> >
> >I'm copy 100G from a W2K system to my vinum file server with a 170G raid5.
> >Current is as of 28 dec...
>
> Please try to move up to current as of today. On Dec 29th I commited
> code to make the desiredvnodes a limit rather than a vague suggestion
> and that should solve your problem I hope.
It seams easy to repeat, AND I haven't copied the whole disk yet.
So there plenty test material. I'll keep you posted.
Today means European saturday during the day? (I'm auto-build everything, cvsup-ing at 6:00)
But the following question is alrady there.
When I woke up this morning I found my box with a double panic:
lock (sleep mutex) VM page queue mutex not locked @
/usr/src/sys/kern/vf
[the remainder was not on the screen]
Is this related, our should this start a new thread?
--WjW
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?051f01c2b42e$e4651400$471b3dd4>