From owner-freebsd-i386@FreeBSD.ORG Thu Apr 6 05:30:15 2006 Return-Path: X-Original-To: freebsd-i386@hub.freebsd.org Delivered-To: freebsd-i386@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DCDBD16A420 for ; Thu, 6 Apr 2006 05:30:14 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C4F743D46 for ; Thu, 6 Apr 2006 05:30:14 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k365UEPN084441 for ; Thu, 6 Apr 2006 05:30:14 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k365UEGt084440; Thu, 6 Apr 2006 05:30:14 GMT (envelope-from gnats) Resent-Date: Thu, 6 Apr 2006 05:30:14 GMT Resent-Message-Id: <200604060530.k365UEGt084440@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-i386@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Chris Thielen Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0FCE616A400 for ; Thu, 6 Apr 2006 05:29:23 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id CCEBC43D46 for ; Thu, 6 Apr 2006 05:29:17 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id k365TC06014255 for ; Thu, 6 Apr 2006 05:29:12 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id k365TC7g014253; Thu, 6 Apr 2006 05:29:12 GMT (envelope-from nobody) Message-Id: <200604060529.k365TC7g014253@www.freebsd.org> Date: Thu, 6 Apr 2006 05:29:12 GMT From: Chris Thielen To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Cc: Subject: i386/95392: Kernel panic loading ndisgen-created device drivers not found before 6.1 X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Apr 2006 05:30:15 -0000 >Number: 95392 >Category: i386 >Synopsis: Kernel panic loading ndisgen-created device drivers not found before 6.1 >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-i386 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Apr 06 05:30:12 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Chris Thielen >Release: 6.1-beta4 >Organization: None >Environment: $ uname -a FreeBSD localhost.localdomain 6.1-BETA4 FreeBSD 6.1-BETA4 #0: Tue Mar 14 13:59:38 UTC 2006 root@wv1u.samsco.home:/usr/obj/usr/src/sys/GENERIC i386 >Description: Using an eMachines m2350 laptop, with the Broadcom BCM4306 80211/b/g wireless NIC, I have used ndisgen from the Win2K drivers provided by Broadcom. This normally isn't a problem - the .ko file generates successfully in both 6.0 and 6.1beta4. I used the device driver over the course of months without a single problem in 6.0, but in 6.1beta4, with a fresh install and a fresh .ko file from ndisgen, I am seemingly randomly getting kernel panics. On boot, I am simply logging in, su'ing and kldload'ing the ndisgen-created .ko file and sometimes so, sometimes not, I get a complete kernel panic. The information isn't being dumped anywhere as it reports "no dump device specified" and then prompts me to hit a key to reboot. The oddity is that sometimes it works without a hitch, and it is _only_ on driver load. If the driver does load, I do not experience random kernel panics or anything using my wireless NIC for hours. It only occurs on kldload. >How-To-Repeat: Boot up, login in, su and simply run kldload on the ndisgen-created .ko device driver for the Broadcom device. >Fix: None, although the kernel panic only occurs in about 1 of every 2 cases, and in practice it's usually on a fresh boot so it's not too big a deal to just spend the extra 30 seconds to reboot, though it is a critical bug certainly. >Release-Note: >Audit-Trail: >Unformatted: