Bug 50943 - kernel panic to initialize NIC (Intel Pro/100 or 3COM905B
Summary: kernel panic to initialize NIC (Intel Pro/100 or 3COM905B
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 5.0-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: John-Mark Gurney
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-04-14 15:00 UTC by Eugene
Modified: 2004-10-14 00:43 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Eugene 2003-04-14 15:00:33 UTC 
        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'
Comment 1 Tilman Keskinoz freebsd_committer freebsd_triage 2004-08-27 15:07:10 UTC 
Responsible Changed
From-To: freebsd-bugs->freebsd-sparc64

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.
Comment 2 John-Mark Gurney freebsd_committer freebsd_triage 2004-09-27 17:43:01 UTC 
State Changed
From-To: open->feedback

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.
Comment 3 John-Mark Gurney freebsd_committer freebsd_triage 2004-09-27 17:43:01 UTC 
Responsible Changed
From-To: freebsd-sparc64->jmg

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.
Comment 4 John-Mark Gurney freebsd_committer freebsd_triage 2004-10-14 00:41:48 UTC 
State Changed
From-To: feedback->closed

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..