From nobody@FreeBSD.org  Sun Feb 18 07:39:01 2007
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id C90E316A400
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 18 Feb 2007 07:39:01 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [69.147.83.33])
	by mx1.freebsd.org (Postfix) with ESMTP id B9DA313C478
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 18 Feb 2007 07:39:01 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.13.1/8.13.1) with ESMTP id l1I7d1l9092317
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 18 Feb 2007 07:39:01 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.13.1/8.13.1/Submit) id l1I7d1xA092315;
	Sun, 18 Feb 2007 07:39:01 GMT
	(envelope-from nobody)
Message-Id: <200702180739.l1I7d1xA092315@www.freebsd.org>
Date: Sun, 18 Feb 2007 07:39:01 GMT
From: Sean Benoit<sean@digital-jungle.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: FreeBSD 6.2 Stable Kernel Update Prevents Dell PowerEdge 1750 (SMP) From Booting
X-Send-Pr-Version: www-3.0

>Number:         109267
>Category:       i386
>Synopsis:       FreeBSD 6.2 Stable Kernel Update Prevents Dell PowerEdge 1750 (SMP) From Booting
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-i386
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Feb 18 07:40:04 GMT 2007
>Closed-Date:    Sun Apr 22 10:13:21 GMT 2007
>Last-Modified:  Sun Apr 22 10:13:21 GMT 2007
>Originator:     Sean Benoit
>Release:        6.2 Stable
>Organization:
Digital Jungle Systems Inc.
>Environment:
FreeBSD mail-server.digital-jungle.com 6.2-STABLE FreeBSD 6.2-STABLE #0: Sat Feb 17 01:33:38 UTC 2007     tarzan@mail-server.digital-jungle.com:/usr/obj/usr/src/sys/MAIL-SERVER  i386
>Description:
As stated in the one line summary. We tried to update the FreeBSD kernel
from 6.2 Pre-Release to 6.2 Release (Stable) and our Dell PowerEdge 1750
multi-processor machines freeze on while detecting the second processor.

In order to get the machines to boot, the second processor must be disabled
in the BIOS.

We had EXACTLY the same problem a few months ago when we updated to 6.2
Pre-Release. It was reported here and you kindly provided a patch extremely
quickly. However, the same bug seems to have made its way into the current
release.
>How-To-Repeat:
Simply update to the 6.2 Release (Stable) kernel on a Dell PowerEdge 1750
with SMP enabled and watch it freeze on boot while detecting the second
processor.
>Fix:
Disable the second processor in the Dell BIOS.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: rwatson 
State-Changed-When: Fri Feb 23 15:20:27 UTC 2007 
State-Changed-Why:  
Is the problem described in this PR and your smp@ posting the same as the 
one described in PR 103697? 

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

Could you confirm whether you are using the ULE scheduler or not? 

SMP posting attached for reference to the PR: 

> Last fall, while updating a 6.1 Stable kernel to 6.2 Pre-Release, I noted 
> that the then new kernel caused all our previously functioning Dell 
> PowerEdge 1750s (dual processor) to freeze on boot at the point in the 
> boot process where the second processor was being detected. Disabling the 
> second processor in the BIOS served as a temporary workaround and enabled 
> the systems to boot successfully. 
>  
> At that time I submitted a PR via the website and a patch was issued 
> within a few hours. The patch resolved the problem. I didn't keep that 
> original correspondence because I assumed that all was well moving 
> forward. 
>  
> Last weekend I attempted to update the same systems for the first time 
> since last fall from the patched 6.2 Pre-Release kernel to the new 6.2 
> Stable kernel. I was alarmed to see that the EXACT same issue had 
> reappeared. The symptoms are exactly the same - as is the workaround 
> (disable the second processor in the BIOS). 
>  
> I have once again submitted a PR (109267) via the website (details at 
> http://www.freebsd.org/cgi/query-pr.cgi?pr=109267); however, I have been 
> advised that I should post the issue to this mailing list instead/prior. 
>  
> Not sure what to do from here... 


http://www.freebsd.org/cgi/query-pr.cgi?pr=109267 
State-Changed-From-To: feedback->closed 
State-Changed-By: linimon 
State-Changed-When: Sun Apr 22 10:12:16 UTC 2007 
State-Changed-Why:  
Feedback timeout (>1 month). 

Please note that if you are still seeing this problem, we can reopen 
this one. 

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