Re: kern/46377 (Use of Coda file system triggers an immediate kernel panic)

[christos%zoulas.com@localhost (Christos Zoulas)]

On May 2,  2:23pm, u-bsdmwle%aetey.se@localhost (u-bsdmwle%aetey.se@localhost) 
wrote:
-- Subject: Re: kern/46377 (Use of Coda file system triggers an immediate ker

| On Sat, Apr 28, 2012 at 08:35:03PM +0000, rmind%NetBSD.org@localhost wrote:
| > Synopsis: Use of Coda file system triggers an immediate kernel panic
| > 
| > State-Changed-From-To: open->feedback
| > State-Changed-By: rmind%NetBSD.org@localhost
| > State-Changed-When: Sat, 28 Apr 2012 20:35:03 +0000
| > State-Changed-Why:
| > Should be fixed.  Can you try latest -current?
| 
| Testing with
| "NetBSD xxx 6.99.6 NetBSD 6.99.6 (GENERIC) #0: Tue May  1 16:11:22 UTC 2012  
builds%b6.netbsd.org@localhost:/home/builds/ab/HEAD/i386/201205010910Z-obj/home/builds/ab/HEAD/src/sys/arch/i386/compile/GENERIC
 i386"
| 
| $ cp /coda/coda.cs.cmu.edu/WELCOME /tmp/xxx
| 
| seems now working, but copying another (and bigger, 640160 bytes) file leads
| to a different system crash, several seconds after the copy operation finishes
| (apparently at sync?) :

You should be able to cause it sooner, by calling sync manually. I found
that it sometimes helps with getting more reliable debugging sessions to
offline all but one cpu's before crashing it.

christos