On Wed, 18 Feb 1998, Dave Huang wrote:
> A kernel built from my normal config crashes with a vm_fault() after
> probing mc0 (MACE internal ethernet). Normally, it'd probe esp0 after
> that... The ddb stack trace says something about config_search() ->
> mapply() -> faultstkadj(), then trap/panic stuff.

Hmmm.... how weird and freaky. My normal kernel config crashes, but if I
just take out "options NETATALK", the kernel works. (And a kernel
without mc0 or netatalk hangs early on; a kernel without mc0 but with
netatalk won't even link). All of this seems too flaky for it to really
be netatalk's fault... any chance the recent pmap changes introduced a
bug? 
-- 
Name: Dave Huang     |   Mammal, mammal / their names are called /
INet: khym@bga.com   |   they raise a paw / the bat, the cat /
FurryMUCK: Dahan     |   dolphin and dog / koala bear and hog -- TMBG
Dahan: Hani G Y+C 22 Y++ L+++ W- C++ T++ A+ E+ S++ V++ F- Q+++ P+ B+ PA+ PL++