Re: kldstat / kernel linker deadlock

2013-01-12 Thread John Baldwin
On Thursday, November 22, 2012 08:26:17 PM Bryan Drewery wrote: > On 8.3-RELEASE I've hit a deadlock with kldstat. > > I can't provide much information as procstat(1) locks up and I have > already rebooted the servers due to it breaking quite a bit in my setup. > > > # kldstat > > Id Refs Address

kldstat / kernel linker deadlock

2012-11-22 Thread Bryan Drewery
On 8.3-RELEASE I've hit a deadlock with kldstat. I can't provide much information as procstat(1) locks up and I have already rebooted the servers due to it breaking quite a bit in my setup. > # kldstat > Id Refs AddressSize Name > load: 0.91 cmd: kldstat 9936 [kernel linker] 51.21r 0.00u

Re: Linker deadlock.

2008-08-03 Thread Pawel Jakub Dawidek
On Sun, Aug 03, 2008 at 02:09:26PM +0300, Kostik Belousov wrote: > Source line backtraces would be nicer, since gcc inliner forces me to make > a guess. It seems that linker_load_module() calls linker_load_file() > that drops and reaquires the linker lock. > > Then, it seems that dropping the modu

Re: Linker deadlock.

2008-08-03 Thread Kostik Belousov
On Sun, Aug 03, 2008 at 09:32:40AM +0200, Pawel Jakub Dawidek wrote: > Hi. > > Linker can easly deadlock when we try to load the same kernel module > from two processes at the same time. This is because we drop kld_sx in > linker_load_file() and reacquire it, which leads to LOR, because we > alrea

Linker deadlock.

2008-08-03 Thread Pawel Jakub Dawidek
Hi. Linker can easly deadlock when we try to load the same kernel module from two processes at the same time. This is because we drop kld_sx in linker_load_file() and reacquire it, which leads to LOR, because we already held vnode lock at this point. Interesing backtraces below. First process: d