From owner-freebsd-current Wed Jul 15 13:09:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10039 for freebsd-current-outgoing; Wed, 15 Jul 1998 13:09:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.ny.otec.com (bright.ny.otec.com [209.3.16.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA10031 for ; Wed, 15 Jul 1998 13:09:00 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.ny.otec.com (8.8.8/8.8.8) with SMTP id QAA20634; Wed, 15 Jul 1998 16:08:46 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.ny.otec.com: bright owned process doing -bs Date: Wed, 15 Jul 1998 16:08:46 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.ny.otec.com To: Richard Wackerbarth cc: current@FreeBSD.ORG Subject: Re: repeatable crash with softupdates In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hrm however my kernel from a few days back seems ok... i'm going to get an etherexpress PRO kinda soon hopefully. if anyone with the knowhow could take a look at the de driver i guess that makes 2 people seeing instability because of the code. thanks, -Alfred On Wed, 15 Jul 1998, Richard Wackerbarth wrote: > >my crash info should have hit the lists already (panic and backtrace and > >dmesg) so i'm not going to repost it. > > > >unfortunatly i had already cvsup'd over the kernel i had compiled, my > >"stable" kernel (without softupdates) is: > > > >FreeBSD bright.ny.otec.com 3.0-CURRENT FreeBSD 3.0-CURRENT #6: Thu Jul 2 > >14:36:20 EST 1998 > >bright@bright.ny.otec.com:/usr/src/sys/compile/bright i386 > > > >my bad kernel is: > >-r-xr-xr-x 1 root wheel 1464261 Jul 14 17:08 /kernel > >(compiled july 14th) > > > >i'm going to compile a kernel with and without softupdates and test them > >later, but i've REALLY got to get to work right now, more later. > > Rather than removing the softupdate code from the kernel, you should > first try simply disabling it with tunefs. > > I suspect that your problem is actually with the "de" driver. > (I'm having the same problem with cvsup (no X) and no softupdates.) > > >#25 0xf01a19a5 in tulip_txput () > >#26 0xf01a1f8d in tulip_ifstart_one () > > Richard Wackerbarth > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message