Date: Sun, 11 Aug 2013 23:02:14 -0400 From: Julio Merino <julio@meroh.net> To: Adrian Chadd <adrian@freebsd.org> Cc: freebsd-wireless@freebsd.org Subject: Re: kern/181100: [bwi] Turning up bwi0 crashes / deadlocks the kernel Message-ID: <CADyfeQWv6t8TuKZqTvtVUiQMNDcAsDZjsDzG_ooRxLgTSUuvcQ@mail.gmail.com> In-Reply-To: <CAJ-Vmo=u7VZjs0Nd0dGkaHNboNwUU=5N%2B25CT=0RfcT7kG0oVg@mail.gmail.com> References: <201308111650.r7BGo1Qt048071@freefall.freebsd.org> <CAJ-Vmo=u7VZjs0Nd0dGkaHNboNwUU=5N%2B25CT=0RfcT7kG0oVg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Aug 11, 2013 at 1:07 PM, Adrian Chadd <adrian@freebsd.org> wrote: > Hi! > > THanks for the report! Hi Adrian, Thanks for getting back to me so quickly. > This is my fault. But, is bwi actually doing 11n rates? I don't know. Is there a way to tell for sure? This machine is from ~2005 so I don't think so, but Wikipedia claims that work on 11n started in 2002... > On 11 August 2013 09:50, Julio Merino <julio@meroh.net> wrote: > >> bwi0: firmware rev 0x0127, patch level 0x000e >> panic: rate 130 is basic/mcs? > > See, that's just odd. If it's a non-11n (MCS) rate, then it should be > 2x the speed, which is 65MBit - which is odd, as that looks more like > an MCS rate speed than what the NIC should do. But is that related? The crash / freezes seem due to a locking issue. >From a very quick look at the code, the ioctl handler is holding the bwi mutex and then calls firmware_get, which goes to sleep possibly waiting for the disk. > Can you get a crashdump? Sure, but any hints at how? When the system enters kdb, I type "panic" as described in section 10.4 of the guide... and the system immediately reboots, without dumping core. Thanks, -- Julio Merino / @jmmv
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADyfeQWv6t8TuKZqTvtVUiQMNDcAsDZjsDzG_ooRxLgTSUuvcQ>