From owner-freebsd-current@FreeBSD.ORG Wed Apr 21 18:12:40 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1366116A4CE for ; Wed, 21 Apr 2004 18:12:40 -0700 (PDT) Received: from ece.ufl.edu (dot.ece.ufl.edu [128.227.220.22]) by mx1.FreeBSD.org (Postfix) with SMTP id 8E6CF43D53 for ; Wed, 21 Apr 2004 18:12:39 -0700 (PDT) (envelope-from kawaja@ece.ufl.edu) Received: (qmail 34367 invoked by uid 0); 22 Apr 2004 01:12:36 -0000 Received: from kawaja@ece.ufl.edu by mail.ece.ufl.edu by uid 0 with qmail-scanner-1.14 (uvscan: v4.1.60/v4352. Clear:. Processed in 0.611604 secs); 22 Apr 2004 01:12:36 -0000 Received: from casper.ece.ufl.edu (128.227.180.133) by dot.ece.ufl.edu with SMTP; 22 Apr 2004 01:12:35 -0000 Date: Wed, 21 Apr 2004 21:14:29 -0400 (EDT) From: jason kawaja To: freebsd-current@freebsd.org In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Qmail-Scanner: uvscan: v4.1.60/v4352. Subject: Re: [ndis] [locking] intel 2100 3b X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Apr 2004 01:12:40 -0000 On Wed, 21 Apr 2004, jason kawaja wrote: > On Wed, 21 Apr 2004, jason kawaja wrote: > > > On Wed, 21 Apr 2004, jason kawaja wrote: > > > > > On Mon, 19 Apr 2004, jason kawaja wrote: > > > > > > > i get approximately 15-30 seconds and then my system locks up, > > > > no keyboard...nothing. power cycle is the only remedy. no logs > > > > of what is going on that i can see. [snip trial and error descriptions] [snip announcement of wpaul submissions on this issue] > i ended up cvsup'ing my entire system, remaking world and kernel and > the following occurs now : > > interface ndis0 now loads and stays up for about 3-5 minutes (this is > longer than the previous 15-30 seconds) but then my sysem locks once > again in the same fashion as before. uh, brought system home and powered it up, all is fine (using ndis0 right now). until i (or others) notice otherwise, this issue is resolved. -- Jason Kawaja http://www.ietf.org/rfc/rfc1855.txt