Re: panic: lock error near wapbl_begin

[Juergen Hannken-Illjes <hannken%eis.cs.tu-bs.de@localhost>]

On Fri, Aug 29, 2008 at 06:41:12PM +0200, Lars Nordlund wrote:
> Hi
> 
> I am running NetBSD 4.99.72 amd64.
> 
> When pummeling on:
> 
> wd0 at atabus6 drive 0: <SAMSUNG HD300LJ>
> wd0: drive supports 16-sector PIO transfers, LBA48 addressing
> wd0: 279 GB, 581418 cyl, 16 head, 63 sec, 512 bytes/sect x 586070255
> sectors wd0: 32-bit data port
> wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 7
> wd0(piixide1:0:0): using PIO mode 4, Ultra-DMA mode 6 (Ultra/133)
> (using DMA)
> 
> mounted as:
> 
> /dev/wd0e on /mnt/kalle type ffs (log, NFS exported, local)
> 
> I see this panic (hand-copied from screen..):
> 
> lock address: 0xffff8000044fda78
> current cpu: 0
> current lwp: 0xffff800046913020
> owner/count: 0xffff800046913020 flags 0x0000000000000004

Locking against self ...

> panic: lock error
> fatal breakpoint in supervisor mode
> trap type 1 code 0 rip ffffffff80501fc5 cs 8 rflags 246 cr2
> ffff8000495e2000 cpl 0 rsp ffff80004ba783a0
> 
> Stopped in pid 1812.1 (gtk-gnutella) at netbsd:breakpoint +0x5: leave
> breakpoint() at netbsd:breakpoint+0x5
> panic() at netbsd:panic+0x260
> lockdebug_abort() at netbsd:lockdebug_abort+0x42
> rw_vector_enter() at netbsd:wapbl_begin+0x76
> ffs_gop_write() at netbsd:ffs_gop_write+0x87
> genfs_do_putpages at netbsd:genfs_do_putpages+0x9bb
> VOP_PUTPAGES() at netbsd:VOP_PUTPAGES+0x71
> ffs_truncate() at netbsd:ffs_truncate+0x3af
> ufs_setattr() at netbsd:ufs_setattr+0x33f
> VOP_SETATTR() at netbsd:VOP_SETATTR+0x63
> sys_truncate at netbsd:sys_truncate+0xf1
> syscall at netbsd:syscall+0x9a
> 
> Too bad I did not use LOCKDEBUG at the time.
> 
> 
> Best regards,
>       Lars Nordlund

Please try Rev. 1.99 of sys/ufs/ffs/ffs_inode.c

-- 
Juergen Hannken-Illjes - hannken%eis.cs.tu-bs.de@localhost - TU Braunschweig 
(Germany)