From owner-freebsd-current@FreeBSD.ORG Mon Sep 19 15:15:17 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 4CE1516A41F for ; Mon, 19 Sep 2005 15:15:17 +0000 (GMT) (envelope-from xi@borderworlds.dk) Received: from ferengi.borderworlds.dk (ferengi.borderworlds.dk [80.166.152.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id C7E3043D48 for ; Mon, 19 Sep 2005 15:15:16 +0000 (GMT) (envelope-from xi@borderworlds.dk) Received: from borg.borderworlds.dk (localhost [127.0.0.1]) by ferengi.borderworlds.dk (Postfix) with ESMTP id EF6DBB846 for ; Mon, 19 Sep 2005 17:15:14 +0200 (CEST) Received: by borg.borderworlds.dk (Postfix, from userid 1001) id BC2F911463; Mon, 19 Sep 2005 17:15:14 +0200 (CEST) Sender: xi@borderworlds.dk To: freebsd-current@freebsd.org References: <86ek7mssz0.fsf@borg.borderworlds.dk> <20050918114803.3fceca23.lists@yazzy.org> From: Christian Laursen Date: 19 Sep 2005 17:15:14 +0200 In-Reply-To: <20050918114803.3fceca23.lists@yazzy.org> Message-ID: <86wtld6qd9.fsf@borg.borderworlds.dk> Lines: 48 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: iwi lockup problem on 6.0-BETA4 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Sep 2005 15:15:17 -0000 Marcin Jessa writes: > This happened to me as well. > After update from a couple of days back (6.0-BETA4) it seems to be working fine. > And it does not constantly disconnect from my AP as it used to before. > Trying to make it connect back made my laptop reboot. Now I can even reconnect changing SSID's or after I lost contact with the AP. > Give it a try and let me know. Unfortunately it doesn't seem to make any difference. > On 18 Sep 2005 10:03:31 +0200 > Christian Laursen wrote: > > > I am having a problem using the iwi driver on my laptop. > > > > Basically I would normally setup the network with this command: > > ifconfig iwi0 inet 10.2.0.3 netmask 255.255.0.0 ssid borderworlds mode 11g channel 3 > > > > but that makes the laptop freeze and a hard reset is the only way to > > get it back to life. > > > > By experimenting a little I found that this sequence of commands works: > > > > ifconfig iwi0 inet 10.2.0.3 netmask 255.255.0.0 > > sleep 5 > > ifconfig iwi0 ssid borderworlds > > sleep 5 > > ifconfig iwi0 mode 11g > > sleep 5 > > ifconfig iwi0 channel 3 > > > > I tried sleep 1 at first but that made the laptop freeze after setting > > mode 11g. > > > > By enabling the software watchdog I can make it panic instead of > > freezing, but the backtrace I get from the dump looks useless (at least > > to me). > > > > The dmesg is at http://borderworlds.dk/~xi/andorian.dmesg > > The trace is at http://borderworlds.dk/~xi/andorian.trace > > > > I am not sure how to further debug this so any help would be > > appreciated. > > > > I will try the latest RELENG_6 next and see if it makes any difference. -- Christian Laursen