Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to boot HAOS in a Core Ultra 125H Mini PC / Beelink SEi14 #3560

Open
dequinho opened this issue Aug 25, 2024 · 0 comments
Open

Unable to boot HAOS in a Core Ultra 125H Mini PC / Beelink SEi14 #3560

dequinho opened this issue Aug 25, 2024 · 0 comments
Labels

Comments

@dequinho
Copy link

Describe the issue you are experiencing

I tried to install HAOS utilizing a Live Ubuntu USB stick and the haos_generic-x86-64-13.1 image starting from scratch. I also was running HAOS in an ancient Intel NUC NUC6CAYB with a Celeron J3455 processor and a SATA SSD.

When trying to boot, it does not go further than the following error messages:

xhci_hcd 0000:00:14.0: Error while assigning device slot ID: Command Aborted
xhci_hcd 0000:00:14.0: Max number of devices this xHCI host support is 64. 
usb usb1-port4: couldn't allocate usb_device
xhci_hcd 0000:00:14.0: Error while assigning device slot ID: Command Aborted
xhci_hcd 0000:00:14.0: Max number of devices this xHCI host support is 64. 
usb usb2-port2: couldn't allocate usb_device
xhci_hcd 0000:00:14.0: Error while assigning device slot ID: Command Aborted
xhci_hcd 0000:00:14.0: Max number of devices this xHCI host support is 64. 
usb usb1-port6: couldn't allocate usb_device
xhci_hcd 0000:00:14.0: Error while assigning device slot ID: Command Aborted
xhci_hcd 0000:00:14.0: Max number of devices this xHCI host support is 64. 
usb usb1-port7: couldn't allocate usb_device
xhci_hcd 0000:00:14.0: Error while assigning device slot ID: Command Aborted
xhci_hcd 0000:00:14.0: Max number of devices this xHCI host support is 64. 
usb usb1-port10: couldn't allocate usb_device
nvme nvme0: I/O 20 QID 0 timeout, completion polled
nvme nvme0: I/O 21 QID 0 timeout, completion polled
nvme nvme0: I/O 22 QID 0 timeout, completion polled
vnvme nvme0: allocated 64 MiB host memory buffer.
nvme nvme0: I/O 23 QID 0 timeout, completion polled
nvme nvme0: I/O 20 QID 0 timeout, completion polled
nvme nvme0: I/O 21 QID 0 timeout, completion polled
nvme nvme0: I/O 22 QID 0 timeout, completion polled
nvme nvme0: I/O 20 QID 0 timeout, completion polled
name nvme0: 1/0/0 defaul/read/poll queues
nvme nvme0: I/O 21 QID 0 timeout, completion polled
nvme nvme0: I/O 21 QID 0 timeout, completion polled
....

The boot up log keep returning these same errors over and over if restarted. I tried to physically remove the SATA SSD that I had in my old NUC, inserted in a USB 3 case and tried to boot with the HAOS that is up and running already, and it also freezes at the very same point during boot sequence, throwing the same errors.

This issue seems to be tied to the Linux Kernel version that HAOS runs. Some people with similar hardware was able to boot by disabling Intel VT-d, but Beelink BIOS for this mini-pc does now allow to turn this off.

The closest issue I could find was the link below - which did not provide much info other than possible Linux kernel incompatibilities with newer hardware.

https://forum.qubes-os.org/t/installer-does-not-boot-nvme-timeout-completion-polled/13639

What operating system image do you use?

generic-x86-64 (Generic UEFI capable x86-64 systems)

What version of Home Assistant Operating System is installed?

13.1

Did the problem occur after upgrading the Operating System?

No

Hardware details

  • Beelink SEi14 Intel Core Ultra 5 125H Mini PC
  • 1TB Crucial P3 Plus NVME SSD
  • USB Keyboard

Steps to reproduce the issue

  1. Install HAOS in a Core 5 Ultra based Mini PC / Beelink SEi14
  2. Try to boot from NVME SSD or with a NVME SSD present

...

Anything in the Supervisor logs that might be useful for us?

During boot up sequence, following errors appears: 

xhci_hcd 0000:00:14.0: Error while assigning device slot ID: Command Aborted
xhci_hcd 0000:00:14.0: Max number of devices this xHCI host support is 64. 
usb usb1-port4: couldn't allocate usb_device
xhci_hcd 0000:00:14.0: Error while assigning device slot ID: Command Aborted
xhci_hcd 0000:00:14.0: Max number of devices this xHCI host support is 64. 
usb usb2-port2: couldn't allocate usb_device
xhci_hcd 0000:00:14.0: Error while assigning device slot ID: Command Aborted
xhci_hcd 0000:00:14.0: Max number of devices this xHCI host support is 64. 
usb usb1-port6: couldn't allocate usb_device
xhci_hcd 0000:00:14.0: Error while assigning device slot ID: Command Aborted
xhci_hcd 0000:00:14.0: Max number of devices this xHCI host support is 64. 
usb usb1-port7: couldn't allocate usb_device
xhci_hcd 0000:00:14.0: Error while assigning device slot ID: Command Aborted
xhci_hcd 0000:00:14.0: Max number of devices this xHCI host support is 64. 
usb usb1-port10: couldn't allocate usb_device
nvme nvme0: I/O 20 QID 0 timeout, completion polled
nvme nvme0: I/O 21 QID 0 timeout, completion polled
nvme nvme0: I/O 22 QID 0 timeout, completion polled
vnvme nvme0: allocated 64 MiB host memory buffer.
nvme nvme0: I/O 23 QID 0 timeout, completion polled
nvme nvme0: I/O 20 QID 0 timeout, completion polled
nvme nvme0: I/O 21 QID 0 timeout, completion polled
nvme nvme0: I/O 22 QID 0 timeout, completion polled
nvme nvme0: I/O 20 QID 0 timeout, completion polled
name nvme0: 1/0/0 defaul/read/poll queues
nvme nvme0: I/O 21 QID 0 timeout, completion polled
nvme nvme0: I/O 21 QID 0 timeout, completion polled
....

Anything in the Host logs that might be useful for us?

Unable to access Host logs

System information

No response

Additional information

No response

@dequinho dequinho added the bug label Aug 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant