Bug 246965 - iwn_init_locked: could not initialize hardware, error 60
Summary: iwn_init_locked: could not initialize hardware, error 60
Status: Closed Overcome By Events
Alias: None
Product: Base System
Classification: Unclassified
Component: wireless (show other bugs)
Version: Unspecified
Hardware: amd64 Any
: --- Affects Some People
Assignee: freebsd-wireless (Nobody)
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2020-06-03 19:46 UTC by Jason W. Bacon
Modified: 2020-10-31 13:32 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jason W. Bacon freebsd_committer freebsd_triage 2020-06-03 19:46:29 UTC
Some recent update around February or March if I recall caused this issue to arise on my Lenovo X201.  The iwn WiFi had been working reliably for maybe a year before that.  It occurs on both 11.3-RELEASE and 12.1-RELEASE.  I swapped in a disk from another machine to test 11.3.

The iwn WiFi works fine for a while after a cold or warm boot, then suddenly goes dark after anywhere from a few minutes to maybe half an hour and logs the following:

May 24 11:57:39 mako kernel: iwn0: iwn_read_firmware: ucode rev=0x09dd0401
May 24 12:45:07 mako kernel: iwn0: iwn_read_firmware: ucode rev=0x09dd0401
May 24 12:50:34 mako kernel: iwn0: device timeout
May 24 12:50:34 mako kernel: iwn0: iwn_read_firmware: ucode rev=0x09dd0401
May 24 12:50:34 mako kernel: iwn0: iwn_hw_init: could not power ON adapter, error 60
May 24 12:50:34 mako kernel: iwn0: iwn_init_locked: could not initialize hardware, error 60

I confirmed that it's a FreeBSD regression and not a hardware failure by installing Debian on this machine.  Debian has its own set of issues, but the Intel WiFi works reliably.

Specs:

Jun  3 14:25:38 manatee kernel: iwn0: <Intel Centrino Advanced-N 6200> mem 0xf2400000-0xf2401fff irq 16 at device 0.0 on pci3
Jun  3 14:25:38 manatee kernel: iwn0: iwn_read_firmware: ucode rev=0x09dd0401
Comment 1 Adrian Chadd freebsd_committer freebsd_triage 2020-06-07 05:20:34 UTC
can you help figure out which release or head snapshot it last /did/ work in?

That'd help narrow things down.

Thanks!
Comment 2 Jason W. Bacon freebsd_committer freebsd_triage 2020-06-07 12:37:08 UTC
Did a little more investigation and it appears the problem arose with the release of 12.1. I did a fresh 12.1 install with no base updates and it does exhibit the problem.  I don't have written records, but I think I had run both 11.2 and 12.0 on this machine without any WiFi issues.
Comment 3 Mark Johnston freebsd_committer freebsd_triage 2020-06-09 14:39:35 UTC
(In reply to Jason W. Bacon from comment #2)
That points at r346037, which is a rather large commit unfortunately.  iwm has gotten a number of updates since 12.1, so it would also be worth testing a recent stable/12 kernel.
Comment 4 Mark Linimon freebsd_committer freebsd_triage 2020-06-23 21:38:06 UTC
^Triage: [tags] in issue Titles are deprecated
Comment 5 Jason W. Bacon freebsd_committer freebsd_triage 2020-10-03 22:42:43 UTC
Didn't see the last response until now.  I'll try 12.2-RC for starters.
Comment 6 Jason W. Bacon freebsd_committer freebsd_triage 2020-10-08 02:13:37 UTC
Still happening on 12.2-RC2.

The frequency of the issue has gone down since it first appeared.  It was generally happening within minutes when it first appeared, but much less frequently since the latest 12.1-RELEASE updates.  Today it ran all day with 12.2-RC1 before going down this evening.
Comment 7 Jason W. Bacon freebsd_committer freebsd_triage 2020-10-31 13:32:03 UTC
I'm running 12.2-RC3 now and haven't seen the issue in weeks.  I'll consider it resolved and reopen if it reappears.