From owner-freebsd-net@FreeBSD.ORG  Tue Feb 21 02:45:54 2012
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 4F610106566B;
	Tue, 21 Feb 2012 02:45:54 +0000 (UTC)
	(envelope-from adam.twardowski@gmail.com)
Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com
	[209.85.210.182])
	by mx1.freebsd.org (Postfix) with ESMTP id 09BC98FC13;
	Tue, 21 Feb 2012 02:45:53 +0000 (UTC)
Received: by iaeo4 with SMTP id o4so11165357iae.13
	for <multiple recipients>; Mon, 20 Feb 2012 18:45:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:content-transfer-encoding;
	bh=W7chaDPZb9p3B5BML093frIdf64MP7JNj9E8zvTSwrg=;
	b=hfgbFSEVtr2nFBqoxWsndwv5E69dIgtJrUP8BwyXyjLpaD6YjwItkJeTUxpkhcU6M3
	SZzXnH9lvqYznUg41zo5I3eOyeKbHeYnNZTb5Fie+afH9vHaoVcrjYO2Ctck2mNVlQaf
	3nZa2/PpdZhv19RhwfiyNpuXaMmCMFo2tZhZ8=
MIME-Version: 1.0
Received: by 10.50.6.138 with SMTP id b10mr13601407iga.21.1329792353515; Mon,
	20 Feb 2012 18:45:53 -0800 (PST)
Received: by 10.231.45.202 with HTTP; Mon, 20 Feb 2012 18:45:53 -0800 (PST)
In-Reply-To: <201202201832.11604.bschmidt@freebsd.org>
References: <CAEvxfZdTxkN-BJnCa1kNYba0k1jA54aDinQ6d_jdYRUqhLATXQ@mail.gmail.com>
	<CAJ-Vmondt98a1gtmVL0kOrJYjTzq0psrEdN4bA=ZbPWHeMSv2g@mail.gmail.com>
	<CAEvxfZdAG8Tj+pUSKUKkpkAzmYohGQD6SZMiysqZpx1VT0Yn4Q@mail.gmail.com>
	<201202201832.11604.bschmidt@freebsd.org>
Date: Mon, 20 Feb 2012 21:45:53 -0500
Message-ID: <CAEvxfZc+F8K8u8eowBy9w7YffZDxRCz1QzM5bbBR2dCTdg-uSg@mail.gmail.com>
From: Adam Twardowski <adam.twardowski@gmail.com>
To: Bernhard Schmidt <bschmidt@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: freebsd-net@freebsd.org, Adrian Chadd <adrian@freebsd.org>
Subject: Re: [urtw] Random wireless crash / kernel panic
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2012 02:45:54 -0000

On Mon, Feb 20, 2012 at 12:32 PM, Bernhard Schmidt <bschmidt@freebsd.org> w=
rote:
> On Monday 20 February 2012 18:03:45 Adam Twardowski wrote:
>> I do still have the kernel and the crash dump. =A0I'll try that fix toni=
ght
>> to see how it goes. =A0Unfortunately, the kernel doesn't usually crash, =
more
>> likely the wifi stops working and I am forced to reboot the machine to g=
et
>> it working again.
>
> Building urtw(4) as module here helps a lot, kldunload/kldload is just so=
 much faster than a reboot. :)
>
> I have a bunch of asorted fixes [1] for urtw(4) which needs some further =
testing, though I still wasn't able to fix the issue which made me look int=
o this in the first place.. As a test case I force a disconnection from the=
 AP side a few times, which will eventually result in a device timeout and =
the requirement to reload the module. I believe that one of those might act=
ually address the panic you're seeing, though, it doesn't fix the device ti=
meout.
>
> [1] http://techwires.net/~bschmidt/urtw/
>
> --
> Bernhard

Bernhard,

I just applied your four patches and rebooted.  I also went with a
module like you suggested.  We will see how it goes.  I did not apply
Adrians change above, not sure if it was necessary.