> On Jun 7, 2018, at 7:59 AM, m...@netbsd.org wrote:
>
> You've changed a default and selectively fixed the one driver that
> people noticed breaks from it. How do you know the rest aren't broken?
As you know, there is very little certainty in this world. For example, how
can I be certain th
Hi,
From: Kengo NAKAHARA , Date: Fri, 8 Jun 2018 20:20:03
+0900
> Hi,
>
> Sorry, I checked it fixed panic only. iwm.c:r1.81 and r1.82 fix this problem
> at my environment.
>
> Could you try latest kernel with these commits?
Thank you very much for your quick fix.
It works fine now.
> Thanks,
Hi,
Sorry, I checked it fixed panic only. iwm.c:r1.81 and r1.82 fix this problem
at my environment.
Could you try latest kernel with these commits?
Thanks,
On 2018/06/09 3:14, Ryo ONODERA wrote:
> Hi,
>
> This change causes the following error and I cannot use iwm(4) device
> anymore.
> Could
Hi,
This change causes the following error and I cannot use iwm(4) device
anymore.
Could you take a look at my problem?
$ ifconfig iwm0
ifconfig: SIOCGIFFLAGS iwm0: Device not configured
dmesg is here:
(snip)
iwm0 at pci2 dev 0 function 0: vendor 8086 product 24fd (rev. 0x78)
iwm0: interrupting
