Hi All,

Tried around 6 distro's and while Windows 10, and FreeBSD run great
on my desktop when attempting to boot any linux distro (live or just a
console ISO) I get the following:

xhci_hcd 0000:02:00.0: AMD-Vi: Event Logged [IO_PAGE_FAULT domain
0x000f address=0xbec10880 flags=0x0000]

Repeated 100 or so times, then I get
xhci_hcd 0000:02:00.0: can;t setup: -110
xhci_hcd 0000:02:00.0: init 0000:02:00.0 fail, -110

Anyone have any ideas? Anything at all?

Shawn

... What is a "free gift"? Aren't all gifts free?


--- Grumble
* Origin: Dirty Ole' Town (618:618/12)

Hello Tiny!

** On Tuesday 17.12.24 - 19:07, Tiny wrote to All:

Hi All,

Tried around 6 distro's and while Windows 10, and FreeBSD run great
on my desktop when attempting to boot any linux distro (live or just a console ISO) I get the following:

xhci_hcd 0000:02:00.0: AMD-Vi: Event Logged [IO_PAGE_FAULT domain
0x000f address=0xbec10880 flags=0x0000]

Repeated 100 or so times, then I get
xhci_hcd 0000:02:00.0: can;t setup: -110
xhci_hcd 0000:02:00.0: init 0000:02:00.0 fail, -110

Anyone have any ideas? Anything at all?

This is what Chatgpt thinks:

The error you're encountering is related to the xhci_hcd (eXtensible Host Controller Interface for USB) driver, which manages USB 3.0 devices. Here's a breakdown of the error:
Error Analysis

AMD-Vi: Event Logged [IO_PAGE_FAULT domain...]
This indicates an I/O page fault reported by AMD's IOMMU (Input-Output Memory Management Unit), which is used for device virtualization and DMA (Direct Memory Access) remapping.
The IOMMU detected that the xhci_hcd driver tried to access an invalid or unmapped memory address (address=0xbec10880).
Possible causes:
A USB device is misbehaving or incompatible.
The xHCI controller firmware/driver is buggy.
A kernel or hardware configuration issue, particularly involving IOMMU or USB.

Repeated 100 times
This repetition suggests the controller is retrying initialization and failing repeatedly, likely due to a persistent memory mapping or hardware issue.

xhci_hcd 0000:02:00.0: can't setup: -110
Error code -110 means timeout, indicating the xHCI driver could not properly initialize the USB controller.

xhci_hcd 0000:02:00.0: init 0000:02:00.0 fail, -110
The initialization of the USB controller failed entirely, and it is disabled.

Potential Causes

IOMMU Configuration Issue:
The IOMMU may not be configured correctly, leading to address translation errors.

Driver or Firmware Bug:
The xHCI driver or the USB controller's firmware may contain a bug causing the failure.

Hardware Problem:
A faulty USB device or controller could trigger these issues.

Kernel or BIOS Settings:
Incompatible or misconfigured BIOS/UEFI settings (e.g., IOMMU or USB) can cause such errors.
Kernel parameters like amd_iommu or iommu may need adjustment.

Troubleshooting Steps
1. Update BIOS/UEFI and Kernel

Ensure your system firmware and kernel are up to date to get the latest fixes for IOMMU and USB.

2. Check USB Devices

Disconnect all USB devices and see if the error persists. If the issue disappears, reconnect devices one by one to identify the culprit.

3. Adjust Kernel Parameters

Add kernel boot parameters to modify IOMMU behavior:
Disable IOMMU: amd_iommu=off iommu=soft
Alternative: iommu=pt (pass-through mode)
Edit the boot loader configuration (e.g., GRUB):
Open /etc/default/grub.
Modify GRUB_CMDLINE_LINUX_DEFAULT to include the parameters.
Run sudo update-grub and reboot.

4. Check PCI Device State

Verify the state of the USB controller:

lspci -vv -s 02:00.0

Check for errors or unusual configurations.

5. Blacklisting or Rebinding Driver

Temporarily blacklist the xhci_hcd driver to test:

echo "blacklist xhci_hcd" | sudo tee /etc/modprobe.d/blacklist-xhci.conf
sudo update-initramfs -u
sudo reboot

Alternatively, unload and reload the driver manually:

sudo modprobe -r xhci_hcd
sudo modprobe xhci_hcd

6. Test with a Different Kernel

Boot into an older or newer kernel version to determine if the issue is specific to your current kernel.

7. Check for Hardware Issues

Test the USB controller card or motherboard on another system, if possible, to rule out hardware failure.
--
../|ug

--- OpenXP 5.0.58
* Origin: (} Pointy McPointface (618:250/1.9)

xhci_hcd 0000:02:00.0: AMD-Vi: Event Logged [IO_PAGE_FAULT domain
0x000f address=0xbec10880 flags=0x0000]

Repeated 100 or so times, then I get
xhci_hcd 0000:02:00.0: can;t setup: -110
xhci_hcd 0000:02:00.0: init 0000:02:00.0 fail, -110

Bad stick of RAM?

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (618:500/24)

Bad stick of RAM?

Not unless the RAM is controlled by the USB 3.0 hardware...

-- Sean




--- MBSE BBS v1.1.0 (Linux-x86_64)
* Origin: Outpost BBS * Johnson City, TN (618:618/1)

Sean Dennis wrote in a message to T.J. Mcmillen:

Bad stick of RAM?

Not unless the RAM is controlled by the USB 3.0 hardware...

So frustrating. The USB works just fine under windows and freebsd. Really wonder what it is about the linux kernel drivers that won't let it boot. Even disabled USB 3.0 controller on the motherboard and sure I didn't have a keyboard but also got the exact same error.

Just strange.

Shawn

... Programmers need more input/output!
--- timEd 1.10.y2k+
* Origin: Dirty ole' Town (618:618/12)

Re: Installing any linux distro
By: Shawn Highfield to Sean Dennis on Wed Dec 18 2024 06:55 pm

Howdy,

So frustrating. The USB works just fine under windows and freebsd. Really wonder what it is about the linux kernel drivers that won't let it boot. Even disabled USB 3.0 controller on the motherboard and sure I didn't have a keyboard but also got the exact same error.

Have you booted passing "usbcore.nousb" on the kernel command line?

If you have a USB keyboard, then you probably wont be able to use it, but at least it'll confirm its the USB subsystem.

You might be able to get in another way (network?) and blacklist the USB device that is causing the problem...


...oEoN
--- SBBSecho 3.20-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (618:510/2)

Hi Deon,
On <Fri, 19 Dec 24>, you wrote me:

Have you booted passing "usbcore.nousb" on the kernel command line?

No, but I did disable the USB support in the bios and it booted so I
assume that's the same thing? I will try your suggestion though just
to know 100% what the issue is.

If you have a USB keyboard, then you probably wont be able to use it,
but at least it'll confirm its the USB subsystem.

Very true. At this point I just want to know. :) I will also try to
find out if there is an upgrade to the bios it's an older computer but
it was a pretty top end motherboard at one point.

You might be able to get in another way (network?) and blacklist the
USB device that is causing the problem...

I'm going to burn the ISO to a DVD if I can find a blank one... THough
I have tried 4 different usb keys.

Shawn

... I haven't lost my mind; it's backed up on tape somewhere!


--- Grumble
* Origin: Dirty Ole' Town (618:618/12)

Tiny wrote to Deon George <=-

No, but I did disable the USB support in the bios and it booted so I assume that's the same thing? I will try your suggestion though just
to know 100% what the issue is.

Being an older computer, does it have an Intel CPU?

-- Sean

... Humans worshipped cats 2000 years ago and the cats never forgot.
--- MultiMail/Linux
* Origin: Outpost BBS * Johnson City, TN (618:618/1)

Hi digimaus,
On <Fri, 19 Dec 24>, you wrote me:

Being an older computer, does it have an Intel CPU?

No it's a AMD FX something or other I think.

I just wish I knew why Windows 10, and FreeBSD can deal with the hardware perfectly. I'm going to install FreeBSD again later today... my only issue with it is getting GD Samba to work as I do use drive shares.

I had NFS working yesterday with one directory so I have a solution, but it's not the solution I want. As well the sound drivers are a nightmare compared to a linux distro.

Shawn

... Diplomacy is the art of saying Nice doggie! till you can find a rock.


--- Grumble
* Origin: From the Dirty Shwa (618:618/12)