Date: Mon, 20 Feb 2012 18:32:11 +0100 From: Bernhard Schmidt <bschmidt@freebsd.org> To: freebsd-net@freebsd.org Cc: Adam Twardowski <adam.twardowski@gmail.com>, Adrian Chadd <adrian@freebsd.org> Subject: Re: [urtw] Random wireless crash / kernel panic Message-ID: <201202201832.11604.bschmidt@freebsd.org> In-Reply-To: <CAEvxfZdAG8Tj%2BpUSKUKkpkAzmYohGQD6SZMiysqZpx1VT0Yn4Q@mail.gmail.com> References: <CAEvxfZdTxkN-BJnCa1kNYba0k1jA54aDinQ6d_jdYRUqhLATXQ@mail.gmail.com> <CAJ-Vmondt98a1gtmVL0kOrJYjTzq0psrEdN4bA=ZbPWHeMSv2g@mail.gmail.com> <CAEvxfZdAG8Tj%2BpUSKUKkpkAzmYohGQD6SZMiysqZpx1VT0Yn4Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 20 February 2012 18:03:45 Adam Twardowski wrote: > I do still have the kernel and the crash dump. I'll try that fix tonight > to see how it goes. Unfortunately, the kernel doesn't usually crash, more > likely the wifi stops working and I am forced to reboot the machine to get > 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 into 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 actually address the panic you're seeing, though, it doesn't fix the device timeout. [1] http://techwires.net/~bschmidt/urtw/ -- Bernhard
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201202201832.11604.bschmidt>