Once in a while, I am getting this error on apu2 via the serial console when cold starting:
usbus1: EHCI version 1.0
usbus1 on ehci0
usbus1: 480Mbps High Speed USB v2.0
isab0: <PCI-ISA bridge> at device 20.3 on pci0
isa0: <ISA bus> on isab0
sdhci_pci0: <Generic SD HCI> mem 0xf7f27000-0xf7f270ff at device 20.7 on pci0
sdhci_pci0: 1 slot(s) allocated
orm0: <ISA Option ROM> at iomem 0xef000-0xeffff on isa0
ppc0: cannot reserve I/O port range
uart0: <16550 or compatible> at port 0x3f8 irq 4 flags 0x10 on isa0
uart0: console (115200,n,8,1)
uart1: <16550 or compatible> at port 0x2f8 irq 3 on isa0
hwpstate0: <Cool`n'Quiet 2.0> on cpu0
Timecounters tick every 1.000 msec
nvme cam probe device init
ugen1.1: <AMD EHCI root HUB> at usbus1
ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0: <SATA SSD SBFM01.1> ACS-4 ATA SATA 3.x device
uhub0: <AMD EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1
ada0: Serial Number 8EFA077A1AE701738346
ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 15272MB (31277232 512 byte sectors)
ugen0.1: <0x1022 XHCI root HUB> at usbus0
[ thread pid 15 tid 100066 ]
Stopped at vga_bitblt_one_text_pixels_block+0x135: movl (%rax,%r13,4),%ebx
db>
Not sure what to make of it, the only way is to unplug and replug the power. Then it will boot like nothing happened. Any ideas?
Apparently there is a race condition in the terminal driver (I cannot find the reference right now), but this happened on VMWare, too.
You should try out adding the following to
/boot/loader.conf.local:
Quotekern.vty=sc
This will change the termnial driver (see https://www.freebsd.org/cgi/man.cgi?query=vt&sektion=4):
Quote
kern.vty
Set this value to `vt' or `sc' to choose a specific system con-
sole, overriding the default. If not set, the default in the
GENERIC kernel is vt.
Thanks, it can also be set in the GUI via System > Administration > Console option > Console driver (uncheck for sc, check for vt)
Even easier then :}
Please mark the thread as [RESOLVED] if this fixed our issue!
I'll mark it as resolved for now, we'll see in the long run since the race condition can't be triggered on purpose :)