From owner-freebsd-current@FreeBSD.ORG Tue Apr 20 05:44:05 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 175BD16A4D0 for ; Tue, 20 Apr 2004 05:44:05 -0700 (PDT) Received: from ece.ufl.edu (dot.ece.ufl.edu [128.227.220.22]) by mx1.FreeBSD.org (Postfix) with SMTP id 91F1143D5E for ; Tue, 20 Apr 2004 05:44:04 -0700 (PDT) (envelope-from kawaja@ece.ufl.edu) Received: (qmail 68830 invoked by uid 0); 20 Apr 2004 12:44:03 -0000 Received: from kawaja@ece.ufl.edu by mail.ece.ufl.edu by uid 0 with qmail-scanner-1.14 (uvscan: v4.1.60/v4351. Clear:. Processed in 0.615645 secs); 20 Apr 2004 12:44:03 -0000 Received: from casper.ece.ufl.edu (128.227.180.133) by dot.ece.ufl.edu with SMTP; 20 Apr 2004 12:44:02 -0000 Date: Tue, 20 Apr 2004 08:45:46 -0400 (EDT) From: jason kawaja To: freebsd-current@freebsd.org In-Reply-To: <20040420110955.A61955@pcle2.cc.univie.ac.at> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Qmail-Scanner: uvscan: v4.1.60/v4351. 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: Tue, 20 Apr 2004 12:44:05 -0000 On Tue, 20 Apr 2004, Lukas Ertl 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. > > Same here. I load if_ndis, and after some random time (sometimes a > few minutes, sometimes 20 minutes), the box locks up hard. Card is > also Intel P/W 2100 3b. > > Last known working kernel is from Apr 12th. ^^^^^^^ are you saying that a cvsup on 04-12-04 worked but now a more current cvsup has resulted in this locking behavior? is there someone out there that had this working at some point (or is still working)? -- Jason Kawaja http://www.ietf.org/rfc/rfc1855.txt