On Aug 25, 2011, at 11:18 PM, Darren Reed wrote:
starting postgres panic's my system every time with this panic:
panic: kernel diagnostic assertion uvm_page_locked_p(pg
e ../../../../arch/x86/x86/pmap.c, line 3214
From the pmap.c that was used to compile the kernel is this
extract,
On Fri, Aug 26, 2011 at 08:33:47AM +, YAMAMOTO Takashi wrote:
What happens if vn_lock(vp, LK_EXCLUSIVE|LK_RETRY) is called on a
LK_SHARED locked vnode? I would expect it to sleep until the shared lock
is released.
a recursive locking attempt is an error.
We have no way to upgrade a
Am 24.08.11 00:00, schrieb Mindaugas Rasiukevicius:
Marc Balmer mbal...@netbsd.org wrote:
Here comes the third iteration of the gpio(4) patch. In addition to
whjat I already described, u_int_XXX types have been replaced by
uint_XXX and gpio(4) is made MPSAFE. Comments?
Furthermore I am
On Fri, Aug 26, 2011 at 01:07:43AM +0200, Emmanuel Dreyfus wrote:
[...]
+*/
+ if ((locked = VOP_ISLOCKED(vp)) != LK_EXCLUSIVE)
+ vn_lock(vp, LK_EXCLUSIVE | LK_RETRY);
You can't use VOP_ISLOCKED this way (it's basically there to be
used in KASSERT()): for ufs, this
Am 25.08.11 23:18, schrieb Darren Reed:
starting postgres panic's my system every time with this panic:
panic: kernel diagnostic assertion uvm_page_locked_p(pg
e ../../../../arch/x86/x86/pmap.c, line 3214
From the pmap.c that was used to compile the kernel is this
extract, with
On Fri, Aug 26, 2011 at 08:33:47AM +, YAMAMOTO Takashi wrote:
if we go this route, it's cleaner to use a puffs internal lock
I did it that way, and it seems to work fine.
--
Emmanuel Dreyfus
m...@netbsd.org
? sys/fs/puffs/puffs_vnops.c-debug
? sys/fs/puffs/puffs_vnops.c.ok1
?
J. Hannken-Illjes wrote:
On Aug 25, 2011, at 11:18 PM, Darren Reed wrote:
starting postgres panic's my system every time with this panic:
panic: kernel diagnostic assertion uvm_page_locked_p(pg
e ../../../../arch/x86/x86/pmap.c, line 3214
From the pmap.c that was used to compile the
Am 26.08.11 20:35, schrieb Darren Reed:
J. Hannken-Illjes wrote:
On Aug 25, 2011, at 11:18 PM, Darren Reed wrote:
starting postgres panic's my system every time with this panic:
panic: kernel diagnostic assertion uvm_page_locked_p(pg
e ../../../../arch/x86/x86/pmap.c, line 3214
From
