Date: Fri, 16 May 2014 13:05:55 -0700 From: Adrian Chadd <adrian@freebsd.org> To: mexas@bris.ac.uk, "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>, =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= <trasz@freebsd.org> Subject: Re: Workaround for "fatal firmware error" iwn(4) problem. Message-ID: <CAJ-Vmo=D-ieSVK=m=z-C2j2t=0aqs=7MvPyXmCeEM%2BU7TgHyMg@mail.gmail.com> In-Reply-To: <201405161821.s4GILXit029854@mech-cluster241.men.bris.ac.uk> References: <8FB7D6BF-005A-41A1-9DCE-C8B09EA338EE@FreeBSD.org> <201405161821.s4GILXit029854@mech-cluster241.men.bris.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <mexas@bris.ac.uk> wrote: >>From: =?iso-8859-2?Q?Edward_Tomasz_Napiera=B3a?= <trasz@FreeBSD.org> >>Subject: Workaround for "fatal firmware error" iwn(4) problem. >>Date: Fri, 16 May 2014 20:06:02 +0200 >>To: "freebsd-hackers@freebsd.org" <freebsd-hackers@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-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=D-ieSVK=m=z-C2j2t=0aqs=7MvPyXmCeEM%2BU7TgHyMg>