Hello Tiny!

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

 T> Hi All,

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

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

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

 T> 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)