Subject: Re: smbfs panic
To: Patrick Welche <>
From: Antti Kantee <>
List: current-users
Date: 11/30/2007 13:25:35
On Fri Nov 30 2007 at 08:28:28 +0000, Patrick Welche wrote:
> I can't keep up with all the commits :-) but just in case, I got the following
> with Monday's source (Nov 26 11:04 GMT):
> breakpoint(c052eefa,cd41c668,0,0,cd41c668) at netbsd:breakpoint+0x1
> panic(c052e128,c0359f64,c052e6d6,c052dfe0,d1de9c80) at netbsd:panic+0xd1
> lockdebug_abort1(d1de9c80,c062ec00,c052e6d6,c052dfe0,1) at netbsd:lockdebug_abort1+0x6e
> lockdebug_mem_check(c052e6d6,d484fd80,6c,0,40500) at netbsd:lockdebug_mem_check+0xe1
> pool_do_put(c061d9c0,d484fd80,cd41c708,c39837c0,f) at netbsd:pool_do_put+0x7f
> pool_put(c061d9c0,d484fd80,0,c0324676,c0621afc) at netbsd:pool_put+0x34
> smbfs_reclaim(cd41c778,cdbdfe00,0,cdbdfe00,201b) at netbsd:smbfs_reclaim+0x18f
> VOP_RECLAIM(d268fa5c,cdbdfe00,ffffffff,cdbdfe00,0) at netbsd:VOP_RECLAIM+0x64
> vclean(d268fa5c,8,cdbdfe00,c039a2fd,d268fa5c) at netbsd:vclean+0x408
> vgonel(d268fa5c,cdbdfe00,c02ab50e,c0328bae,1000000) at netbsd:vgonel+0xad
> getcleanvnode(cdbdfe00,200000,0,0,c02ab50e) at netbsd:getcleanvnode+0x15e
> getnewvnode(1,c2b28000,c2c49c00,cd41c8d0,800) at netbsd:getnewvnode+0x176
> ffs_vget(c2b28000,20c59,0,cd41c96c,cd41c970) at netbsd:ffs_vget+0x8b
> ufs_lookup(cd41ca24,cdbdfe00,0,0,cd41ca58) at netbsd:ufs_lookup+0xf15
> VOP_LOOKUP(cd57d3f8,cd41cb40,cd41cb54,cdbdfe00,100d680) at netbsd:VOP_LOOKUP+0x6a
> lookup(cd41cb2c,20002,400,cd41cb48,1) at netbsd:lookup+0x4d6
> namei(cd41cb2c,1,cd41cb3c,c0352683,c062ec40) at netbsd:namei+0x383
> do_sys_stat(cdbdfe00,bb92218c,0,cd41cba0,c062ec40) at netbsd:do_sys_stat+0x40
> sys___lstat30(cdbdfe00,cd41cc34,cd41cc2c,1,c03e0190) at netbsd:sys___lstat30+0x32
> syscall(cd41cc78,b3,bb9100ab,bb91001f,bfbf001f) at netbsd:syscall+0x1d6
> (I did have a win2003 share mounted)

The actual panic message is also generally helpful, it's not printed
just to make your screen look cool ;)

But luckily it's easy guessing where the thing is going wrong.
Try smbfs_node.c rev 1.34.  You should be able to trigger the condition
very quickly by setting kern.maxvnodes low and doing e.g. ls -lR in
your smbfs.  If this patch doesn't help, let's start investigations with
the panic message.

Antti Kantee <>                     Of course he runs NetBSD                
    "la qualité la plus indispensable du cuisinier est l'exactitude"