From owner-freebsd-drivers@FreeBSD.ORG Tue Nov 6 18:27:50 2007 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 03ACB16A419; Tue, 6 Nov 2007 18:27:50 +0000 (UTC) (envelope-from doug@polands.org) Received: from ms-smtp-03.rdc-kc.rr.com (ms-smtp-03.rdc-kc.rr.com [24.94.166.129]) by mx1.freebsd.org (Postfix) with ESMTP id B23B013C48D; Tue, 6 Nov 2007 18:27:49 +0000 (UTC) (envelope-from doug@polands.org) Received: from corinth.polands.org (CPE-75-87-219-217.new.res.rr.com [75.87.219.217]) by ms-smtp-03.rdc-kc.rr.com (8.13.6/8.13.6) with ESMTP id lA6IK7UN002564; Tue, 6 Nov 2007 12:20:08 -0600 (CST) Received: from omnihp-rj45.polands.org (ammon.polands.org [172.16.1.7]) by corinth.polands.org (8.13.8/8.13.8) with ESMTP id lA6IRNO6008324; Tue, 6 Nov 2007 12:27:23 -0600 (CST) (envelope-from doug@polands.org) Message-ID: <4730B20A.3070807@polands.org> Date: Tue, 06 Nov 2007 12:27:22 -0600 From: Doug Poland User-Agent: Thunderbird 2.0.0.6 (X11/20071031) MIME-Version: 1.0 To: Frank Staals References: <472A6708.9030109@clearchain.com> <472B779B.9060002@gmx.net> <472B9597.2050108@clearchain.com> <473082C5.5080700@gmx.net> In-Reply-To: <473082C5.5080700@gmx.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Virus-Scanned: ClamAV 0.88.4/4682/Tue Nov 6 09:42:37 2007 on corinth.polands.org X-Virus-Status: Clean Cc: freebsd-current , freebsd-drivers@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: [RFT] Intel 3945abg wireless driver (wpi) X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Nov 2007 18:27:50 -0000 Frank Staals wrote: > Benjamin Close wrote: >> Frank Staals wrote: > >>> >>> >>> Everything works fine with the connection itself. Allthough sometimes >>> when switching from tty9 to tty0 and back the system locks up. I've >>> had it before when switching from tty1 to tty0. Anyone with the same >>> problems ? >>> >>> Anyway; Great work on the driver so far :D >>> >> I've similar issues and believe it might be due to the amount of >> kernel printfs that are happening. Can you sysctl debug.wpi=0 and see >> if the problem still exists? >> By chance are you using ZFS? I caught a memory modified after free >> panic in zfs the other day pid was from syslogd. I'm trying to work >> out if it's related. >> >> Cheers, >> Benjamin >> > When setting debug.wpi to 0 it seems like the problem is gone. I'm not > using ZFS by the way. I did have a problem connecting to the AP at my > university though; the driver wouldn't assosicate whatever I tried. I > didn't have a chance to do some extensive testing though. It might be > because of the WEP+wpa_supplicant + ca certificate method that is > required to authenticate. Anyway I'll let it know if there is an actual > problem with the driver itself > > Regards, > Setting debug.wpi=0 eliminated the lock ups when switching between tty[0-8] for me. -- Regards, Doug