Summary: | iwm: Wireless device not working after resume | ||||||
---|---|---|---|---|---|---|---|
Product: | Base System | Reporter: | Oleksandr Kryvulia <o.kryvulia> | ||||
Component: | wireless | Assignee: | freebsd-wireless (Nobody) <wireless> | ||||
Status: | Closed Unable to Reproduce | ||||||
Severity: | Affects Only Me | CC: | adrian, avg, markj | ||||
Priority: | --- | Keywords: | patch | ||||
Version: | CURRENT | ||||||
Hardware: | amd64 | ||||||
OS: | Any | ||||||
Attachments: |
|
Description
Oleksandr Kryvulia
2020-06-05 12:14:30 UTC
Which revision are you running? r361273 might be relevant. r361662 Created attachment 215252 [details]
proposed patch
Thanks. Could you please try the attached patch?
Your patch doesn't help, same errors. Thank you. I'm not able to reproduce this on a laptop with a 8265 chip. You might try seeing if reverting r361662 fixes the problem. And of course, make sure that the rfkill switch is not actually engaged. :) I installed FreeBSD into this laptop (Lenovo Thinkpad E540) in February 2020 and wireless never works after suspend-resume. So my problem is not related to r361662. Pressing wireless switch on keyboard (Fn+F8) doesn't make any difference. Only reboot needed. hi! Just try disabling the rfkill path totally: edit if_iwm_pcie_trans.c, go to the function named iwm_check_rfkill() and change "return rv" to "return 0". I dont' know if the hardware is active or not at this point, but at least we'll know it's not because it's getting a spurious rfkill interrupt or something. hi! Just try disabling the rfkill path totally: edit if_iwm_pcie_trans.c, go to the function named iwm_check_rfkill() and change "return rv" to "return 0". I dont' know if the hardware is active or not at this point, but at least we'll know it's not because it's getting a spurious rfkill interrupt or something. Hi! Disabling rfkill doesn't change anything. May be it's related to some ACPI issue? (In reply to Alexandr Krivulya from comment #9) Could you try to debug it further? E.g., you can add printf-s to see why the code decides that "radio is disabled by hardware switch" and so on. Nobody else can reproduce this problem, so unless you debug your issue, there's a little chance that it would be fixed. It is not reproducible any more, so may be closed. Thank you. |