Toshiba Portage R930 (Intel 6235) WiFi Problem after Suspend

rocktorrentz · 2014-04-29 21:21:54

I've just come back to Arch (by way of archbang) after a bit of a hiatus from Linux tinkering and some time using Lubuntu. It's good to be back.

However I've got one problem with my shiny new laptop which I didn't have with fedora, the only other distro I've had on this machine so far. After I open the lid to wake up from suspend the wifi repeatedly tries to reauthentiate but fails. Connecting to my other SSID (I have one for 5GHz and one for 2.4GHz) sometimes resolves it but sometimes I have to reboot.

Here is the card I'm using:

04:00.0 Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)

Here are the journal logs from a normal authentication after a reboot (journalctl _TRANSPORT=kernel | grep wlp4s0):

Apr 29 22:06:50 river systemd-udevd[172]: renamed network interface wlan0 to wlp4s0
Apr 29 22:06:59 river kernel: IPv6: ADDRCONF(NETDEV_UP): wlp4s0: link is not ready
Apr 29 22:07:02 river kernel: wlp4s0: authenticate with 10:0d:7f:0d:7a:38
Apr 29 22:07:02 river kernel: wlp4s0: send auth to 10:0d:7f:0d:7a:38 (try 1/3)
Apr 29 22:07:02 river kernel: wlp4s0: authenticated
Apr 29 22:07:02 river kernel: wlp4s0: associate with 10:0d:7f:0d:7a:38 (try 1/3)
Apr 29 22:07:02 river kernel: wlp4s0: RX AssocResp from 10:0d:7f:0d:7a:38 (capab=0x411 status=0 aid=3)
Apr 29 22:07:02 river kernel: wlp4s0: associated
Apr 29 22:07:02 river kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready

When I'm having a problem after waking up the laptop:

Apr 29 22:01:59 river kernel: IPv6: ADDRCONF(NETDEV_UP): wlp4s0: link is not ready
Apr 29 22:02:05 river kernel: wlp4s0: authenticate with 10:0d:7f:1a:91:60
Apr 29 22:02:05 river kernel: wlp4s0: send auth to 10:0d:7f:1a:91:60 (try 1/3)
Apr 29 22:02:05 river kernel: wlp4s0: authenticated
Apr 29 22:02:05 river kernel: wlp4s0: associate with 10:0d:7f:1a:91:60 (try 1/3)
Apr 29 22:02:05 river kernel: wlp4s0: RX AssocResp from 10:0d:7f:1a:91:60 (capab=0x411 status=0 aid=3)
Apr 29 22:02:05 river kernel: wlp4s0: associated
Apr 29 22:02:05 river kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
Apr 29 22:02:05 river kernel: wlp4s0: deauthenticating from 10:0d:7f:1a:91:60 by local choice (reason=2)
Apr 29 22:02:05 river kernel: wlp4s0: authenticate with 10:0d:7f:1a:91:60
Apr 29 22:02:05 river kernel: wlp4s0: send auth to 10:0d:7f:1a:91:60 (try 1/3)
Apr 29 22:02:08 river kernel: wlp4s0: send auth to 10:0d:7f:1a:91:60 (try 2/3)
Apr 29 22:02:09 river kernel: wlp4s0: send auth to 10:0d:7f:1a:91:60 (try 3/3)
Apr 29 22:02:09 river kernel: wlp4s0: authentication with 10:0d:7f:1a:91:60 timed out
Apr 29 22:02:31 river kernel: wlp4s0: authenticate with 00:00:00:00:00:00
Apr 29 22:02:31 river kernel: wlp4s0: send auth to 00:00:00:00:00:00 (try 1/3)
Apr 29 22:02:31 river kernel: wlp4s0: send auth to 00:00:00:00:00:00 (try 2/3)
Apr 29 22:02:31 river kernel: wlp4s0: send auth to 00:00:00:00:00:00 (try 3/3)
Apr 29 22:02:31 river kernel: wlp4s0: authentication with 00:00:00:00:00:00 timed out
Apr 29 22:02:34 river kernel: wlp4s0: authenticate with 10:0d:7f:1a:91:60
Apr 29 22:02:34 river kernel: wlp4s0: direct probe to 10:0d:7f:1a:91:60 (try 1/3)
Apr 29 22:02:35 river kernel: wlp4s0: direct probe to 10:0d:7f:1a:91:60 (try 2/3)
Apr 29 22:02:35 river kernel: wlp4s0: direct probe to 10:0d:7f:1a:91:60 (try 3/3)
Apr 29 22:02:35 river kernel: wlp4s0: authentication with 10:0d:7f:1a:91:60 timed out
Apr 29 22:02:56 river kernel: wlp4s0: authenticate with 00:00:00:00:00:00
Apr 29 22:02:56 river kernel: wlp4s0: send auth to 00:00:00:00:00:00 (try 1/3)
Apr 29 22:02:56 river kernel: wlp4s0: send auth to 00:00:00:00:00:00 (try 2/3)
Apr 29 22:02:56 river kernel: wlp4s0: send auth to 00:00:00:00:00:00 (try 3/3)
Apr 29 22:02:56 river kernel: wlp4s0: authentication with 00:00:00:00:00:00 timed out
Apr 29 22:03:00 river kernel: wlp4s0: authenticate with 10:0d:7f:1a:91:60
Apr 29 22:03:00 river kernel: wlp4s0: direct probe to 10:0d:7f:1a:91:60 (try 1/3)
Apr 29 22:03:00 river kernel: wlp4s0: direct probe to 10:0d:7f:1a:91:60 (try 2/3)
Apr 29 22:03:01 river kernel: wlp4s0: direct probe to 10:0d:7f:1a:91:60 (try 3/3)
Apr 29 22:03:01 river kernel: wlp4s0: authentication with 10:0d:7f:1a:91:60 timed out
Apr 29 22:03:24 river kernel: wlp4s0: authenticate with 00:00:00:00:00:00
Apr 29 22:03:24 river kernel: wlp4s0: send auth to 00:00:00:00:00:00 (try 1/3)
Apr 29 22:03:24 river kernel: wlp4s0: send auth to 00:00:00:00:00:00 (try 2/3)
Apr 29 22:03:24 river kernel: wlp4s0: send auth to 00:00:00:00:00:00 (try 3/3)
Apr 29 22:03:24 river kernel: wlp4s0: authentication with 00:00:00:00:00:00 timed out
Apr 29 22:03:37 river kernel: wlp4s0: authenticate with 10:0d:7f:1a:91:60
Apr 29 22:03:37 river kernel: wlp4s0: direct probe to 10:0d:7f:1a:91:60 (try 1/3)
Apr 29 22:03:37 river kernel: wlp4s0: direct probe to 10:0d:7f:1a:91:60 (try 2/3)
Apr 29 22:03:38 river kernel: wlp4s0: direct probe to 10:0d:7f:1a:91:60 (try 3/3)
Apr 29 22:03:38 river kernel: wlp4s0: authentication with 10:0d:7f:1a:91:60 timed out
Apr 29 22:03:52 river kernel: wlp4s0: authenticate with 00:00:00:00:00:00
Apr 29 22:03:52 river kernel: wlp4s0: send auth to 00:00:00:00:00:00 (try 1/3)
Apr 29 22:03:52 river kernel: wlp4s0: send auth to 00:00:00:00:00:00 (try 2/3)
Apr 29 22:03:52 river kernel: wlp4s0: send auth to 00:00:00:00:00:00 (try 3/3)
Apr 29 22:03:52 river kernel: wlp4s0: authentication with 00:00:00:00:00:00 timed out

Any ideas what could be causing this? I sadly can't find anything after much searching around.

Rexilion · 2014-04-30 09:02:20

What kernel did you use under Fedora? Maybe using the same kernel will help. We could then work from there.

rocktorrentz · 2014-04-30 20:01:36

Rexilion wrote:

What kernel did you use under Fedora? Maybe using the same kernel will help. We could then work from there.

My really unhelpful answer is: Whatever the default kernel is in fedora 20. Although I did install x86 by accident so that could have had some impact.

I'll try a few other kernels from the aur and see if it makes any difference. Currently building linux-mainline.

Thanks
Sam

rocktorrentz · 2014-05-01 20:52:40

Had a few issues with the mainline kernel unrelated to wi-fi (I think it was UEFI related). However I've just installed the 3.13.11-2-ck kernel and things are looking good so far. Thanks for the pointer.

Rexilion · 2014-05-02 05:16:36

rocktorrentz wrote:

Had a few issues with the mainline kernel unrelated to wi-fi (I think it was UEFI related). However I've just installed the 3.13.11-2-ck kernel and things are looking good so far. Thanks for the pointer.

Kewl. If you had some spare time, you could do the following:

- try a latest git kernel (see if it fixes it)
- if the latest git kernel does not work, try a git bisect and report an upstream bug

However, bisecting takes quite a while.

Arch Linux

#1 2014-04-29 21:21:54

Toshiba Portage R930 (Intel 6235) WiFi Problem after Suspend

#2 2014-04-30 09:02:20

Re: Toshiba Portage R930 (Intel 6235) WiFi Problem after Suspend

#3 2014-04-30 20:01:36

Re: Toshiba Portage R930 (Intel 6235) WiFi Problem after Suspend

#4 2014-05-01 20:52:40

Re: Toshiba Portage R930 (Intel 6235) WiFi Problem after Suspend

#5 2014-05-02 05:16:36

Re: Toshiba Portage R930 (Intel 6235) WiFi Problem after Suspend

Board footer