Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#66585 - [linux] Asus AH001 universal dock rejected after LTS is the 5.x series

Attached to Project: Arch Linux
Opened by Hervé (herve) - Friday, 08 May 2020, 11:17 GMT
Last edited by freswa (frederik) - Friday, 08 May 2020, 15:06 GMT
Task Type Bug Report
Category Packages: Core
Status Assigned
Assigned To Tobias Powalowski (tpowa)
Jan Alexander Steffens (heftig)
Levente Polyak (anthraxx)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No



I've been bugged by this issue for months, but now I finally have time to report it.

This is most likely an upstream bug, but I found to report it, and they say "for posting bugs against the upstream Linux kernels (not distribution kernels)", and as I use the Arch package... That may explain why there are already many bugs open here. Sorry to add one more.

I've got a Asus AH001 USB-C universal dock, and when I plug it in, it works as expected, providing me the extra Ethernet port, HDMI output etc.

But one day the linux-lts package switched to the 5.x series, and the dock wasn't working anymore.

What I can see from my user point of view is the Ethernet icon popping up in the Gnome top bar for a couple of seconds and then disappearing. The monitor never reacts to some wake up event.
I'll attach the dmesg output anyway.

I downgraded the linux-lts package to 4.19.101-2, rebooted, and the dock works once again as expected. So I kept this package for months and ignored the updates to keep my workstation operational.

Now I take the time, I installed the latest regular linux 5.6.11.arch1-1 package to test once again, and generate the dmesg output attached below.
This is the only machine with a USB-C port I have to test that dock.

I did some research and found people I thought had the same issues:

But it's supposed to be fixed in 5.6.8-arch1-1. And I tested a fresh Fedora 32 live USB that's supposed to embed a kernel with that fix, and it made no difference (I just quickly checked the dmesg output and saw some "Null pointer reference" in red (recalling that one from memory).

I'm confident enough to use Arch Linux but I'm not that much an advanced user, let alone compiling my own kernel, so please bear with me.

Additional info:
* package version(s): 5.6.11.arch1-1
* config and/or log files etc. I attached 4 files but that's the same session:
- Fresh boot before plugging in the dock;
- just after I plugged in the dock;
- after waiting for a minute;
- after unplugging it.
* link to upstream bug report, if any: it seemed inappropriate to their rules

On a side note, the laptop itself is a Asus ZenBook, if that's important somehow.

Steps to reproduce: hard without the hardware I guess...
This task depends upon

Comment by Hervé (herve) - Saturday, 05 September 2020, 10:09 GMT
Still happening with kernel 5.8.6.arch1-1.

I attach the dmseg of that test session. The dock is plugged in at line 966, and everything seems detected fine. But starting from line 1050, every device on that dock disconnects one after the other.

Again, booting back on the kernel 4.19.101-2-lts restores the dock full functionality, I also attach the dmesg to compare.

Maybe I should report it upstream, but I'm afraid they'll send me back here.

More precisely, the laptop is an Asus ZenBook Flip S UX370UA