Alx driver issue after suspend

thepasto · 2013-09-21 06:05:29

Hi guys,

This is the problem i get when i resume my laptop after a suspend. Dmesg shows several lines like that:

alx 0000:04:00.0: invalid PHY speed/duplex: 0xffff

So wired network is not working, and after some minutes gnome hangs too and i need to reboot my computer.

Any suggenstion? thanks

beanaroo · 2013-09-23 07:54:35

I'm having the exact same problem.

alx 0000:02:00.0: invalid PHY speed/duplex: 0xffff

spams dmesg and renders the system unusable after two minutes.

gtolden · 2013-09-23 14:04:06

same problem, to make things worse, one of my 4 cpu cores get up to 100% usage and the system will hang after a while.

systemctl stop NetworkManager 
 ip link set enp3s0

before suspend seems to make things fine for me, but it is not a sensible choice

Is it a kernel bug?

Last edited by gtolden (2013-09-23 14:04:46)

thepasto · 2013-09-23 18:05:04

You can just rmmod alx before suspending. As i can remember the problem is always there since 3.10 kernel (alx merged into kernel tree)

gtolden · 2013-09-24 14:14:44

Anyone who can help? I can't always remember to type the command before I close my lid...

nfreitas · 2013-09-27 04:28:21

You could blacklist the alx module.

thepasto · 2013-09-27 13:55:10

I just found a better solution working for my case.

/etc/systemd/system/root-suspend.service

[Unit]
Description=Local system suspend actions
Before=sleep.target

[Service]
Type=simple
ExecStart=/usr/bin/rmmod alx

[Install]
WantedBy=suspend.target

/etc/systemd/system/root-resume.service

[Unit]
Description=Local system resume actions
After=suspend.target

[Service]
Type=simple
ExecStart=/usr/bin/modprobe alx

[Install]
WantedBy=suspend.target

and then just enable them:

sudo systemctl enable root-suspend
sudo systemctl enable root-resume

gtolden · 2013-10-01 05:52:21

thepasto wrote:

I just found a better solution working for my case.

/etc/systemd/system/root-suspend.service

[Unit]
Description=Local system suspend actions
Before=sleep.target

[Service]
Type=simple
ExecStart=/usr/bin/rmmod alx

[Install]
WantedBy=suspend.target

/etc/systemd/system/root-resume.service

[Unit]
Description=Local system resume actions
After=suspend.target

[Service]
Type=simple
ExecStart=/usr/bin/modprobe alx

[Install]
WantedBy=suspend.target

and then just enable them:

sudo systemctl enable root-suspend
sudo systemctl enable root-resume

Many thanks:)

bericp1 · 2013-10-09 20:21:22

thepasto wrote:

I just found a better solution working for my case.

/etc/systemd/system/root-suspend.service

[Unit]
Description=Local system suspend actions
Before=sleep.target

[Service]
Type=simple
ExecStart=/usr/bin/rmmod alx

[Install]
WantedBy=suspend.target

/etc/systemd/system/root-resume.service

[Unit]
Description=Local system resume actions
After=suspend.target

[Service]
Type=simple
ExecStart=/usr/bin/modprobe alx

[Install]
WantedBy=suspend.target

and then just enable them:

sudo systemctl enable root-suspend
sudo systemctl enable root-resume

Thanks, this helped me out. I knew the workaround probably involved systemd but I've yet to dive into how it works.

tazee · 2013-10-13 03:29:48

Thanks this helped me out too. The looping message and lagginess were very irritating and are now gone.

tazee · 2013-10-22 04:26:53

thepasto : your solution works good when I put my computer to sleep (Suspend to RAM), but it does not work for hibernate (Suspend to disk). I also would like something similar to work for hibernate too. What modification should I make?

thepasto · 2013-10-22 18:54:58

I think you create two files with the same structure using hibernate.target instead of suspend.target.

[Unit]
Description=Local system suspend actions
Before=sleep.target

[Service]
Type=simple
ExecStart=/usr/bin/rmmod alx

[Install]
WantedBy=hibernate.target

[Unit]
Description=Local system resume actions
After=hibernate.target

[Service]
Type=simple
ExecStart=/usr/bin/modprobe alx

[Install]
WantedBy=hibernate.target

And enable them.. Maybe you can do everything with 2 files but i'm not so good with systemd stuff

Good luck and let me know!!

beanaroo · 2013-10-22 22:22:02

@thepasto Thank you! Your solution is elegant and works perfectly.

tazee · 2013-10-23 01:44:56

@thepasto Thank you! This does work well. I did end up with 4 files. Two files for suspend to Ram and 2 files for suspend to disk. And because of this I learned a little bit more about systemd.

Last edited by tazee (2013-10-23 01:47:41)

anachron8 · 2013-10-28 19:05:12

I modified thepasto's suggested fix into a single file solution. It seems to work OK -- please report back if it doesn't

[Unit]
Description=Local system sleep actions
Before=sleep.target
PartOf=sleep.target

[Service]
Type=oneshot
RemainAfterExit=yes

# Commands to run when suspending or hibernating
ExecStart=/usr/bin/modprobe -r alx


# Commands to run when resuming or waking up
ExecStop=/usr/bin/modprobe alx


[Install]
WantedBy=sleep.target

tazee · 2013-10-29 04:23:45

anachron8 : will this work for both suspend to ram as well as suspend to disk?

aeqel · 2013-11-01 05:48:34

Confirming anachron8's solution worked for both suspend to ram and suspend to disk on my F201E.

tazee · 2013-11-04 06:38:36

Yes I tried it too. It works for both suspend to ram and suspend to disk. Thanks.

anachron8 · 2013-11-04 15:42:25

Sorry for not paying attention to this thread; I wasn't automatically subscribed when I posted.

It works for both suspend and hibernate because they both pull in sleep.target.

Multimoon · 2013-11-29 00:12:55

Someone should add this to the wiki. If noone does, I will in a day or two.

hahnjo · 2014-05-06 15:34:18

Sorry to post in such an old topic...

It was indeed a kernel bug. I submitted a patch in November and it was included in 3.11.10, 3.12.2 and 3.13 (https://bugzilla.kernel.org/show_bug.cgi?id=62491)
I think you should remove the section from the wiki

tazee · 2014-05-15 01:40:36

Hahnjo, thanks for your post as well as the kernel bug patch. I removed my systemd based workaround to test the new kernel and it works fine. I have removed the section from the wiki too.

Arch Linux

#1 2013-09-21 06:05:29

Alx driver issue after suspend

#2 2013-09-23 07:54:35

Re: Alx driver issue after suspend

#3 2013-09-23 14:04:06

Re: Alx driver issue after suspend

#4 2013-09-23 18:05:04

Re: Alx driver issue after suspend

#5 2013-09-24 14:14:44

Re: Alx driver issue after suspend

#6 2013-09-27 04:28:21

Re: Alx driver issue after suspend

#7 2013-09-27 13:55:10

Re: Alx driver issue after suspend

#8 2013-10-01 05:52:21

Re: Alx driver issue after suspend

#9 2013-10-09 20:21:22

Re: Alx driver issue after suspend

#10 2013-10-13 03:29:48

Re: Alx driver issue after suspend

#11 2013-10-22 04:26:53

Re: Alx driver issue after suspend

#12 2013-10-22 18:54:58

Re: Alx driver issue after suspend

#13 2013-10-22 22:22:02

Re: Alx driver issue after suspend

#14 2013-10-23 01:44:56

Re: Alx driver issue after suspend

#15 2013-10-28 19:05:12

Re: Alx driver issue after suspend

#16 2013-10-29 04:23:45

Re: Alx driver issue after suspend

#17 2013-11-01 05:48:34

Re: Alx driver issue after suspend

#18 2013-11-04 06:38:36

Re: Alx driver issue after suspend

#19 2013-11-04 15:42:25

Re: Alx driver issue after suspend

#20 2013-11-29 00:12:55

Re: Alx driver issue after suspend

#21 2014-05-06 15:34:18

Re: Alx driver issue after suspend

#22 2014-05-15 01:40:36

Re: Alx driver issue after suspend

Board footer