Date: Thu, 2 Mar 2017 00:34:57 -0800 From: Adrian Chadd <adrian.chadd@gmail.com> To: Olivier Houchard <cognet@ci0.org> Cc: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org> Subject: Re: if_iwm issue Message-ID: <CAJ-Vmo=nGRJLj0YBCXqM%2BS3fFn1nBFurrjhQkZLrDctSg7oOqg@mail.gmail.com> In-Reply-To: <20170216225644.GA72987@ci0.org> References: <20170216225644.GA72987@ci0.org>
next in thread | previous in thread | raw e-mail | index | archive | help
hows head behaving now? -a On 16 February 2017 at 14:56, Olivier Houchard <cognet@ci0.org> wrote: > Hi, > > Since r313430, the one that removed the delay after fw loading, my iwm > device became unusable. > When loading the module, I get : > iwm0: <Intel Dual Band Wireless AC 8260> mem 0xdcd00000-0xdcd01fff at > device 0.0 > on pci2 > iwm0: hw rev 0x200, fw ver 16.242414.0, address e4:b3:18:fb:f3:6a > wlan0: Ethernet address: e4:b3:18:fb:f3:6a > iwm0: iwm_post_alive: sched addr mismatch: alive: 0x817080 prph: > 0x800000 > iwm0: dumping device error log > iwm0: Start Error Log Dump: > [dump available on request] > iwm0: iwm_intr: controller panicked, iv_state = 0; restarting > wlan0: ieee80211_new_state_locked: pending INIT -> SCAN transition lost > iwm0: failed to send bt coex configuration: 35 > iwm_run_init_mvm_ucode: failed 35 > iwm_init_hw failed 35 > in a loop. > > Reverting that particular revision fixes the issue for me. > I'm of course willing to act as a guinea pig, please let me know if > you need me to test anything. > > Regards, > > Olivier > > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=nGRJLj0YBCXqM%2BS3fFn1nBFurrjhQkZLrDctSg7oOqg>