Subject: Re: 1.6 vm_fault on ie packet rx
To: Chuck Silvers <chuq@chuq.com>
From: Adam Kropelin <akropel1@rochester.rr.com>
List: port-sun3
Date: 11/23/2002 17:55:20
----- Original Message -----
From: "Chuck Silvers" <chuq@chuq.com>
To: "Adam Kropelin" <akropel1@rochester.rr.com>
Cc: <port-sun3@netbsd.org>
Sent: Saturday, November 23, 2002 1:34 PM
Subject: Re: 1.6 vm_fault on ie packet rx


> On Fri, Nov 22, 2002 at 09:04:43PM -0500, Adam Kropelin wrote:
> > > it would be easier to just use an NFS root rather than mess with a
ramdisk,
> > > if you can do that...
> >
> > ...except it's the ethernet driver that's panicing the system to begin
with.
>
> well, that means that you can get information about the problem, right?

You're right, of course. I was focused on reproducing the exact environment
in which I had the problem, but NFS root should do it, too.

> > Building the ramdisk pieces in distrib/ seems strightforward except the
> > Makefiles all seem to need dozens of env vars that only get set if you
build
> > release from the top of the tree. For now I'll see if I can reproduce on
> > GENERIC (James Wiley says the problem doesn't exist on GENERIC) and if
not I
> > guess I'll try building release. Any suggestions on getting the ramdisk
> > image built without having to build the rest of the world?
> >
> > --Adam
>
> the distrib tree probably depends on various libraries and such from
> the earlier parts of the build.  it's easiest just to cross-build
> the release from a fast pc.

Ok, thanks...

--Adam