It's likely part the firmware and pat the driver. Yeah, we need a way to recover from a firmware crash. I and others in the open source community don't have documentation to know what the hell is or isn't permissable with firmware :(
Ed - the reason why ieee80211_runtask() doesn't always run is because it can get paused during things like scanning and interface-down things. Your best bet is to create a new taskqueue in iwn and a task that runs on an iwn taskqueue. (And yeah, I really do need to rip out the taskqueue abuse by the net80211 scan code so a scan doesn't stop tasks from running. Grr.) -a On 16 May 2014 11:21, Anton Shterenlikht <me...@bris.ac.uk> wrote: >>From: =?iso-8859-2?Q?Edward_Tomasz_Napiera=B3a?= <tr...@freebsd.org> >>Subject: Workaround for "fatal firmware error" iwn(4) problem. >>Date: Fri, 16 May 2014 20:06:02 +0200 >>To: "freebsd-hack...@freebsd.org" <freebsd-hack...@freebsd.org> >> >>I've started using FreeBSD laptop and iwn(4) failing at random moments >>like this... > > see also > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/176104 > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/189802 > > BTW, I disabled iwn and tried pccard bwn device instead, > and the errors are gone. Also wireless doesn't disconnect > as it used to with iwn. This is just because I thought > my laptop or setup were to blame. So this is further > evidence that iwn driver is at fault. > > Anton > _______________________________________________ > freebsd-hack...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org" _______________________________________________ email@example.com mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"