Solved Boot hangs on cherrytrail uefi system (installer + preinstalled stick), no dmesg written

O

olidietzel

Edit: Solved, I had to disable the uarts in /boot/device.hints

After disabling ACPI and APIC via /boot/loader.conf.local I saw the entropy harvester tried to harvest nonexistent uarts... :)

In /boot/device.hints I had to replace the UART hints there with "disabled" settings:
Code: 
hint.uart.0.disabled="1"
hint.uart.1.disabled="1"
/Edit

I need an idea on how to debug a hanging FreeBSD (10.3 and 11rc1) boot process.

I want to make a home server with firewall/router function out of a Cherry Trail z5-8300 mini PC (Beelink z83 / bt3, 64bit UEFI installed). Ubuntu 16.04 and OpenBSD 5.9 install fine into eMMC, but my preferred OS FreeBSD (more packages, same great PF) hangs on boot, always on or after a "ppc0: cannot reserve I/O port range" Message, see cam screenshot:

26532118nc.jpg


This happens if I boot a working install stick and if I boot from a tested working preinstalled Sandisk stick.

Nothing is written in /var/run/dmesg.boot.

How can I make the boot process more verbose in order to identify what exactly happens? Seems there is a -v option for the kernel boot stage, but where and how may I set it?

https://www.freebsd.org/doc/handbook/boot-introduction.html#boot-kernel

Edit: Managed to boot -v :)

But this didn't give me a lot more info. Seems the Kernel hangs while testing legacy hardware. Stuck at or after non existing com port.

Do I have to build a legacy free kernel or is there some other trick?

26532577uc.jpg
 
Last edited by a moderator:
Update:

There seems to exist a patch for Cherry Trail uarts

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207910

diff --git a/sys/dev/uart/uart_bus_pci.c b/sys/dev/uart/uart_bus_pci.c
index 4166222..13dd919 100644
--- a/sys/dev/uart/uart_bus_pci.c
+++ b/sys/dev/uart/uart_bus_pci.c
@@ -128,6 +128,10 @@ static const struct pci_id pci_ns8250_ids[] = {
{ 0x8086, 0x1c3d, 0xffff, 0, "Intel AMT - KT Controller", 0x10 },
{ 0x8086, 0x1d3d, 0xffff, 0, "Intel C600/X79 Series Chipset KT Controller", 0x10 },
{ 0x8086, 0x1e3d, 0xffff, 0, "Intel Panther Point KT Controller", 0x10 },
+{ 0x8086, 0x228a, 0xffff, 0, "Intel Cherryview SIO HSUART#1", 0x10,
+ 24 * DEFAULT_RCLK, 2 },
+{ 0x8086, 0x228c, 0xffff, 0, "Intel Cherryview SIO HSUART#2", 0x10,
+ 24 * DEFAULT_RCLK, 2 },
{ 0x8086, 0x2a07, 0xffff, 0, "Intel AMT - PM965/GM965 KT Controller", 0x10 },
{ 0x8086, 0x2a47, 0xffff, 0, "Mobile 4 Series Chipset KT Controller", 0x10 },
{ 0x8086, 0x2e17, 0xffff, 0, "4 Series Chipset Serial KT Controller", 0x10 },
 
Hi All,

Appreciate this thread happened long ago but it's one of the highest ranking results for this issue and so would like to potentially help others facing the same issue.

I was attempting to install pfsense on a machine affected by this issue earlier today. I wrote the installer to a key, booted it and was getting the same error message.

To allow the installation to continue, press space on boot to pause the boot menu, press 3 to go into the loader.

You can then override the UART settings and boot normally:

Code: 
set hint.uart.0.disabled="1"
set hint.uart.1.disabled="1"
boot

After installation you'll need to edit the /boot/device.hints file with the edits as mentioned by OP.

Quick edit: seems creating /boot/loader.conf.local and adding the two lines there is more suitable for pfsense, as device.hints gets replaced on a firmware update!

Many Thanks

Adrian
 

Attachments

  • IMG_20190107_142845.jpg
    IMG_20190107_142845.jpg
    245.1 KB · Views: 1,263
Last edited:
Just faced a very similar situation with the Atomic Pi board running FreeBSD 12.0.

In my case setting the uart to disabled didn't work. Instead I managed to boot by issuing
Code: 
unset hint.uart.1.at
boot

Once the install finished I just commented the relevant entry in /boot/device.hints

Hope this is as helpful to others as the previous posts on this issue were to me.
 
Arptastic said:
Hi All,

Appreciate this thread happened long ago but it's one of the highest ranking results for this issue and so would like to potentially help others facing the same issue.

I was attempting to install pfsense on a machine affected by this issue earlier today. I wrote the installer to a key, booted it and was getting the same error message.

To allow the installation to continue, press space on boot to pause the boot menu, press 3 to go into the loader.

You can then override the UART settings and boot normally:

Code: 
set hint.uart.0.disabled="1"
set hint.uart.1.disabled="1"
boot

After installation you'll need to edit the /boot/device.hints file with the edits as mentioned by OP.

Quick edit: seems creating /boot/loader.conf.local and adding the two lines there is more suitable for pfsense, as device.hints gets replaced on a firmware update!

Many Thanks

Adrian
Click to expand...
Hi Sir,
How to create or edit file name: /boot/loader.conf.local

what you pressed keyboard or code...Pls help me step by step because of not working at IT.
Tks,
 
David Muller said:
… How to create or edit file name: /boot/loader.conf.local …
Click to expand...

Welcome to The FreeBSD Forums.

In a nutshell:
  1. enter what's required at the so-called loader prompt (a one-off, allow the computer to boot/start from the installation disk)
  2. install FreeBSD
  3. attempt to boot the installation of FreeBSD
  4. again, enter what's required at the loader prompt (another one-off, for what was installed to actually boot/start for the first time)
  5. login as root
  6. at a normal command prompt, run the command below (to edit a file).
ee /boot/loader.conf

For an ordinary user, /boot/loader.conf (instead of /boot/loader.conf.local) is OK.

Working at the loader prompt can be mind-bending, even with guidance, so ask again if you get stuck.
 
Cath O'Deray can you help me?

I am trying to boot in an MSI NUC 5 and failing like never before.

I managed to install and change the configuration files, but when I reboot the OS never goes up. I did this after boot on the live image again:

Bash: 
mkdir /tmp/mounted
zpool import -f -R /tmp/mounted zroot
zfs mount zroot/ROOT/default
ee /tmp/mounted/boot/loader.conf and also device.hints (just in case)

# added to the files:
hint.uart.0.disabled="1"
hint.uart.1.disabled="1"

# Finished with:
zfs unmount zroot/ROOT/default
zpool export zroot
reboot
 
Notice that all these users have Z8350 CPU in common. This is a quirk for that processor.

You seem to have a 10th Gen Chip in the MSI NUC 5.

Are you sure about your diagnosis?
 
What about trying to disable UART via ACPI.
tomstorey

Post in thread 'Serial Console Problem'

Years later, I am toying with 13.3 on an old VPN appliance that has a Super Micro X10SBA-L. Same issue as reported, the serial console essentially freezes at the end of boot and you cannot login.

This motherboard has 4 UARTs on board. Following the instructions here, adding all 4 of them to debug.acpi.avoid in /boot/loader.conf.local resolved the serial console issues I was having.

I have in /boot/loader.conf:

Code: 
boot_multicons="YES"
console="comconsole,vidconsole"

and in /boot/loader.conf.local:

Code: 
debug.acpi.avoid="\_SB_.PCI0.LPCB.UAR1 \_SB_.PCI0.LPCB.UAR2 \_SB_.PCI0.LPCB.UAR3...
  • Like
  • Thanks

Note this part:
jmck said:
2) Identify the location of the device in the ACPI namespace:
$ sysctl -a | grep 'uart.0'
Click to expand...

Your ACPI device could have different name. Make sure you check yours.
 
You must log in or register to reply here.
Back
Top