idualwifi7260 doesn't connect

[korli]

using hrev52097 x86_64

KERN: PCI: [dom 0, bus  2] bus   2, device  0, function  0: vendor 8086, device 24fd, revision 78
KERN: PCI:   class_base 02, class_function 80, class_api 00
KERN: PCI:   vendor 8086: Intel Corporation
KERN: PCI:   device 24fd: Wireless 8265 / 8275
KERN: PCI:   info: Network controller
KERN: PCI:   line_size 10, latency 00, header_type 00, BIST 00
KERN: PCI:   ROM base host 00000000, pci 00000000, size 00000000
KERN: PCI:   cardbus_CIS 00000000, subsystem_id 0110, subsyKERN: stem_vendor_id 8086
KERN: PCI:   interrupt_line 0a, interrupt_pin 01, min_grant 00, max_latency 00
KERN: PCI:   base reg 0: host ef000000, pci ef000000, size 00002000, flags 04
KERN: PCI:   base reg 1: host 00000000, pci 00000000, size 00000000, flags 00
KERN: PCI:   base reg 2: host 00000000, pci 00000000, size 00000000, flags 00
KERN: PCI:   base reg 3: host 00000000, pci 00000000, size 00000000, flags 00
KERN: PCI:   base reg 4: host 00000000, pci 00000000, size 00000000, flags 00
KERN: PCI:   base reg 5: host 00000000, pci 00000000, size 00000000, flags 00
KERN: PCI:   Capabilities: PM, MSI, PCIe

[korli]

syslog

[korli]

syslog grepped for driver name

[waddlesplash]

KERN: [idualwifi7260] (iwm) iwm_intr: controller panicked, iv_state = 2; restarting
...
KERN: [idualwifi7260] (iwm) iwm_auth: failed to update power management
KERN: [idualwifi7260] (iwm) iwm_newstate: could not move to auth state: -2147483637

That looks to be the problem here. Can you test on FreeBSD 11.2, please? And if you haven't, compiling the driver with IWM_DEBUG enabled and the if-test later on in that file commented out so all prints are enabled might give some more insights.

I'll ask the FreeBSD folks if they know anything about this, though.

[korli]

I tested with the FreeBSD 11.2 memstick, the driver doesn't show up. I've verified the stick with the laptop with the Atheros wlan device, it works there. I've checked in /var/log/messages, no iwm related messages there. Any idea to get more logs in FreeBSD?

[waddlesplash]

I know there are some sysctls to enable more logging, but these only work after boot has completed, and so probably are not useful. You might need to manually enable a firmware if they haven't enabled it by default; but I've never had to do that so I'm not sure. (Maybe find me on IRC?)

[waddlesplash]

There are some commits in OpenBSD and DragonFlyBSD that might fix this. One of the FreeBSD developers said that he plans to cross-merge those within the next few weeks; so waiting for that might make sense.

[korli]

I tried 12.0-CURRENT, same behavior. Then I tried "kldload if_iwm", the driver is loaded, the correct firmware module appears loaded when listing with kldstat. I could then create the wlan interface, but wpa_supplicant returns an error about interfacing the driver.

[korli]

Maybe it would be better to remove the PCI id involved in a release.

[waddlesplash]

Well, if it doesn't KDL, what's the harm?

[waddlesplash]

So, I have actually seen this occur on my hardware now; it seems intermittent. On some reboots it happens 100% of the time, on others it never happens and I have WiFi. Talking to the FreeBSD guys, it seems the iwm driver is just very flaky in general...

[waddlesplash]

Please retest after hrev52722.

[waddlesplash]

If you haven't yet, please retest after hrev52792.

[waddlesplash]

At least I haven't seen those controller panics anymore after that commit, so, closing as fixed.

[nielx]

Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone