Bug 211929

Summary: FreeBSD 11-RC1 installer can't run on USB3 on GIGABYTE SYS-R150-T60 "unable to install"
Product: Base System Reporter: M. Macha <freebsd-bugzilla.mmacha>
Component: armAssignee: freebsd-arm (Nobody) <freebsd-arm>
Status: Open ---    
Severity: Affects Some People CC: der, emaste, hselasky
Priority: ---    
Version: 11.0-RELEASE   
Hardware: arm64   
OS: Any   
Description Flags
Boot with hint.ahci.0.msi=0 and hw.usb.xhci.use_polling=1
Boot with hw.usb.xhci.use_polling=1 none

Description M. Macha 2016-08-17 09:42:59 UTC

we're unable to install FreeBSD-11.0-RC1 on a "GIGABYTE SYS-R150-T60" system.
The installer is unable to find a device (memstick) while boot up.

Sadly the system has only 3 USB 3.0 ports and even changing:


didn't helped :(

System message:

Root mount waiting for: usbus0 usbus1 usbus2  
Mounting from ufs:/dev/ufs/FreeBSD_Install failed with error 19.

I don't know if this is related: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204378
Comment 1 Hans Petter Selasky freebsd_committer 2016-08-17 09:56:44 UTC

Can you try to set:


What are the USB errors / XHCI dmesg printed?

Comment 2 M. Macha 2016-08-17 10:05:08 UTC
(In reply to Hans Petter Selasky from comment #1)

Just hw.usb.xhci.use_polling=1 or in addition to my previously used parameters?
Comment 3 Hans Petter Selasky freebsd_committer 2016-08-17 10:07:21 UTC
Just "hw.usb.xhci.use_polling=1" alone.

BTW: Is your memory stick USB 3.0 or USB 2.0?

Comment 4 Hans Petter Selasky freebsd_committer 2016-08-17 10:14:24 UTC
Is it possible to write down some of the USB related FreeBSD "dmesg". Where exactly does the boot process stop?

Comment 5 M. Macha 2016-08-17 10:30:05 UTC
(In reply to Hans Petter Selasky from comment #4)

sure the system installer runs on serial console. So I can give you the full output.

By the way the system also needs hint.ahci.0.msi=0 for booting "up"
But i will send you logs with both settings.

I will provide the output in about 5 minutes.
Comment 6 M. Macha 2016-08-17 10:52:39 UTC
Created attachment 173772 [details]
Boot with hint.ahci.0.msi=0 and hw.usb.xhci.use_polling=1
Comment 7 M. Macha 2016-08-17 10:53:18 UTC
Created attachment 173773 [details]
Boot with hw.usb.xhci.use_polling=1
Comment 8 M. Macha 2016-08-17 10:55:22 UTC
I provided two logs, one with additionalhint.ahci.0.msi=0 and one without.

PS: the device is usb 3.0 but usb 2.0 doesn't not work, too.
Comment 9 Hans Petter Selasky freebsd_committer 2016-08-17 11:57:59 UTC

I've forwarded this PR to someone which are working on a similar setup. Maybe it is not directly USB related. It might also be you'll need a 12-current kernel to be able to boot because arm64 is heavily under development.

Comment 10 M. Macha 2016-08-17 12:40:18 UTC
(In reply to Hans Petter Selasky from comment #9)

Ok, thanks. I just tested the latest 12-CURRENT installer which fails the same way.

Kind regards
Comment 11 Dominik Ermel 2016-08-24 12:12:28 UTC

This is dual socket so there are probably two ITSs (one ITS per socket.) FreeBSD for ARM64 supports only one ITS. If your USB port is connected to the second ITS the system will not be receiving interrupts from xhci.

Best regards,
Comment 12 M. Macha 2016-08-24 13:35:11 UTC
(In reply to Dominik Ermel from comment #11)


so may gigabyte connected all USB ports on the second ITS :/
Comment 13 M. Macha 2017-04-12 14:50:34 UTC

I just tested again with FreeBSD 11-RELEASE and FreeBSD 12 20170316-r315413.
Still unable to boot.
Comment 14 Ed Maste freebsd_committer 2017-11-14 18:45:27 UTC
FYI, FreeBSD-CURRENT now runs on 2-socket ThunderX systems in Packet.net.