Bug 62491
| Summary: | [PATCH]alx 0000:02:00.0: invalid PHY speed/duplex: 0xffff | ||
|---|---|---|---|
| Product: | Networking | Reporter: | vaniaz |
| Component: | Other | Assignee: | Stephen Hemminger (stephen) |
| Status: | RESOLVED CODE_FIX | ||
| Severity: | normal | CC: | alan, cj.wijtmans, cra, gilboad, hahnjo, martin, morian, shemming |
| Priority: | P1 | ||
| Hardware: | x86-64 | ||
| OS: | Linux | ||
| Kernel Version: | 3.12-rc3 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: | Patch to fix this bug | ||
|
Description
vaniaz
2013-10-03 17:21:27 UTC
This is the second report I see of this, but I have no idea. I can't even easily run my machine that has this driver with 3.12-rc, it's in production now. Maybe you can bisect? hardware: ASUS N56VZ, Qualcomm Atheros AR8161 Gigabit Ethernet (rev 10) software: ArchLinux with GNOME Have the same Bug on 3.12-rc6 and had it on 3.11.x before. On 3.10.x-lts everything is working correctly, even now... I can try to bisect it. On the main tree by Linus, correct? I tried it last week and yesterday and got weird results (a commit containing changes on nouveau, changes in the USB-core...) I have now found out that this problem occurs only when causing the suspend from GNOME with a shortcut on my keyboard or when closing the lid. However, it does NOT happen when using "sudo pm-suspend" in the terminal! I finally found and verified it:
It is commit bc2bebe8de8ed4ba6482c9cc370b0dd72ffe8cd2 ("alx: remove WoL support") by you...
Simply reverting it did the trick on 3.12.0-rc7. And my laptop isn't resuming at once. Everything working correctly like in 3.10.x...
Confirming this problem under Fedora 19 with KDE on Asus N56VZ, Qualcomm Atheros AR8161 Gigabit Ethernet (rev 10). After closing the lid and then resuming, a kworker thread pegs the CPU and the "invalid PHY speed/duplex: 0xffff" messages flood the kernel ring buffer. Also this problem is happening for me even if I just use "sudo pm-suspend", unlike reported in comment 3. One workaround is to never suspend, only shut down. Also confirming what is said in comment 4, reverting bc2bebe8de8ed4ba6482c9cc370b0dd72ffe8cd2 fixed the suspend/resume issue on a fresh 3.12.0 kernel. Created attachment 114381 [details]
Patch to fix this bug
I have finally found the necessary lines from the whole commit. The patch is attached
*** Bug 62501 has been marked as a duplicate of this bug. *** Patch has been applied to the net subsystem (In reply to Jonas Hahnfeld from comment #7) > Created attachment 114381 [details] > Patch to fix this bug > > I have finally found the necessary lines from the whole commit. The patch is > attached This patch fixes the problem for me on an Asus X202E. 3.12.2 and 3.11.10 have been released which both include this patch. So I think this bug can be marked as fixed! Probably i will be hated for posting this here but i am getting desperate. Is there any ALX driver maintainer left? Or someone that can propose the patch to be included. Basically multiple people want to have WOL functionality back in the ALX driver. Also some people claim the reason(bug) for taking the functionality out no longer applies to recent kernels. https://bugzilla.kernel.org/show_bug.cgi?id=61651 I would like to note that WOL functionality is the main reason i got this hardware. And it could be extremely useful to me for being away and working on distance. To get involved, please submit details of what is broken to Network Developers mailing list <netdev@vger.kernel.org> Bugzilla is only used as a proxy to forward bugs to the mailing list. It is not actively used by the kernel developers. |