Re: Two issues during upgrade from 6.99.23 to 6.99.24

[Nick Hudson <nick.hudson%gmx.co.uk@localhost>]

On 21/10/2013 21:10, Paul Goyette wrote:
> I upgraded my last machine this morning, from 6.99.23 (July 
> time-frame) to 6.99.24 (October).  I've encountered two separate 
> issues on this machine, which did not occur on my other systems.
[snip]

> 2. I'm still experiencing the nfsserver problem that I reported a 
> couple of months ago, although the symptoms have changed somewhat.  
> This time around, I got a crash at the point where nfsserver module 
> would have been loaded.  The console output referenced "syscall #246" 
> (which is, I think, modctl()), but I was unable to copy down 
> everything else before it filled the screen with the crash-dump 
> count-down.
>
> It _did_ leave a core-dump file, but the back-trace doesn't seem to be 
> complete.  It just has the panic stuff...
>
>     (gdb) bt
>     #0  0xffffffff8021e8a3 in cpu_reboot (howto=260, 
> bootstr=<optimized out>)
>         at /build/netbsd-local/src/sys/arch/amd64/amd64/machdep.c:701
>     #1  0xffffffff802d1226 in vpanic (fmt=0xffffffff8040e1bc "trap",
>         ap=0xfffffe813c6a35b0) at 
> /build/netbsd-local/src/sys/kern/subr_prf.c:284
>     #2  0xffffffff802d12da in panic (fmt=<unavailable>)
>         at /build/netbsd-local/src/sys/kern/subr_prf.c:200
>     #3  0xffffffff80302ebd in trap (frame=0xfffffe813c6a36f0)
>         at /build/netbsd-local/src/sys/arch/amd64/amd64/trap.c:294
>     #4  0xffffffff80100f66 in alltraps ()
>     #5  0xffffffff805a2b00 in ?? ()
>     #6  0x0000000000000000 in ?? ()

crash(8) will probably do a better job of getting a full backtrace.

Nick