Date: Tue, 21 May 1996 18:44:10 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: sysseh@devetir.qld.gov.au (Stephen Hocking) Cc: toor@dyson.iquest.net, current@freebsd.org Subject: Re: Possible problem with new VM code? Message-ID: <199605220144.SAA02815@phaeton.artisoft.com> In-Reply-To: <199605220045.AAA01916@netfl15a.devetir.qld.gov.au> from "Stephen Hocking" at May 22, 96 10:45:35 am
next in thread | previous in thread | raw e-mail | index | archive | help
> After installing the latest patches to vm_object.c (ctm src-cur 1809) I am now > getting a new sort of panic! > > panic: cleaned vnode isn't > > _getnewvnode(1,f0932600,f0909800,efbffdac,efbffe08) at _getnewvnode+0x10d > _ffs_vget(f0932600,2,efbffdc8,f01bb980,0) at _ffs_vget+0xa3 > _ufs_root(f0932600,efbffe08,f091aa80,efbfff94,efbffea0) at _ufs_root+0x1c > _lookup(,efbfff94,f0a60000,efbfff94,100) at _lookup+0x463 > _namei(efbffea0,efbfff94,f0a60000,0,10540) at _namei+0x183 > _stat(f0a60000,efbfff94,efbfff84,807d060,efbfdb78) at _stat+0x44 > _syscall(10027,efbf0027,10540,efbfdb78,efbfdbd8) at _syscall+0x19c > _Xsyscall() at _Xsyscall+0x35 > > --- syscall 188, eip = 0x806b7f1, ebp = 0xefbfdbd8 Look at my original vget/vclean patch for this and see if it helps; I was pretty sure that the fix the went in for this avoided the problem instead of fixing it. My patch was a kludge, but it addressed the actual problem location. It should be in the -current list archives (look for "free vnode isn't"). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605220144.SAA02815>