Opened 2 years ago

Closed 23 months ago

#17479 closed bug (not reproducible)

iprowifi4965 stops working after a while

Reported by: pulkomandy Owned by: waddlesplash
Priority: normal Milestone: Unscheduled
Component: Drivers/Network/iprowifi4965 Version: R1/beta3
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

After a while the wifi stops working. I'm disconnected and can't even scan available networks. This shows in the syslog when it happens:

KERN: [iprowifi4965] (iwn) iwn_tx_cmd: ni (0x81ea0000) or m (0xd4c3bc48) for idx 38 in queue 0 is not NULL!
KERN: Last message repeated 29 times.
KERN: Last message repeated 4 times.
KERN: : [iprowifi4965] device timeout
KERN: [net/iprowifi4965/0] stop running, 1 vaps running
KERN: [net/iprowifi4965/0] ieee80211_new_state_locked: RUN -> INIT (nrunning 0 nscanning 0)
KERN: ieee80211_notify_ifnet_change not implemented, yet.
KERN: [net/iprowifi4965/0] down parent 
KERN: [net/iprowifi4965/0] ieee80211_newstate_cb: RUN -> INIT arg -1
KERN: [net/iprowifi4965/0] sta_newstate: RUN -> INIT (-1)
KERN: [net/iprowifi4965/0] ieee80211_ref_node (ieee80211_send_mgmt:2647) 0x81ea0000<b8:26:6c:bf:26:27> refcnt 6
KERN: [net/iprowifi4965/0] [b8:26:6c:bf:26:27] send station disassociate (reason: 8 (sending STA is leaving/has left BSS))
KERN: ieee80211_notify_node_leave
KERN: [net/iprowifi4965/0] node_reclaim: remove 0x81ea0000<b8:26:6c:bf:26:27> from station table, refcnt 5
KERN: [net/iprowifi4965/0] ieee80211_alloc_node 0x89f80000<10:0b:a9:48:54:ec> in station table
KERN: [net/iprowifi4965/0] [10:0b:a9:48:54:ec] ieee80211_alloc_node: inact_reload 2
KERN: [net/iprowifi4965/0] start running, 0 vaps running
KERN: ieee80211_notify_ifnet_change not implemented, yet.
KERN: [net/iprowifi4965/0] ieee80211_start_locked: up parent 
KERN: wlan_control: 9234, 20
KERN: Last message repeated 2 times.
KERN: /dev/net/iprowifi4965/0: media change, media 0x100a0 quality 1000 speed 0
KERN: [iprowifi4965] (iwn) iwn_read_firmware: ucode rev=0x12a80601
KERN: ifmedia_ioctl: switching wlan to   Type: IEEE 802.11 Wireless Ethernet
KERN:   Mode: autoselect
KERN:   SubType: autoselect
KERN: wlan_control: 9234, 16
KERN: wlan_control: 9234, 17
KERN: wlan_control: 9234, 26
KERN: wlan_open(0xd3b87c00)
KERN: [net/iprowifi4965/0] ieee80211_init
KERN: [net/iprowifi4965/0] start running, 1 vaps running
Last message repeated 1 time
KERN: wlan_control: 9234, 103
KERN: [net/iprowifi4965/0] ieee80211_new_state_locked: INIT -> SCAN (nrunning 0 nscanning 0)
KERN: [iprowifi4965] (iwn) iwn5000_post_alive: crystal calibration failed, error -2147483637
KERN: [iprowifi4965] (iwn) iwn_init_locked: could not initialize hardware, error -2147483637
KERN: [net/iprowifi4965/0] stop running, 1 vaps running
KERN: [net/iprowifi4965/0] ieee80211_new_state_locked: pending INIT -> SCAN transition lost
KERN: [net/iprowifi4965/0] ieee80211_new_state_locked: INIT -> INIT (nrunning 0 nscanning 0)
KERN: ieee80211_notify_ifnet_change not implemented, yet.
KERN: [net/iprowifi4965/0] down parent 
KERN: [net/iprowifi4965/0] ieee80211_newstate_cb: INIT -> INIT arg -1
KERN: [net/iprowifi4965/0] sta_newstate: INIT -> INIT (-1)

Change History (5)

comment:1 by waddlesplash, 2 years ago

Please see if a pre-GCC11 build of the driver behaves any differently.

comment:2 by pulkomandy, 2 years ago

I can try, but it's hard to say because this does not happen predictably. Sometimes the wifi will work just fine for hours, and at some point it will stop this way.

I think we should at least improve our recovery from these errors, the drivers should manage to reinit things and reconnect?

comment:3 by waddlesplash, 23 months ago

The memory management fixes (ending with hrev56182) may affect this, if you have a chance to retest.

comment:4 by pulkomandy, 23 months ago

I can't easily test on this machine anymore because it's my homeserver now. If no one else has issues with this driver I'm fine with closing this.

comment:5 by waddlesplash, 23 months ago

Resolution: not reproducible
Status: newclosed

If anyone else has similar problems then we can open a new ticket and investigate that way, yes.

Note: See TracTickets for help on using tickets.