Arch Linux

r2b2

Member

Registered: 2013-08-12

Posts: 14

Wireless not reassociating with AP after suspend/resume cycle

Apologies if this is answered somewhere else but can't find anything that fits the bill.

I'm having issues getting my Wireless to reassociate with the AP after I suspend and then resume my PC.

I've got my netctl-auto@enp5s0.service running and when the system first starts up the network comes up fine. However following a sleep/resume, I have to issue a systemctl restart netctl-auto@enp5s0.service to get the network up and running again. (Yes, the name is enp5s0 but its really a wireless interface - honest )

iwconfig & iwlist show that following a resume the interface is up and running, it just doesn't reconnect to the AP.

Any assistance greatly appreciated! Please let me know what further info might be needed to diagnose the issue.

Richard.

r0b0t

Member

From: /tmp

Registered: 2009-05-24

Posts: 507

Re: Wireless not reassociating with AP after suspend/resume cycle

What does the log says? systemctl?

r2b2

Member

Registered: 2013-08-12

Posts: 14

Re: Wireless not reassociating with AP after suspend/resume cycle

What does the log says? systemctl?

A  log from journalctl after a 'systemctl restart netctl-auto@enp5s0.service' seems to show:

Aug 13 20:25:33 voxarch kernel: RX DESC ffff880037c45000  size = 2048
Aug 13 20:25:33 voxarch kernel: RTMP_TimerListAdd: add timer obj ffffc900131029c8!
Aug 13 20:25:33 voxarch kernel: RTMP_TimerListAdd: add timer obj ffffc90013102a38!
Aug 13 20:25:33 voxarch kernel: RTMP_TimerListAdd: add timer obj ffffc90013102aa8!
Aug 13 20:25:33 voxarch kernel: RTMP_TimerListAdd: add timer obj ffffc90013102958!
Aug 13 20:25:33 voxarch kernel: RTMP_TimerListAdd: add timer obj ffffc90013102808!
Aug 13 20:25:33 voxarch kernel: RTMP_TimerListAdd: add timer obj ffffc90013102878!
Aug 13 20:25:33 voxarch kernel: RTMP_TimerListAdd: add timer obj ffffc900130ccd88!
Aug 13 20:25:33 voxarch kernel: RTMP_TimerListAdd: add timer obj ffffc900130ccdf8!
Aug 13 20:25:33 voxarch kernel: RTMP_TimerListAdd: add timer obj ffffc900130ccca0!
Aug 13 20:25:33 voxarch kernel: RTMP_TimerListAdd: add timer obj ffffc900130bbb90!
Aug 13 20:25:33 voxarch kernel: RTMP_TimerListAdd: add timer obj ffffc900130bbc08!
Aug 13 20:25:33 voxarch kernel: RTMP_TimerListAdd: add timer obj ffffc900130ccbc0!
Aug 13 20:25:33 voxarch kernel: RTMP_TimerListAdd: add timer obj ffffc900130cce88!
Aug 13 20:25:33 voxarch kernel: Key1Str is Invalid key length(0) or Type(0)
Aug 13 20:25:33 voxarch kernel: Key2Str is Invalid key length(0) or Type(0)
Aug 13 20:25:33 voxarch kernel: Key3Str is Invalid key length(0) or Type(0)
Aug 13 20:25:33 voxarch kernel: Key4Str is Invalid key length(0) or Type(0)
Aug 13 20:25:33 voxarch kernel: 1. Phy Mode = 9
Aug 13 20:25:33 voxarch kernel: 2. Phy Mode = 9
Aug 13 20:25:33 voxarch kernel: NVM is Efuse and its size =2d[2d0-2fc] 
Aug 13 20:25:33 voxarch kernel: 3. Phy Mode = 9
Aug 13 20:25:33 voxarch kernel: [53B blob data]
Aug 13 20:25:33 voxarch kernel: RTMPSetPhyMode: channel is out of range, use first channel=1 
Aug 13 20:25:33 voxarch kernel: MCS Set = ff ff 00 00 01
Aug 13 20:25:33 voxarch kernel: <==== rt28xx_init, Status=0
Aug 13 20:25:33 voxarch kernel: 0x1300 = 00064300
Aug 13 20:25:33 voxarch kernel:  AUX_CTRL = 0x                            5c42
Aug 13 20:25:33 voxarch kernel:  Read AUX_CTRL = 0x5c42
Aug 13 20:25:33 voxarch kernel:  Write AUX_CTRL = 0x5c42
Aug 13 20:25:33 voxarch kernel:  OSC_CTRL = 0x3ff11
Aug 13 20:25:33 voxarch kernel: ====> rt30xx Read PowerLevelMode =  0x3.
Aug 13 20:25:33 voxarch kernel: ====> rt30xx F Write 0x83 Command = 0x3.

Whilst one from after a resume shows:

Aug 13 20:16:19 voxarch kernel: RX DESC ffff880037c45000  size = 2048
Aug 13 20:16:19 voxarch kernel: RTMP_TimerListAdd: add timer obj ffffc900131029c8!
Aug 13 20:16:19 voxarch kernel: RTMP_TimerListAdd: add timer obj ffffc90013102a38!
Aug 13 20:16:19 voxarch kernel: RTMP_TimerListAdd: add timer obj ffffc90013102aa8!
Aug 13 20:16:19 voxarch kernel: RTMP_TimerListAdd: add timer obj ffffc90013102958!
Aug 13 20:16:19 voxarch kernel: RTMP_TimerListAdd: add timer obj ffffc90013102808!
Aug 13 20:16:19 voxarch kernel: RTMP_TimerListAdd: add timer obj ffffc90013102878!
Aug 13 20:16:19 voxarch kernel: RTMP_TimerListAdd: add timer obj ffffc900130ccd88!
Aug 13 20:16:19 voxarch kernel: RTMP_TimerListAdd: add timer obj ffffc900130ccdf8!
Aug 13 20:16:19 voxarch kernel: RTMP_TimerListAdd: add timer obj ffffc900130ccca0!
Aug 13 20:16:19 voxarch kernel: RTMP_TimerListAdd: add timer obj ffffc900130bbb90!
Aug 13 20:16:19 voxarch kernel: RTMP_TimerListAdd: add timer obj ffffc900130bbc08!
Aug 13 20:16:19 voxarch kernel: RTMP_TimerListAdd: add timer obj ffffc900130ccbc0!
Aug 13 20:16:19 voxarch kernel: RTMP_TimerListAdd: add timer obj ffffc900130cce88!
Aug 13 20:16:19 voxarch kernel: Key1Str is Invalid key length(0) or Type(0)
Aug 13 20:16:19 voxarch kernel: Key2Str is Invalid key length(0) or Type(0)
Aug 13 20:16:19 voxarch kernel: Key3Str is Invalid key length(0) or Type(0)
Aug 13 20:16:19 voxarch kernel: Key4Str is Invalid key length(0) or Type(0)
Aug 13 20:16:19 voxarch kernel: 1. Phy Mode = 9
Aug 13 20:16:19 voxarch kernel: 2. Phy Mode = 9
Aug 13 20:16:19 voxarch kernel: NVM is Efuse and its size =2d[2d0-2fc] 
Aug 13 20:16:19 voxarch kernel: 3. Phy Mode = 9
Aug 13 20:16:19 voxarch kernel: [53B blob data]
Aug 13 20:16:19 voxarch kernel: RTMPSetPhyMode: channel is out of range, use first channel=1 
Aug 13 20:16:19 voxarch kernel: MCS Set = ff ff 00 00 01
Aug 13 20:16:19 voxarch kernel: <==== rt28xx_init, Status=0
Aug 13 20:16:19 voxarch kernel: 0x1300 = 000a4300
Aug 13 20:16:19 voxarch kernel:  AUX_CTRL = 0x                            4c02
Aug 13 20:16:19 voxarch kernel:  Read AUX_CTRL = 0x4c02
Aug 13 20:16:19 voxarch kernel:  Write AUX_CTRL = 0x5c02
Aug 13 20:16:19 voxarch kernel:  OSC_CTRL = 0x3ff11
Aug 13 20:16:19 voxarch kernel: ====> rt30xx Read PowerLevelMode =  0x3.
Aug 13 20:16:19 voxarch kernel: ====> rt30xx F Write 0x83 Command = 0x3.
Aug 13 20:16:19 voxarch kernel: ERROR!!! H2M_MAILBOX still hold by MCU. command fail
Aug 13 20:16:19 voxarch kernel: ERROR!!! H2M_MAILBOX still hold by MCU. command fail

By the looks the AUX_CTRL value is different and there's the H2M_MAILBOX error but these appear to be the only difference.

systemctl status netctl-auto@enp5s0.service doesnt't appear to log anything after resume (i.e. it doesn't appear to get restarted - not sure if that's normal or not)

r0b0t

Member

From: /tmp

Registered: 2009-05-24

Posts: 507

Re: Wireless not reassociating with AP after suspend/resume cycle

It sounds like a ralink (if that's the driver) issue, would try looking for some already open bug or open a new one if the issue is persistent with this device...

r2b2

Member

Registered: 2013-08-12

Posts: 14

Re: Wireless not reassociating with AP after suspend/resume cycle

It sounds like a ralink (if that's the driver) issue, would try looking for some already open bug or open a new one if the issue is persistent with this device...

That's what I suspected but hoped wasn't the case. I've had to compile an older driver downloaded from Ralink's website as that appears to be the only way I can get my wireless card to go above about 10mbps and not drop packets all other the place. So I'm not sure how much help I'll find out there.

However I have managed to work around it by putting a systemd hook in to restart the netctl-auto on resume so that seems to work around the issue which is good so not too much of an issue now.

Thanks for taking a look.