From owner-freebsd-sparc64@FreeBSD.ORG  Fri Aug 27 14:09:30 2004
Return-Path: <owner-freebsd-sparc64@FreeBSD.ORG>
Delivered-To: freebsd-sparc64@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 2029116A4CE; Fri, 27 Aug 2004 14:09:30 +0000 (GMT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 008AB43D6E; Fri, 27 Aug 2004 14:09:30 +0000 (GMT)
	(envelope-from arved@FreeBSD.org)
Received: from freefall.freebsd.org (arved@localhost [127.0.0.1])
	i7RE9TxS069981;	Fri, 27 Aug 2004 14:09:29 GMT
	(envelope-from arved@freefall.freebsd.org)
Received: (from arved@localhost)
	by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i7RE9Tic069977;
	Fri, 27 Aug 2004 14:09:29 GMT
	(envelope-from arved)
Date: Fri, 27 Aug 2004 14:09:29 GMT
From: Tilman Linneweh <arved@FreeBSD.org>
Message-Id: <200408271409.i7RE9Tic069977@freefall.freebsd.org>
To: arved@FreeBSD.org, freebsd-bugs@FreeBSD.org,
	freebsd-sparc64@FreeBSD.org
Subject: Re: kern/50943: kernel panic to initialize NIC (Intel Pro/100 or
	3COM905B
X-BeenThere: freebsd-sparc64@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting FreeBSD to the Sparc <freebsd-sparc64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
	<mailto:freebsd-sparc64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-sparc64>
List-Post: <mailto:freebsd-sparc64@freebsd.org>
List-Help: <mailto:freebsd-sparc64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
	<mailto:freebsd-sparc64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Aug 2004 14:09:30 -0000

Synopsis: kernel panic to initialize NIC (Intel Pro/100 or 3COM905B

Responsible-Changed-From-To: freebsd-bugs->freebsd-sparc64
Responsible-Changed-By: arved
Responsible-Changed-When: Fri Aug 27 14:07:10 GMT 2004
Responsible-Changed-Why: 
Maybe this is a sparc64 specific problem. Does the em(4) driver even work on
sparc64? Over to Mailinglist for feedback.

If you are sure this is not a sparc64 specific issue please reassign the PR 
to em(4) driver maintainer.

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