Re: Acquiring lockmgr lock "ufs" with non-sleepable locks

Suleiman Souhlal wrote:

> This was introduced by my commit to take out the various kqueue  
> operations outside of ufs. It is because we are trying to lock the  
> vnode while holding the knlist mutex. I'll work on a fix on  wednesday, 
> as I'll unfortunately be a bit busy until then. I hope  this won't cause 
> you any inconvenience.

Is the below the same ?
I simply ask because I see this on ppc.
Doing a tail -f /var/log/messages produces a continues kdb message flow:

Jun 28 23:14:51 albook kernel: Acquiring lockmgr lock "ufs" with the 
following non-sleepable locks held:
Jun 28 23:14:52 albook kernel: exclusive sleep mutex vnode pollinfo r = 
0 (0x34be1000) locked _at_ /home/andreast/devel/src/sys/kern/kern_event.c:881
Jun 28 23:14:53 albook kernel: KDB: stack backtrace:
Jun 28 23:14:53 albook kernel: 0xe117b910: at witness_warn+0x274
Jun 28 23:14:53 albook kernel: 0xe117b9c0: at lockmgr+0xf8
Jun 28 23:14:53 albook kernel: 0xe117ba00: at vop_stdlock+0x2c
Jun 28 23:14:53 albook kernel: 0xe117ba10: at VOP_LOCK_APV+0xe8
Jun 28 23:14:53 albook kernel: 0xe117ba30: at ffs_lock+0x20
Jun 28 23:14:53 albook kernel: 0xe117ba40: at VOP_LOCK_APV+0xe8
Jun 28 23:14:53 albook kernel: 0xe117ba60: at vn_lock+0xd4
Jun 28 23:14:53 albook kernel: 0xe117bab0: at filt_vfsread+0x58
Jun 28 23:14:53 albook kernel: 0xe117bb60: at kqueue_register+0x6f8
Jun 28 23:14:53 albook kernel: 0xe117bba0: at kern_kevent+0x100
Jun 28 23:14:53 albook kernel: 0xe117bca0: at kevent+0x7c
Jun 28 23:14:53 albook kernel: 0xe117bce0: at syscall+0x29c
Jun 28 23:14:53 albook kernel: 0xe117bd60: at trap+0x168
Jun 28 23:14:53 albook kernel: 0xe117bda0: at powerpc_interrupt+0xc0
Jun 28 23:14:53 albook kernel: 0xe117bdd0: user SC trap by 0x2189aed8: 
srr1=0xd032
Jun 28 23:14:53 albook kernel: r1=0x7fffdb50 cr=0x24000022 xer=0 
ctr=0x2189aed0
Jun 28 23:14:53 albook kernel: Acquiring lockmgr lock "ufs" with the 
following non-sleepable locks held:
Jun 28 23:14:53 albook kernel: exclusive sleep mutex kqueue r = 0 
(0x2cbcfb00) locked _at_ /home/andreast/devel/src/sys/kern/kern_event.c:1524
Jun 28 23:14:53 albook kernel: exclusive sleep mutex vnode pollinfo r = 
0 (0x34be1000) locked _at_ /home/andreast/devel/src/sys/kern/kern_event.c:1512
Jun 28 23:14:53 albook kernel: KDB: stack backtrace:
Jun 28 23:14:53 albook kernel: 0xdede58a0: at witness_warn+0x274
Jun 28 23:14:53 albook kernel: 0xdede5950: at lockmgr+0xf8
Jun 28 23:14:53 albook kernel: 0xdede5990: at vop_stdlock+0x2c
Jun 28 23:14:53 albook kernel: 0xdede59a0: at VOP_LOCK_APV+0xe8
Jun 28 23:14:53 albook kernel: 0xdede59c0: at ffs_lock+0x20
Jun 28 23:14:53 albook kernel: 0xdede59d0: at VOP_LOCK_APV+0xe8
Jun 28 23:14:53 albook kernel: 0xdede59f0: at vn_lock+0xd4
Jun 28 23:14:53 albook kernel: 0xdede5a40: at filt_vfsread+0x58
Jun 28 23:14:53 albook kernel: 0xdede5af0: at knote+0xd4
Jun 28 23:14:53 albook kernel: 0xdede5b20: at VOP_WRITE_APV+0x20c
Jun 28 23:14:53 albook kernel: 0xdede5bf0: at vn_write+0x280
Jun 28 23:14:53 albook kernel: 0xdede5c90: at kern_writev+0xc0
Jun 28 23:14:53 albook kernel: 0xdede5cc0: at writev+0x54
Jun 28 23:14:53 albook kernel: 0xdede5ce0: at syscall+0x29c
Jun 28 23:14:53 albook kernel: 0xdede5d60: at trap+0x168
Jun 28 23:14:53 albook kernel: 0xdede5da0: at powerpc_interrupt+0xc0
Jun 28 23:14:53 albook kernel: 0xdede5dd0: user SC trap by 0x218be914: 
srr1=0xd032
Jun 28 23:14:53 albook kernel: r1=0x7fffba10 cr=0x40022042 
xer=0x20000000 ctr=0x218be90c

etc....

No, I did not try the follow-up patch yet.

Thanks,
Andreas