Bug#1006477: Still broken in latest bullseye backports kernel but not in vanilla kernel
I downloaded the vanilla 5.16.11 kernel from kernel.org, compiled it and installed it. This time the resulting kernel worked flawlessly (well, almost). The machine boots normally and the USB card is working great. Both the ethernet ports and USB ports in it are functioning well. The only issue I have found so far is that I am not able to mount ISO9660 partitions, but besides that everything is perfect. This filesystem issue is probably an unrelated issue... Anyway, I decided to check the Debian backports repository and noticed that the linux-image-amd64 is using debian kernel 5.16.0, which I think maps to vanilla kernel 5.16.12. So I proceeded to install that backports package. I did that because I would like to run a debian-supported kernel rather than a self-compiled kernel. Unfortunately, the USB Card problem came back when I installed the debian backports kernel. The xhci_hcd log stating that a "Host System Error" occurred showed up again in /var/log/messages, the ethernet port on the USB card no longer works and also the USB ports on the card do not work either. So, my conclusion is that there is something specific to the debian kernels that is breaking this USB ethernet card. For now, I am going to stick to the vanilla kernel I compiled myself, but it would be great if the debian maintainers did something about addressing this issue at some point (hopefully sooner rather than later!) so folks like me can go back to using debian-supported kernels. So far I have not seen any maintainer chime-in here though. I do not know if it is because I am not providing the correct information, if they have bigger fish to fry or something else... I still offer my help though to try things out to assist the maintainers at getting more information (or the right information!) or to test patches or whatever...
Bug#1006477: Any update?
Hi, Just checking to see if anyone has looked into this and if there's an update/progress. Alternatively, if there's anything you need me to provide, test or do please let me know. Thanks!
Re: Problem: USB Ethernet PCI-E card does not work with kernel 5.10.0-11-amd64
Yes, I also believe it's all caused by the xhci_hcd issue. I did open a proper kernel issue report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006477 You can see in that report that the card worked ok with the newest vanilla kernel. But I don't know what fixed it yet andI have not had time to do any furher investigation. FYI, I won't update this thread anymore, but if anyone is interested in contributing ideas, information, etc, please would you do it on the issue report itself? Thanks for all the help! On Tue, Mar 8, 2022, 4:59 AM Bjørn Mork wrote: > Flacusbigotis writes: > > > The kernel logs indicating issues in Bullseye include a warning of a > "host > > failure" by xhci_hcd, and several write/read errors by the ax88179 > ethernet > > driver/module for the card, as follows: > > > > Feb 22 17:22:53 server1 kernel: [1.380198] xhci_hcd :1c:00.0: > xHCI > > Host Controller > > Feb 22 17:22:53 server1 kernel: [1.380205] xhci_hcd :1c:00.0: new > > USB bus registered, assigned bus number 5 > > Feb 22 17:22:53 server1 kernel: [1.380209] xhci_hcd :1c:00.0: > Host > > supports USB 3.0 SuperSpeed > > Feb 22 17:22:53 server1 kernel: [1.380260] usb usb5: New USB device > > found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.10 > > Feb 22 17:22:53 server1 kernel: [1.380261] usb usb5: New USB device > > strings: Mfr=3, Product=2, SerialNumber=1 > > Feb 22 17:22:53 server1 kernel: [1.380263] usb usb5: Product: xHCI > Host > > Controller > > Feb 22 17:22:53 server1 kernel: [1.380264] usb usb5: Manufacturer: > > Linux 5.10.0-11-amd64 xhci-hcd > > Feb 22 17:22:53 server1 kernel: [1.380265] usb usb5: SerialNumber: > > :1c:00.0 > > Feb 22 17:22:53 server1 kernel: [1.380396] hub 5-0:1.0: USB hub found > > Feb 22 17:22:53 server1 kernel: [1.380411] hub 5-0:1.0: 4 ports > detected > > Feb 22 17:22:53 server1 kernel: [5.508457] ax88179_178a 5-1:1.0 eth0: > > register 'ax88179_178a' at usb-:1c:00.0-1, ASIX AX88179 USB 3.0 > Gigabit > > Ethernet, 00:11:22:33:44:55 > > Feb 22 17:23:25 server1 kernel: [ 39.576966] xhci_hcd :1c:00.0: > > WARNING: Host System Error > > Feb 22 17:26:00 server1 kernel: [ 194.596335] ax88179_178a 5-1:1.0 > > enx001122334455: Failed to read reg index 0x0002: -22 > > I am guessing that the random mac address is a symptom caused by a > failure to read the permanent mac from the USB ethernet > controller. Which again probably is caused by one or more of these read > errors. > > But I believe those are only symptoms, and that the real error is that > unspecified "Host System Error". > > I wonder is this could be related to some of the quirks that have been > added for this xhci controller since v4.19? There have been a few since > the VL805 is used in the RPi4. Some of these might very well be > misunderstood and RPI related only. There is also an odd code path in > drivers/usb/host/pci-quirks.c where we select a different path on RPi > than on other systems because "things are taken care of by the board's > co-processor". I find that very suspiscious. > > And I must admit that my interest in this bug is because I'm worried > that the quirk I recently pushed could have unexpected side effects... > I have no clue. > > but the most likely cause is some power managenment issue. Test > disabling ASPM e.g. by adding pcie_aspm=off to the kernel command line. > > Or disabling USB autosuspend, e.g by adding usbcore.autosuspend=-1 to the > kernel command line. > > I do NOT suggest that you run with those settings by default. Only > testing to try to narrow down the problem. > > It would also be intersting to know if removing the XHCI_LPM_SUPPORT > quirk would make a difference, since this was added to the VL805 between > v4.19 and v5.10 without anyone really knowing if it works.. But I can't > figure out how to disable a device specific quirk like that without > patching the kernel. Anyone? > > > > Bjørn >
Bug#1006477: Problem does not happen in kernel 5.16.11
I read at [1] (see at bottom) that there was a problem with xhci in kernel 5.10 (which was fixed in a later kernel than 5.10) which could cause these USB cards to not work. So, I compiled the latest vanilla kernel (5.16.11) from kernel.org and booted up Bullseye with it. The boot did not succeed 100% (some other things broke, such as lightdm), but it did bring up the networking correctly and gave me access to a shell. I was able to verify that the ethernet port on the USB card worked fine. Also, the "xhci_hcd :1c:00.0: WARNING: Host System Error" log was not present and neither were the ax88179_178a kernel failure logs. So, it looks like whatever kernel software changes fixed the xhci also address the ethernet port issue (or perhaps the entire card in general because now I realize even the USB ports on it were not working in kernel 5.10). However, I have no idea what the kernel software changes that fixed this are, and I have less of a clue as to how to figure that out. [1] = https://community.ipfire.org/t/update-158-to-161-problems-with-usb-ethernet-adpater/6854/5
Bug#1006477: linux-image-5.10.0-11-amd64: USB Ethernet port on Syba SD-PEX50100 PCI-E card does not work with kernel 5.10.0-11-amd64
Package: src:linux Version: 5.10.92-1 Severity: important X-Debbugs-Cc: flacusbigo...@gmail.com Dear Maintainer, * What led up to the situation? I just upgraded from Debian Buster to Debian Bullseye and after the upgrade, the ethernet port on the Syba SD-PEX50100 PCI-E card has become unusable. In Bullseye, with kernel 5.10.0-11-amd64, the ethernet port on the card starts getting random MAC addresses during bootup which causes issues with ISPs that use DHCP servers that lock-on to MAC addresses. I also think the ethernet port does not work in general in Bullseye but I am not sure how to prove that wider claim. * What exactly did you do (or not do) that was effective (or ineffective)? The ethernet port works just fine in Debian Buster with kernel 4.19.0-11-amd64. It never fails to obtain a lease from the ISP DHCP server and its real MAC address is always used because it never gets randomized. I have used a pair of Debian Live USB sticks to boot from (one containing Bullseye and another containing Buster) to prove that the card works on one and not the other. In these environments, the card is managed by NetworkManager.service. I have also tested it with a hard-drive installation of Bullseye where the card is managed via networking.service instead and the same issues occur as with the Bullseye Live image that uses NetworkManager.service. In Bullseye, the /var/log/messages file shows kernel logs that indicate that there are issues during boot up with the PCI-E card. Those logs do not occur at all in Debian Buster. This is why I think the issue is in the kernel. The kernel logs indicating issues in Bullseye include a warning of a "host system error" by xhci_hcd, and several write/read errors by the ax88179 ethernet kernel driver/module for the card, as follows: Feb 22 17:22:53 server1 kernel: [1.380198] xhci_hcd :1c:00.0: xHCI Host Controller Feb 22 17:22:53 server1 kernel: [1.380205] xhci_hcd :1c:00.0: new USB bus registered, assigned bus number 5 Feb 22 17:22:53 server1 kernel: [1.380209] xhci_hcd :1c:00.0: Host supports USB 3.0 SuperSpeed Feb 22 17:22:53 server1 kernel: [1.380260] usb usb5: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.10 Feb 22 17:22:53 server1 kernel: [1.380261] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Feb 22 17:22:53 server1 kernel: [1.380263] usb usb5: Product: xHCI Host Controller Feb 22 17:22:53 server1 kernel: [1.380264] usb usb5: Manufacturer: Linux 5.10.0-11-amd64 xhci-hcd Feb 22 17:22:53 server1 kernel: [1.380265] usb usb5: SerialNumber: :1c:00.0 Feb 22 17:22:53 server1 kernel: [1.380396] hub 5-0:1.0: USB hub found Feb 22 17:22:53 server1 kernel: [1.380411] hub 5-0:1.0: 4 ports detected Feb 22 17:22:53 server1 kernel: [5.508457] ax88179_178a 5-1:1.0 eth0: register 'ax88179_178a' at usb-:1c:00.0-1, ASIX AX88179 USB 3.0 Gigabit Ethernet, 00:11:22:33:44:55 Feb 22 17:23:25 server1 kernel: [ 39.576966] xhci_hcd :1c:00.0: WARNING: Host System Error Feb 22 17:26:00 server1 kernel: [ 194.596335] ax88179_178a 5-1:1.0 enx001122334455: Failed to read reg index 0x0002: -22 Feb 22 17:26:00 server1 kernel: [ 194.596338] ax88179_178a 5-1:1.0 enx001122334455: Failed to write reg index 0x0002: -22 Feb 22 17:26:11 server1 kernel: [ 205.378965] ax88179_178a 5-1:1.0 enx001122334455: Failed to write reg index 0x0002: -22 Feb 22 17:26:11 server1 kernel: [ 205.378969] ax88179_178a 5-1:1.0 enx001122334455: Failed to write reg index 0x0002: -22 Feb 22 17:26:11 server1 kernel: [ 205.585506] ax88179_178a 5-1:1.0 enx001122334455: Failed to write reg index 0x0001: -22 Feb 22 17:26:11 server1 kernel: [ 205.693515] ax88179_178a 5-1:1.0 enx001122334455: Failed to read reg index 0x0001: -22 Feb 22 17:26:11 server1 kernel: [ 205.693524] ax88179_178a 5-1:1.0 enx001122334455: Failed to read reg index 0x0006: -22 Feb 22 17:26:11 server1 kernel: [ 205.693527] ax88179_178a 5-1:1.0 enx001122334455: invalid MAC address, using random Feb 22 17:26:11 server1 kernel: [ 205.693532] ax88179_178a 5-1:1.0 enx001122334455: Failed to write reg index 0x0006: -22 Feb 22 17:26:11 server1 kernel: [ 205.693535] ax88179_178a 5-1:1.0 enx001122334455: Failed to write reg index 0x0005: -22 Feb 22 17:26:11 server1 kernel: [ 205.693538] ax88179_178a 5-1:1.0 enx001122334455: Failed to write reg index 0x0001: -22 Feb 22 17:26:11 server1 kernel: [ 205.693541] ax88179_178a 5-1:1.0 enx001122334455: Failed to write reg index 0x0001: -22 Feb 22 17:26:11 server1 kernel: [ 205.693544] ax88179_178a 5-1:1.0 enx001122334455: Failed to write reg index 0x0001: -22 Feb 22 17:26:11 server1 kernel: [ 205.693547] ax88179_178a 5-1:1.0 enx001122334455: Failed to write reg index 0x0001: -22 Feb 22 17:26:11 server1 kernel: [ 205.693550] ax88179_178a 5-1:1.0 enx001122334455: Fa
Re: Problem: USB Ethernet PCI-E card does not work with kernel 5.10.0-11-amd64
On Wed, Feb 23, 2022 at 10:45 AM Diederik de Haas wrote: > This and the message you posted do make it likely that it's a kernel issue. > So here's my recommendation: > 1) Try disabling the MAC randomization and see whether that improves > things. > 2) If not or it doesn't properly/fully resolve issues, use the reportbug > tool/ > program to file a bug against the linux-image-5.10.0-11-amd64. > > That will itself generate various info about your system, but if there's > info > that you posted to this list that isn't automatically included in the bug > report, then do add it manually (by copy-paste f.e.). > That way all the relevant information is present in that (one) bug report > and > other/outside people don't have to be aware that you also send a separate > msg. > > > Thanks Diederik for your guidance. I will do as you suggested.
Problem: USB Ethernet PCI-E card does not work with kernel 5.10.0-11-amd64
Issue: The ethernet port on the Syba SD-PEX50100 PCI-E card does not work properly in Debian Bullseye (kernel 5.10.0-11-amd64). In Bullseye, with kernel 5.10.0-11-amd64, the ethernet card starts randomizing the MAC address which causes issues with ISPs that DHCP servers that lock-on to MAC addresses. I also think the ethernet port does not work in general in Bullseye but I am not sure how to prove that bigger claim. The card works just fine in Debian Buster with kernel 4.19.0-11-amd64. It never fails to obtain a lease from the ISP DHCP server and its real MAC address is always used because it never gets randomized. I have used a pair of Debian Live USB sticks to boot from (one containing Bullseye and another containing Buster) to prove that the card works on one and not the other. In these environments, the card is managed by NetworkManager.service. I have also tested it with a hard-drive installation of Bullseye where the card is managed via networking.service instead and the same issues occur as with the Bullseye Live image that uses NetworkManager.service. In Bullseye, the /var/log/messages file shows kernel logs that indicate that there are issues during boot up with the PCI-E card. Those logs do not occur at all in Debian Buster. This is why I think the issue is in the kernel. The kernel logs indicating issues in Bullseye include a warning of a "host failure" by xhci_hcd, and several write/read errors by the ax88179 ethernet driver/module for the card, as follows: Feb 22 17:22:53 server1 kernel: [1.380198] xhci_hcd :1c:00.0: xHCI Host Controller Feb 22 17:22:53 server1 kernel: [1.380205] xhci_hcd :1c:00.0: new USB bus registered, assigned bus number 5 Feb 22 17:22:53 server1 kernel: [1.380209] xhci_hcd :1c:00.0: Host supports USB 3.0 SuperSpeed Feb 22 17:22:53 server1 kernel: [1.380260] usb usb5: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.10 Feb 22 17:22:53 server1 kernel: [1.380261] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Feb 22 17:22:53 server1 kernel: [1.380263] usb usb5: Product: xHCI Host Controller Feb 22 17:22:53 server1 kernel: [1.380264] usb usb5: Manufacturer: Linux 5.10.0-11-amd64 xhci-hcd Feb 22 17:22:53 server1 kernel: [1.380265] usb usb5: SerialNumber: :1c:00.0 Feb 22 17:22:53 server1 kernel: [1.380396] hub 5-0:1.0: USB hub found Feb 22 17:22:53 server1 kernel: [1.380411] hub 5-0:1.0: 4 ports detected Feb 22 17:22:53 server1 kernel: [5.508457] ax88179_178a 5-1:1.0 eth0: register 'ax88179_178a' at usb-:1c:00.0-1, ASIX AX88179 USB 3.0 Gigabit Ethernet, 00:11:22:33:44:55 Feb 22 17:23:25 server1 kernel: [ 39.576966] xhci_hcd :1c:00.0: WARNING: Host System Error Feb 22 17:26:00 server1 kernel: [ 194.596335] ax88179_178a 5-1:1.0 enx001122334455: Failed to read reg index 0x0002: -22 Feb 22 17:26:00 server1 kernel: [ 194.596338] ax88179_178a 5-1:1.0 enx001122334455: Failed to write reg index 0x0002: -22 Feb 22 17:26:11 server1 kernel: [ 205.378965] ax88179_178a 5-1:1.0 enx001122334455: Failed to write reg index 0x0002: -22 Feb 22 17:26:11 server1 kernel: [ 205.378969] ax88179_178a 5-1:1.0 enx001122334455: Failed to write reg index 0x0002: -22 Feb 22 17:26:11 server1 kernel: [ 205.585506] ax88179_178a 5-1:1.0 enx001122334455: Failed to write reg index 0x0001: -22 Feb 22 17:26:11 server1 kernel: [ 205.693515] ax88179_178a 5-1:1.0 enx001122334455: Failed to read reg index 0x0001: -22 Feb 22 17:26:11 server1 kernel: [ 205.693524] ax88179_178a 5-1:1.0 enx001122334455: Failed to read reg index 0x0006: -22 Feb 22 17:26:11 server1 kernel: [ 205.693527] ax88179_178a 5-1:1.0 enx001122334455: invalid MAC address, using random Feb 22 17:26:11 server1 kernel: [ 205.693532] ax88179_178a 5-1:1.0 enx001122334455: Failed to write reg index 0x0006: -22 Feb 22 17:26:11 server1 kernel: [ 205.693535] ax88179_178a 5-1:1.0 enx001122334455: Failed to write reg index 0x0005: -22 Feb 22 17:26:11 server1 kernel: [ 205.693538] ax88179_178a 5-1:1.0 enx001122334455: Failed to write reg index 0x0001: -22 Feb 22 17:26:11 server1 kernel: [ 205.693541] ax88179_178a 5-1:1.0 enx001122334455: Failed to write reg index 0x0001: -22 Feb 22 17:26:11 server1 kernel: [ 205.693544] ax88179_178a 5-1:1.0 enx001122334455: Failed to write reg index 0x0001: -22 Feb 22 17:26:11 server1 kernel: [ 205.693547] ax88179_178a 5-1:1.0 enx001122334455: Failed to write reg index 0x0001: -22 Feb 22 17:26:11 server1 kernel: [ 205.693550] ax88179_178a 5-1:1.0 enx001122334455: Failed to write reg index 0x0002: -22 Feb 22 17:26:11 server1 kernel: [ 205.693553] ax88179_178a 5-1:1.0 enx001122334455: Failed to write reg index 0x0001: -22 Feb 22 17:26:11 server1 kernel: [ 205.693555] ax88179_178a 5-1:1.0 enx001122334455: Failed to write reg index 0x0002: -22 Feb 22 17:26:11 server1 kernel: [ 205.693561] ax88179_178a 5-1:1.0 enx001122334455: Failed to read reg index 0x0001: -22 Feb 22 17:26:11 server1 kernel: [ 20
