kern/166805: Winbond W83627DHG-P serial console hang

Ian yoitsmeremember at
Mon Apr 9 22:00:43 UTC 2012

>Number:         166805
>Category:       kern
>Synopsis:       Winbond W83627DHG-P serial console hang
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Apr 09 22:00:42 UTC 2012
>Originator:     Ian
>Release:        FreeBSD 9.0-RELEASE amd64
FreeBSD diamond 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Mon Apr  9 18:52:38 UTC 2012     root at diamond:/usr/obj/usr/src/sys/DIAMOND  amd64
When using a serial console (either "-Dh -S115200" or "-h -S115200") on an Intel D2500CC, the system will hang during boot, shortly after the root filesystem is loaded.  More specifically, it will hang (not panic) after printing "Setting hostuuid", and if hostid is disabled in rc.conf, it will hang after printing "Entropy harvesti" (without the "ng" at the end), coincidentally the exact same number of printed characters (16) as would have been printed when trying to set the host UUID.  This leads me to believe it's a buffering issue.

According to the "Technical Product Specification" from Intel, the board uses a Winbond W83627DHG-P for legacy, including serial, I/O.  In dmesg these appear as:

uart0: <16550 or compatible> port 0x3f8-0x3ff irq 3 flags 0x10 on acpi0
uart1: <16550 or compatible> port 0x2f8-0x2ff irq 4 on acpi0
uart2: <16550 or compatible> port 0x2e8-0x2ef irq 3 on acpi0
uart3: <16550 or compatible> port 0x2e0-0x2e7 irq 4 on acpi0

The problem also occurs with any combination of either amd64 or i386 and FreeBSD 8.2-RELEASE or 9.0-RELEASE.
Boot FreeBSD 9.0 or 8.2, either amd64 or i386, with a serial console configured (in my case, "-h -S115200" in /boot.config) on a D2500CC or, presumably, any board with a Winbond W83627DHG-P for serial I/O.

I also configured a serial tty for the same line at 115200 baud in /etc/ttys, though I don't believe it had any effect as I never got to a login prompt.
No known fix.

As there are also issues with the GPU on the new Intel Atom boards (see amd64/166639: [boot] Syscons issue Intel D2700) this leaves minimal options for administration of such boards running FreeBSD.  Aside from network administration (e.g. sshd), you may be stuck installing a PCI graphics card for installation or configuration if you are unable to do so via the network.


More information about the freebsd-bugs mailing list