Date: Thu, 22 May 2014 10:54:39 -0700 From: Sean Bruno <sbruno@ignoranthack.me> To: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= <trasz@FreeBSD.org>, sbruno@freebsd.org Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@FreeBSD.org> Subject: Re: Workaround for "fatal firmware error" iwn(4) problem. Message-ID: <3am0iq7vn2l3np23f77vm5hm.1400781279549@email.android.com>
index | next in thread | raw e-mail
Restarting the interface manually works. -------- Original message -------- From: Edward Tomasz Napierała <trasz@FreeBSD.org> Date:05/22/2014 10:40 AM (GMT-07:00) To: sbruno@freebsd.org Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@FreeBSD.org> Subject: Re: Workaround for "fatal firmware error" iwn(4) problem. Wiadomość napisana przez Sean Bruno w dniu 22 maj 2014, o godz. 19:19: > On Fri, 2014-05-16 at 20:06 +0200, Edward Tomasz Napierała wrote: >> I've started using FreeBSD laptop and iwn(4) failing at random moments >> like this... >> >> May 16 17:11:54 brick kernel: iwn0: iwn_intr: fatal firmware error > > > so, interesting. iwi(4) seems to do the same thing. I'm not sure > what's up, but I've been trying to pin it down. It seems to already have the required code, iwi_restart(). Doesn't it work?help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3am0iq7vn2l3np23f77vm5hm.1400781279549>
