From nobody@FreeBSD.org  Sat Mar 27 23:05:25 2004
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id A1CA116A4CE
	for <freebsd-gnats-submit@FreeBSD.org>; Sat, 27 Mar 2004 23:05:25 -0800 (PST)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9B85A43D1D
	for <freebsd-gnats-submit@FreeBSD.org>; Sat, 27 Mar 2004 23:05:25 -0800 (PST)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.12.10/8.12.10) with ESMTP id i2S75P72084413
	for <freebsd-gnats-submit@FreeBSD.org>; Sat, 27 Mar 2004 23:05:25 -0800 (PST)
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.12.10/8.12.10/Submit) id i2S75P7L084412;
	Sat, 27 Mar 2004 23:05:25 -0800 (PST)
	(envelope-from nobody)
Message-Id: <200403280705.i2S75P7L084412@www.freebsd.org>
Date: Sat, 27 Mar 2004 23:05:25 -0800 (PST)
From: Jeff Stohl <spssmt@hotmail.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: Multiple em devices force system lockup (em0 and em1)
X-Send-Pr-Version: www-2.3

>Number:         64831
>Category:       kern
>Synopsis:       [em] [hang] Multiple em devices force system lockup (em0 and em1)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    tackerman
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Mar 27 23:10:21 PST 2004
>Closed-Date:    Mon Oct 24 04:53:16 GMT 2005
>Last-Modified:  Mon Oct 24 04:53:16 GMT 2005
>Originator:     Jeff Stohl
>Release:        5.2.1 CVS Current
>Organization:
Individual
>Environment:
FreeBSD demo.xn.com 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Sat Mar 27 22:34:27 PST 2004     root@demo.xn.com:/usr/src/sys/i386/compile/xn  i386
>Description:
Utilizing the MSI P1-102A2M 1u server with two integrated Gigabit ports (1 x Intel 82541 and 1 x Intel 82547) only allows one port to be in use at a time. If both ports are utilized the system will hangup and force a rise in CPU percent. The system becomes almost instantly unavailable over the network.

Utilizing either em0 or em1 individually works without error.

root      21  0.0  0.0     0   12  ??  WL   10:48PM   0:00.00  (irq11: em0)
root      33  0.0  0.0     0   12  ??  WL   10:48PM   0:00.07  (irq23: em1)




>How-To-Repeat:
Cable both network ports and bring both interfaces to up status.
>Fix:
None known
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->tackerman 
Responsible-Changed-By: dwmalone 
Responsible-Changed-When: Sun May 30 09:27:59 PDT 2004 
Responsible-Changed-Why:  
This sounds like it may be an interrupt routing problem, but it could 
be em related either. Tony may have some idea. 

David. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=64831 
State-Changed-From-To: open->feedback 
State-Changed-By: tackerman 
State-Changed-When: Thu Sep 23 16:55:38 GMT 2004 
State-Changed-Why:  
I have tried to reproduce this issue on a Dell system which has both 82541 and 82547 devices 
and it works fine.  I'm using 5.2.1  
Are you still experiencing this problem?  If so, I'd suggest disabling ACPI and retesting. 
ACPI may be causing some interrupt sharing issues. 


http://www.freebsd.org/cgi/query-pr.cgi?pr=64831 
State-Changed-From-To: feedback->closed 
State-Changed-By: linimon 
State-Changed-When: Mon Oct 24 04:52:54 GMT 2005 
State-Changed-Why:  
Feedback timeout (1 year). 

http://www.freebsd.org/cgi/query-pr.cgi?pr=64831 
>Unformatted:
I'm tracking down a similar system.  I have found one but it will take a day or two to 
get it together.  When I have a system I'll repro the issue. 
