From eug@Makalu.ssu.gov.ua  Mon Apr 14 06:54:27 2003
Return-Path: <eug@Makalu.ssu.gov.ua>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 34E7537B401
	for <FreeBSD-gnats-submit@freebsd.org>; Mon, 14 Apr 2003 06:54:27 -0700 (PDT)
Received: from Makalu.ssu.gov.ua (Makalu.ssu.gov.ua [195.13.47.5])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3492143F3F
	for <FreeBSD-gnats-submit@freebsd.org>; Mon, 14 Apr 2003 06:54:25 -0700 (PDT)
	(envelope-from eug@Makalu.ssu.gov.ua)
Received: from Makalu.ssu.gov.ua (localhost [127.0.0.1])
	by Makalu.ssu.gov.ua (8.12.8/8.12.8) with ESMTP id h3EDsM33027010
	for <FreeBSD-gnats-submit@freebsd.org>; Mon, 14 Apr 2003 16:54:22 +0300
Received: (from eug@localhost)
	by Makalu.ssu.gov.ua (8.12.8/8.12.8/Submit) id h3EDsMQZ027009
	for FreeBSD-gnats-submit@freebsd.org; Mon, 14 Apr 2003 16:54:22 +0300
Message-Id: <200304141354.h3EDsMQZ027009@Makalu.ssu.gov.ua>
Date: Mon, 14 Apr 2003 16:54:22 +0300
From: Eugene <eug@ssu.gov.ua>
To: FreeBSD-gnats-submit@freebsd.org
Subject: kernel panic to initialize NIC (Intel Pro/100 or 3COM905B

>Number:         50943
>Category:       kern
>Synopsis:       kernel panic to initialize NIC (Intel Pro/100 or 3COM905B
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    jmg
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Apr 14 07:00:33 PDT 2003
>Closed-Date:    Wed Oct 13 23:43:19 GMT 2004
>Last-Modified:  Wed Oct 13 23:43:19 GMT 2004
>Originator:     Eugene Bogush <eug@ssu.gov.ua>
>Release:        FreeBSD 5.0-RELEASE sparc64
>Organization:
no
>Environment:
System: FreeBSD sun 5.0-RELEASE FreeBSD 5.0-RELEASE #7: Mon Apr 14 13:55:02 GMT 2003 root@sun:/usr/src/sys/sparc64/compile/mykernel sparc64

        machine: UltraSparc 5
        nic:     PCI 3COM905B, PCI INTEL PRO/100 Server Adapter
>Description:
        System fails to initialize NIC.
        Any attempt to configure the
        interface results in a kernel panic.


>How-To-Repeat:
        Boot, configure interface using 'ifconfig up'

>Fix:

>Release-Note:
>Audit-Trail:
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 
State-Changed-From-To: open->feedback 
State-Changed-By: jmg 
State-Changed-When: Mon Sep 27 16:43:01 GMT 2004 
State-Changed-Why:  
Does this continue to happen in 5.3-BETA6 or any of the recent beta's? 
Also, what driver(s) are failing?  is it the em or fxp for the Intel card? 
We need the kernel panic, along with a backtrace to continue to debug this. 

Thanks. 


Responsible-Changed-From-To: freebsd-sparc64->jmg 
Responsible-Changed-By: jmg 
Responsible-Changed-When: Mon Sep 27 16:43:01 GMT 2004 
Responsible-Changed-Why:  
Does this continue to happen in 5.3-BETA6 or any of the recent beta's? 
Also, what driver(s) are failing?  is it the em or fxp for the Intel card? 
We need the kernel panic, along with a backtrace to continue to debug this. 

Thanks. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=50943 
State-Changed-From-To: feedback->closed 
State-Changed-By: jmg 
State-Changed-When: Wed Oct 13 23:41:48 GMT 2004 
State-Changed-Why:  
I can use fxp perfectly fine on my AXe sparc clone: 
# uname -a 
FreeBSD silver.funkthat.com 5.3-BETA7 FreeBSD 5.3-BETA7 #2: Sun Oct 10 19:00:52 PDT 2004     jmg@silver.funkthat.com:/usr/home/jmg/RELENG_5/src/sys/sparc64/compile/silver  sparc64 
# ifconfig fxp0 
fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 
options=8<VLAN_MTU> 
inet 192.168.0.45 netmask 0xffffff00 broadcast 192.168.0.255 
ether 00:a0:c9:3c:5b:93 
media: Ethernet autoselect (100baseTX <full-duplex>) 
status: active 

probably has been fixed since.. 

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