amd64/88485: em(4) problem

[Danny Braniss]

Can someone please close this PR?
The problem is not the cable length, nor em(4), nor amd64 but IPMI!

when IPMI is enabled it will 'catch' packets to ports 0x26f & 0x298

sorry for the noise.

	danny
> 
> >Number:         88485
> >Category:       amd64
> >Synopsis:       em(4) problem
> >Confidential:   no
> >Severity:       serious
> >Priority:       medium
> >Responsible:    freebsd-amd64
> >State:          open
> >Quarter:        
> >Keywords:       
> >Date-Required:
> >Class:          sw-bug
> >Submitter-Id:   current-users
> >Arrival-Date:   Fri Nov 04 11:50:15 GMT 2005
> >Closed-Date:
> >Last-Modified:
> >Originator:     Danny Braniss
> >Release:        FreeBSD 6.0-STABLE amd64
> >Organization:
> >Environment:
> System: FreeBSD cs4 6.0-STABLE FreeBSD 6.0-STABLE #20: Thu Nov 3 13:06:27 IST 2005 danny at x-dev:/r+d/obj/x-dev/amd64/r+d/6.0/src/sys/HUJI amd64
> 
> 
> 	
> >Description:
> 	The motherboard is an Intel SE7320VP2, when booting diskless
> 	via PXE, it will porceed as far having to mount root via NFS,
> 	at which point, it gets stuck sending GETATTR packet but not seeing
> 	the answer from the server. Increasing the length of the ethernet
> 	cable (cat 5) overcomes the problem. This problem has been seen
> 	on three such motherboards.
> 	Booting an i32 kernel works fine.
> 
> >How-To-Repeat:
> 	
> >Fix:
> 	using a longer cat-5 cable
> >Release-Note:
> >Audit-Trail:
> >Unformatted:
> _______________________________________________
> freebsd-amd64 at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-amd64
> To unsubscribe, send any mail to "freebsd-amd64-unsubscribe at freebsd.org"
>