Date: Wed, 15 Jul 1998 16:08:46 -0500 (EST) From: Alfred Perlstein <bright@hotjobs.com> To: Richard Wackerbarth <rkw@Dataplex.Net> Cc: current@FreeBSD.ORG Subject: Re: repeatable crash with softupdates Message-ID: <Pine.BSF.3.96.980715160416.2699D-100000@bright.ny.otec.com> In-Reply-To: <l03130301b1d2b921a69b@[208.2.87.10]>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980715160416.2699D-100000>