Opened 3 days ago

Closed 3 days ago

Last modified 3 days ago

#19207 closed bug (duplicate)

[Kernel] PANIC: lock is in use and the caller doesn't call the write lock

Reported by: diver Owned by: nobody
Priority: normal Milestone: Unscheduled
Component: System/Kernel Version: R1/Development
Keywords: Cc:
Blocked By: #19122 Blocking:
Platform: All

Description

This is hrev58272 in VMware Fusion.

Running Firefox Nightly with 1 GB of RAM triggers the following KDL:

KERN: PANIC: rw_lock_destroy(): lock is in use and the caller doesn't hold the write lock (0xffffffff8802fc98)
KERN: Welcome to Kernel Debugging Land...
KERN: Thread 12 "low resource manager" running on CPU 0
KERN: stack trace for thread 12 "low resource manager"
KERN:     kernel stack: 0xffffffff8214f000 to 0xffffffff82154000
KERN: frame                       caller             <image>:function + offset
KERN:  0 ffffffff82153b90 (+  32) ffffffff801508d0   <kernel_x86_64> arch_debug_call_with_fault_handler + 0x1a
KERN:  1 ffffffff82153be0 (+  80) ffffffff800b7618   <kernel_x86_64> debug_call_with_fault_handler + 0x78
KERN:  2 ffffffff82153c40 (+  96) ffffffff800b8d04   <kernel_x86_64> kernel_debugger_loop(char const*, char const*, __va_list_tag*, int) + 0xf4
KERN:  3 ffffffff82153c90 (+  80) ffffffff800b909e   <kernel_x86_64> kernel_debugger_internal(char const*, char const*, __va_list_tag*, int) + 0x6e
KERN:  4 ffffffff82153d80 (+ 240) ffffffff800b9437   <kernel_x86_64> panic + 0xb7
KERN:  5 ffffffff82153dc0 (+  64) ffffffff8009d31b   <kernel_x86_64> rw_lock_destroy + 0x7b
KERN:  6 ffffffff82153de0 (+  32) ffffffff81a231c4   <bfs> Inode::~Inode[clone .localalias] () + 0x44
KERN:  7 ffffffff82153e00 (+  32) ffffffff81a231f1   <bfs> Inode::~Inode[clone .localalias] () + 0x11
KERN:  8 ffffffff82153e50 (+  80) ffffffff81a353ad   <bfs> bfs_put_vnode(fs_volume*, fs_vnode*, bool) + 0x2d
KERN:  9 ffffffff82153e90 (+  64) ffffffff80100e24   <kernel_x86_64> free_vnode(vnode*, bool) + 0xb4
KERN: 10 ffffffff82153ee0 (+  80) ffffffff801025db   <kernel_x86_64> dec_vnode_ref_count[clone .isra.0] (vnode*, bool, bool) + 0x33b
KERN: 11 ffffffff82153f30 (+  80) ffffffff80101fef   <kernel_x86_64> free_unused_vnodes[clone .part.0] (int) + 0x10f
KERN: 12 ffffffff82153fb0 (+ 128) ffffffff800683d5   <kernel_x86_64> low_resource_manager(void*) + 0x2a5
KERN: 13 ffffffff82153fd0 (+  32) ffffffff8008f637   <kernel_x86_64> common_thread_entry(void*) + 0x37
KERN: 14 0000000000000000 (+   0) ffffffff82153fe0   157:low resource manager_12_kstack@0xffffffff8214f000 + 0x4fe0

It is continuable, however, even after closing Firefox and having lots of free RAM, system continues to work really sluggish.

Attachments (1)

syslog (324.4 KB ) - added by diver 3 days ago.

Download all attachments as: .zip

Change History (3)

by diver, 3 days ago

Attachment: syslog added

comment:1 by waddlesplash, 3 days ago

Blocked By: 19122 added
Resolution: duplicate
Status: newclosed

Duplicate of #19122.

I guess hrev58258 didn't fix this after all.

comment:2 by diver, 3 days ago

Version: R1/beta5R1/Development
Note: See TracTickets for help on using tickets.