Subject: Re: Crash dump analysis?
To: Charles M. Hannum <mycroft@NetBSD.ORG>
From: Simon J. Gerraty <sjg@frodo.dn.itg.telecom.com.au>
List: current-users
Date: 02/05/1996 11:18:17
>    It seems to have died somewhere in dead_ something or other,
>    but the message flashed by while I was just walking in.
> 
> dead_badop(), and it's already been fixed.  Update your kernel sources
> (specifically dead_vnops.c).

Thanks Charles, just what I needed.  Since I can't sup reliably, could
I just add a new dead_vnops.c to the Jan 27 tar ball sources?   Or
would the latest tar_files Feb 3/4 be ok?

Strangely, I built and tested the Jan-27 tar ball on hobbit (SS2) before
builing and testing on not (i486 notebook), both worked fine.  I even
tested that ppp from the notebook worked to zen (my gateway machine at
home) and since all looked ok I installed the new binaries and kernel
on zen.

When I re-booted, ppp failed to negotiate config with the ISP, and
shortly after comming up multi-user I got the dead_badop panic.
This happens consistently.

Sadly, the previous (very) reliable kernel was 95.08.18 and won't work
with the new user-land.

Getting rid of the panic's will let me start working on getting ppp
working again.

Anyway, thanks again for saving me a few hours (or worse) looking
through the source.

--sjg