Subject: Re: uvm_loan() panic (Was: Re: Softdep with ffs, how broken is it?)
To: Andrew Gillham <gillham@vaultron.com>
From: Jaromír <jdolecek@netbsd.org>
List: tech-kern
Date: 07/01/2001 13:38:11
Yah, definitely this is uvm_loan() related, this is not a softdep
related.

Can you please file a pr?
While this is probably not something I'd
be able to fix myself, Chuck Cranor or Chuck Silvers might be able to :)

It would also be nice if you'd be able
to provide -g compiled kernel with appropriate crashdump somewhere, Greg.
I guess the problem is not easily repetable, right?

Jaromir

Andrew Gillham wrote:
> On Sun, Jul 01, 2001 at 01:20:13AM -0400, Greg A. Woods wrote:
> > 
> > Here's a trace of what the last two looked like:
> > 
> > panic: lockmgr: release of unlocked lock!
> > Stopped in pid 4517 (cron) at   cpu_Debugger+0x4:       leave
> > db> trace 
> > cpu_Debugger(d0ba48d8,6,0,d0d5ce04,c019c8ce) at cpu_Debugger+0x4
> > panic(c0384380,8085000,1,3000,d0a12420) at panic+0x8e
> > lockmgr(d0ba48d8,6,0) at lockmgr+0x88e
> > uvm_loan(d0ba48d4,8085000,3000,c0cf7890,2) at uvm_loan+0x243
> > pipe_write(d0ddc734,d0ddc750,d0d5cf04,c08a3f00,1) at pipe_write+0x38a
> > dofilewrite(d0e5e91c,5,d0ddc734,8084000,32fb) at dofilewrite+0x94
> > sys_write(d0e5e91c,d0d5cf80,d0d5cf78) at sys_write+0x63
> > syscall_plain(2b,805002b,bfbf001f,807001f,8084000) at syscall_plain+0x98
> > db> 
> 
> Is this at all related to the new pipes?  e.g. options NEW_PIPE
> 
> -Andrew
> 


-- 
Jaromir Dolecek <jdolecek@NetBSD.org>      http://www.ics.muni.cz/~dolecek/
NetBSD - just plain best OS! -=*=- Got spare MCA cards or docs? Hand me them!