Return to BSD News archive
Xref: sserve comp.bugs.4bsd:1940 comp.os.386bsd.bugs:545 Newsgroups: comp.bugs.4bsd,comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!munnari.oz.au!hp9000.csc.cuhk.hk!saimiri.primate.wisc.edu!caen!uwm.edu!cs.utexas.edu!wotan.compaq.com!hackney From: hackney@wotan.compaq.com (Greg Hackney) Subject: Re: flock broken - I could use some help Message-ID: <1993Apr23.180213.25332@wotan.compaq.com> Organization: Compaq Computer Corporation References: <1993Apr21.184636.1121@cs.few.eur.nl> <1993Apr22.183734.4448@wotan.compaq.com> <1993Apr23.071135.28560@cs.few.eur.nl> Date: Fri, 23 Apr 1993 18:02:13 GMT Lines: 21 In article <1993Apr23.071135.28560@cs.few.eur.nl> pk@cs.few.eur.nl writes: > I'm pretty sure the problem is in that area though. Now, my proposed patch > may be faulty and cause panics of its own. I suggest you have a look at > a kernel stack trace (option DDB) at the time of the panic. Here's the output: # vm_fault(fe109000, fe1c8000, 1, 0) -> 1 type c, code 0 kernel: type 12 trap, code=0 Stopped at _lf_wakelock+0x17: movl 0x18(%ebx),%ebx db> trace _lf_wakelock(fe2701a0) at _lf_wakelock+0x17 _lf_clearlock(fe270180,fe368000,fdbfffa4,14,fe368044) at _lf_clearlock+0x2c _ufs_advlock(fe368000,fe2701c0,2,fdbfff4c,20) at _ufs_advlock+0xe8 _flock(fe37d600,fdbfffa4,fdbfff9c,fbbeeffc,0) at _flock+0xc0 _syscall(11370,0,fbbeefe0,fdbfffec,fbbeeffc) at _syscall+0xed Bad frame pointer: 0xfbbeefe0