From owner-freebsd-stable@FreeBSD.ORG Sun Apr 3 00:22:48 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 36B6416A4CE for ; Sun, 3 Apr 2005 00:22:48 +0000 (GMT) Received: from innosense.washington.edu (c-67-171-35-77.hsd1.wa.comcast.net [67.171.35.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09BEA43D45 for ; Sun, 3 Apr 2005 00:22:48 +0000 (GMT) (envelope-from evantd@washington.edu) Received: by innosense.washington.edu (Postfix, from userid 1001) id D83C0C22B; Sat, 2 Apr 2005 16:22:34 -0800 (PST) Date: Sat, 2 Apr 2005 16:22:34 -0800 From: Evan Dower To: freebsd-stable@freebsd.org Message-ID: <20050403002234.GA53367@innosense.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: Recent NDIS Panics Appear To Be Solved X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Apr 2005 00:22:48 -0000 I recently experienced panics with dhclient ndis0 (ndis swi), and I saw that others had noticed similar problems. There is a PR or two about it at the moment. CVSUPping today solved the problem for me. So for those who had the problems, you may find them solved now. Ciao, -- Evan Dower Undergraduate, Computer Science University of Washington Public key: http://students.washington.edu/evantd/pgp-pub-key.txt Key fingerprint = D321 FA24 4BDA F82D 53A9 5B27 7D15 5A4F 033F 887D