Bug 211929 - FreeBSD 11-RC1 installer can't run on USB3 on GIGABYTE SYS-R150-T60 "unable to install"
Summary: FreeBSD 11-RC1 installer can't run on USB3 on GIGABYTE SYS-R150-T60 "unable t...
Status: Closed Overcome By Events
Alias: None
Product: Base System
Classification: Unclassified
Component: arm (show other bugs)
Version: 11.0-RELEASE
Hardware: arm64 Any
: --- Affects Some People
Assignee: Mark Linimon
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-17 09:42 UTC by Matthias M.
Modified: 2024-10-04 10:47 UTC (History)
4 users (show)

See Also:

Attachments
Boot with hint.ahci.0.msi=0 and hw.usb.xhci.use_polling=1 (17.27 KB, text/plain)
2016-08-17 10:52 UTC, Matthias M. 		no flags Details
Boot with hw.usb.xhci.use_polling=1 (20.76 KB, text/plain)
2016-08-17 10:53 UTC, Matthias M. 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Matthias M. 2016-08-17 09:42:59 UTC 
Hi,

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:

hw.usb.xhci.msi=1
kern.cam.boot_delay="1000"
kern.cam.scsi_delay="3000"
debug.acpi.disabled="hostres"

didn't helped :(

System message:

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



PS:
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 freebsd_triage 2016-08-17 09:56:44 UTC 
Hi,

Can you try to set:

hw.usb.xhci.use_polling=1

What are the USB errors / XHCI dmesg printed?

--HPS
Comment 2 Matthias M. 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 freebsd_triage 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?

--HPS
Comment 4 Hans Petter Selasky freebsd_committer freebsd_triage 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?

--HPS
Comment 5 Matthias M. 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 Matthias M. 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 Matthias M. 2016-08-17 10:53:18 UTC 
Created attachment 173773 [details]
Boot with hw.usb.xhci.use_polling=1
Comment 8 Matthias M. 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 freebsd_triage 2016-08-17 11:57:59 UTC 
Hi,

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.

--HPS
Comment 10 Matthias M. 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 
Hi,

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,
Dominik
Comment 12 Matthias M. 2016-08-24 13:35:11 UTC 
(In reply to Dominik Ermel from comment #11)

Hi,

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

I just tested again with FreeBSD 11-RELEASE and FreeBSD 12 20170316-r315413.
Still unable to boot.
Comment 14 Ed Maste freebsd_committer freebsd_triage 2017-11-14 18:45:27 UTC 
FYI, FreeBSD-CURRENT now runs on 2-socket ThunderX systems in Packet.net.
Comment 15 Ed Maste freebsd_committer freebsd_triage 2022-04-03 15:01:22 UTC 
Can anyone with the affected firmware report whether this is still an issue?
Comment 16 Noah Cyrus 2022-04-25 09:37:28 UTC 
MARKED AS SPAM
Comment 17 Mark Linimon freebsd_committer freebsd_triage 2024-10-04 10:47:27 UTC 
^Triage: with all the changes since FreeBSD 11, this PR is surely OBE.