On Wednesday 04 February 2009 11:05:02 am Nikola Knežević wrote:
> On 2 Feb 2009, at 19:09 , Julian Elischer wrote:
>
> >>> It says "non-sleepable locks", yet it classifies click_instance
> >>> as sleep mutex. I think witness code should emit messages which
> >>> are more clear.
> >> It is c
On 2 Feb 2009, at 19:09 , Julian Elischer wrote:
It says "non-sleepable locks", yet it classifies click_instance
as sleep mutex. I think witness code should emit messages which
are more clear.
It is confusing, but you can't do an M_WAITOK malloc while holding
a mutex. Basically, sleeping
John Baldwin wrote:
On Monday 02 February 2009 7:33:08 am Nikola Knežević wrote:
On 30 Jan 2009, at 18:11 , Nikola Knežević wrote:
This is the message buffer:
Unread portion of the kernel message buffer:
panic: blockable sleep lock (sleep mutex) 16 @ /usr/src/sys/vm/
uma_core.c:1834
Any
On Monday 02 February 2009 7:33:08 am Nikola Knežević wrote:
> On 30 Jan 2009, at 18:11 , Nikola Knežević wrote:
>
> > This is the message buffer:
> > Unread portion of the kernel message buffer:
> > panic: blockable sleep lock (sleep mutex) 16 @ /usr/src/sys/vm/
> &
On 30 Jan 2009, at 18:11 , Nikola Knežević wrote:
This is the message buffer:
Unread portion of the kernel message buffer:
panic: blockable sleep lock (sleep mutex) 16 @ /usr/src/sys/vm/
uma_core.c:1834
Any hints where I should search for the cause?
Ok, I solved this problem. I had a
is the message buffer:
Unread portion of the kernel message buffer:
panic: blockable sleep lock (sleep mutex) 16 @ /usr/src/sys/vm/
uma_core.c:1834
cpuid = 0
Uptime: 24m35s
Physical memory: 114 MB
Dumping 42 MB: 27 11
Any hints where I should search for the cause?
I'm using MTX_DEF mutexes to
6 matches
Mail list logo