Two issues during upgrade from 6.99.23 to 6.99.24

[Paul Goyette <paul%whooppee.com@localhost>]

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.

1. In-treee Xorg won't start.  The /var/log/Xorg.0.log looks like it 
starts quite normal, but as soon as it starts to attach the video 
driver, it just stops.  Here is the end of the log file:

        [   258.999] (II) XINPUT: Adding extended input device "Keyboard1" 
(type: KEYBOARD)
        [   259.116] (II) UnloadModule: "mouse"
        [   259.116] (II) Unloading mouse
        [   259.116] (II) UnloadModule: "kbd"
        [   259.116] (II) Unloading kbd
        [   259.142] (II) RADEON(0): RADEONRestoreMemMapRegisters() :
        [   259.142] (II) RADEON(0):   MC_FB_LOCATION   : 0x00df00d0 0x00df00d0
        [   259.142] (II) RADEON(0):   MC_AGP_LOCATION  : 0x00000000
        [   259.145] (II) RADEON(0): avivo_restore !
        [   259.165] (WW) RADEON(0): remove MTRR a0000 - b0000
        [   259.179] (II) RADEON(0): [drm] removed 1 reserved context for kernel
        [   259.179] (II) RADEON(0): [drm] unmapping 8192 bytes of SAREA 
0xffff80004187a000 at 0x7f7ff7fc7000
        [   259.179] (II) RADEON(0): [drm] Closed DRM master.

(Similar results occur if I replace the radeon driver with vesa.)

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 ?? ()

I was able to get the hfs-server running - by manually loading nfs 
module at boot time.  I still got an error message "NFS syscalls not 
available" (or similar), but manually running /etc/rc.d/nfsd got thing 
running.




-------------------------------------------------------------------------
| Paul Goyette     | PGP Key fingerprint:     | E-mail addresses:       |
| Customer Service | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com    |
| Network Engineer | 0786 F758 55DE 53BA 7731 | pgoyette at juniper.net |
| Kernel Developer |                          | pgoyette at netbsd.org  |
-------------------------------------------------------------------------