From nobody@FreeBSD.org  Wed Jan 19 04:07:54 2011
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 823A2106566C
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 19 Jan 2011 04:07:54 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from red.freebsd.org (unknown [IPv6:2001:4f8:fff6::22])
	by mx1.freebsd.org (Postfix) with ESMTP id 726B28FC08
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 19 Jan 2011 04:07:54 +0000 (UTC)
Received: from red.freebsd.org (localhost [127.0.0.1])
	by red.freebsd.org (8.14.4/8.14.4) with ESMTP id p0J47sDN009943
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 19 Jan 2011 04:07:54 GMT
	(envelope-from nobody@red.freebsd.org)
Received: (from nobody@localhost)
	by red.freebsd.org (8.14.4/8.14.4/Submit) id p0J47sLK009942;
	Wed, 19 Jan 2011 04:07:54 GMT
	(envelope-from nobody)
Message-Id: <201101190407.p0J47sLK009942@red.freebsd.org>
Date: Wed, 19 Jan 2011 04:07:54 GMT
From: Dario Perovich <dariop@webnx.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: Failure during boot w/ supermicro H8QGi
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         154132
>Category:       i386
>Synopsis:       [boot] Failure during boot w/ supermicro H8QGi
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    marcel
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Jan 19 04:10:09 UTC 2011
>Closed-Date:    Mon Apr 25 17:00:27 UTC 2011
>Last-Modified:  Mon Apr 25 17:00:27 UTC 2011
>Originator:     Dario Perovich
>Release:        7.2 AMD, 7.3 i386/AMD64, 8.0-8.2RC1 i386/AMD64, 9-Current/AMD64
>Organization:
WebNX.com
>Environment:
n/a unable to install
>Description:
Unable to install FreeBSD, locks during boot.

8.0+ locks on boot with last line: uart1: [FILTER]
7.2 AMD64 7.3+ locks with last line: si01: [FILTER]

Tried multiple different versions 7.2, 7.3, 7.4, 8.0, 8.1, 8.2, and 9.
All fail with the exception of 7.2 i386 which can get to sysinstall
screen.  No acpi / safe mode make no difference.

http://www.supermicro.com/Aplus/motherboard/Opteron6100/SR56x0/H8QGi-F.cfm

If anyone would like to work on this we can put up a test machine with
ip/kvm.  Feel free to contact me at 800-840-5996 x42.  Thank you.

>How-To-Repeat:
Boot ISO, locks after uart1/si01
>Fix:
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->freebsd-i386 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Wed Jan 19 06:03:23 UTC 2011 
Responsible-Changed-Why:  
hardware-related. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=154132 

From: Daniel Gerzo <danger@FreeBSD.org>
To: bug-followup@FreeBSD.org, dariop@webnx.com
Cc:  
Subject: Re: i386/154132
Date: Fri, 18 Feb 2011 14:30:49 +0100

 Hello,
 
 we had the same problem. The system boots with the kernel which doesn't 
 include device uart in its configuration file, thus we expect that the 
 uart driver has some problem...
 
 
 -- 
 S pozdravom / Best regards
    Daniel Gerzo, FreeBSD committer

From: Martin Matuska <mm@FreeBSD.org>
To: bug-followup@FreeBSD.org, dariop@webnx.com
Cc:  
Subject: Re: i386/154132: [boot] Failure during boot w/ supermicro H8QGi
Date: Sat, 19 Feb 2011 19:00:44 +0100

 We experience this very same problem on a SuperMicro 1042G-TF server
 (mainboard: H8QGi+-F).
 
 I can confirm that the uart(4) driver causes the boot problem.
 A kernel without this driver boots and runs without problems and if you
 issue "kldload uart", the system hangs.
 
 As the GENERIC kernel does include uart(4), you need a custom kernel.
Responsible-Changed-From-To: freebsd-i386->marcel 
Responsible-Changed-By: remko 
Responsible-Changed-When: Wed Mar 30 05:35:19 UTC 2011 
Responsible-Changed-Why:  
People report that this might be within UART, and I thought that 
you might be able to have a look at that? 

http://www.freebsd.org/cgi/query-pr.cgi?pr=154132 
State-Changed-From-To: open->closed 
State-Changed-By: marcel 
State-Changed-When: Mon Apr 25 16:52:48 UTC 2011 
State-Changed-Why:  
No response from originator. Since the hang happens with both sio(4) 
and uart(4), as per the description, the problem appears specific to 
that particular machine or that particular mainboard. Assuming it's 
the mainboard, then other people are likely to hit the same problem. 
Hopefully we can work them to resolve the issue. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=154132 
>Unformatted:
