Comment 76 for bug 1173952

Hi,

I am affected by this bug.

My Computer is an Asus UX52VS running an all fresh Ubuntu 13.10 Install.

Running Kernel 3.11 (current 3.11.0-13), if a let the alx module loaded and go to suspend (closing my laptop)
When opening up, i get back the X11 authentication, i can log in then the system totally hangs

Ventirad begins to go in high load (so i guess because of an high CPU load) , sometimes i can access to the terminal (first console) and i can see the message repeated very fast:

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

The only solution is to hard power off the system to recover.

I can reproduce that everytime, if a unload the alx module before suspending everthing works fine...

I can see traces in kern.log:

Nov 18 21:01:59 guilhem-UX52VS kernel: [ 70.009079] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
Nov 18 21:01:59 guilhem-UX52VS kernel: [ 70.015965] iwlwifi 0000:03:00.0: Radio type=0x2-0x1-0x0
Nov 18 21:01:59 guilhem-UX52VS kernel: [ 70.105370] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Nov 18 21:01:59 guilhem-UX52VS kernel: [ 70.108113] alx 0000:04:00.0: irq 49 for MSI/MSI-X
Nov 18 21:01:59 guilhem-UX52VS kernel: [ 70.108348] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Nov 18 21:01:59 guilhem-UX52VS kernel: [ 70.109175] alx 0000:04:00.0: invalid PHY speed/duplex: 0xffff
Nov 18 21:01:59 guilhem-UX52VS kernel: [ 70.110913] alx 0000:04:00.0: invalid PHY speed/duplex: 0xffff
Nov 18 21:01:59 guilhem-UX52VS kernel: [ 70.112513] alx 0000:04:00.0: invalid PHY speed/duplex: 0xffff
Nov 18 21:01:59 guilhem-UX52VS kernel: [ 70.114340] alx 0000:04:00.0: invalid PHY speed/duplex: 0xffff
Nov 18 21:01:59 guilhem-UX52VS kernel: [ 70.115916] alx 0000:04:00.0: invalid PHY speed/duplex: 0xffff
Nov 18 21:01:59 guilhem-UX52VS kernel: [ 70.117484] alx 0000:04:00.0: invalid PHY speed/duplex: 0xffff

The system hanged when began the message about alx...

Is there any solution or workaround ?

I was expecting to test with kernel 3.12 if the same bug was existing, unfortunately under kernel 3.12 for me th situation is even worst and suspend simply does not work (alx module loaded or unloaded) all i get a black screen but this it an other story -:-)

Blacklisting the alx module "resolves" the issue as far as you don't need any wired connection, but this is a dirty workaround not a solution...

Thank you in advance for your help!