Date: Tue, 11 Oct 2011 07:20:04 -0500 From: Chuck Burns <break19@gmail.com> To: PseudoCylon <moonlightakkiy@yahoo.ca> Subject: Re: [urtw] Wifi link dying randomly. reboot required to reconnect. Message-ID: <201110110720.04292.break19@gmail.com> Resent-Message-ID: <201110110721.45404.break19@gmail.com> In-Reply-To: <CAFZ_MY%2Bu=z7p%2BJdYeoU4hkh3vwzqTtMV0LV0Ddw26PmqhcJBwA@mail.gmail.com> References: <CAFZ_MY%2Bu=z7p%2BJdYeoU4hkh3vwzqTtMV0LV0Ddw26PmqhcJBwA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday, October 11, 2011 1:04:59 AM you wrote: > > Date: Thu, 6 Oct 2011 19:02:15 -0500 > > From: Chuck Burns <break19@gmail.com> > > Subject: Re: [urtw] Wifi link dying randomly. reboot required to > > reconnect. > > To: Gary Palmer <gpalmer@freebsd.org> > > Cc: freebsd-net@freebsd.org > > Message-ID: <201110061902.15838.break19@gmail.com> > > Content-Type: Text/Plain; charset="iso-8859-1" > > > > > > options KDB # Kernel debugger related code > > options KDB_TRACE # Print a stack trace for a panic > > #options KDB_UNATTENDED # Reboot on panic > > options WITNESS # add me > > > With run(4) (another usb dangle), there is a LOR between node lock and > driver lock in if_raw_xmit(). Maybe, stuck on sending mgmt frames -> > hang/disconnected from AP? > > With run(4), the LOR hasn't caused dead lock in 11abg mode, but in 11n > mode, it causes dead lock every time. You run it in 11g mode, but it > might be having bad hair day occasionally. Next time, rather than > unplugging the device to induce a panic, wait and see if the computer > will completely be locked up. > > > AK I've seen it completely lock up very seldomly.. But generally, if it hasn't locked up by the time I notice the connection is dead, it won't. I've added witness to options now. Chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201110110720.04292.break19>