Bug 14549

Summary: 3C509 broken in 3.3
Product: Base System Reporter: ryan <ryan>
Component: kernAssignee: Matthew N. Dodd <mdodd>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description ryan 1999-10-27 01:00:01 UTC
The 3C509 driver appears to be seriously broken in 3.3-RELEASE, I've
seen this on several different machines (different MB's,509 revs, etc),
all worked with 2.2.x and 3.1, but none worked with 3.3.  Unfortunately
its not critical enough for me to spend the time tracking down exactly
what the issue is (I just used different cards :) so all I can really
offer is anecdotal evidence

64 bytes from x.x.x.x: icmp_seq=0 ttl=253 time=23810.466 ms
64 bytes from x.x.x.x: icmp_seq=1 ttl=253 time=22805.705 ms
64 bytes from x.x.x.x: icmp_seq=2 ttl=253 time=21796.488 ms
64 bytes from x.x.x.x: icmp_seq=3 ttl=253 time=20787.113 ms

Fix: 

Sorry, haven't had time to track it down
How-To-Repeat: Install a 3C509 (ep0) card in a FreeBSD machine, ifconfig it, and
try to ping (or do anything else to) any machine connected via that
interface
Comment 1 Matthew N. Dodd freebsd_committer freebsd_triage 2000-07-18 07:49:16 UTC
Responsible Changed
From-To: freebsd-bugs->mdodd

'ep' seems to be my problem.
Comment 2 Mark Linimon freebsd_committer freebsd_triage 2007-04-28 10:29:06 UTC
State Changed
From-To: open->feedback

Is this still a problem with modern versions of FreeBSD?
Comment 3 Mark Linimon freebsd_committer freebsd_triage 2007-06-14 07:06:34 UTC
State Changed
From-To: feedback->closed

Feedback timeout (1 month).