Subject: port-sgimips/32160: mec0 network adapter on SGI O2 10k not working
To: None <port-sgimips-maintainer@netbsd.org, gnats-admin@netbsd.org,>
From: None <herzog@phys.ethz.ch>
List: netbsd-bugs
Date: 11/24/2005 18:25:00
>Number: 32160
>Category: port-sgimips
>Synopsis: mec0 network adapter on SGI O2 10k not working
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: port-sgimips-maintainer
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Nov 24 18:25:00 +0000 2005
>Originator: Christian Herzog
>Release: NetBSD 2.1
>Organization:
Swiss Federal Institute of Technology
>Environment:
NetBSD 2.1 NetBSD 2.1 (GENERIC32_IP3x) #0: Tue Oct 25 00:48:05 UTC 2005 builds@b3.netbsd.org:/home/builds/ab/netbsd-2-1-RELEASE/sgimips/200510241747Z-obj/home/builds/ab/netbsd-2-1-RELEASE/src/sys/arch/sgimips/compile/GENERIC32_IP3x sgimips
>Description:
after being able to install NetBSD on our two O2s 10k (thanks to Izumi for the fix!) we now have problems with the network: Both machines constantly throw error messages like
mec0: mec_rxintr: status = 0x8000956ec2ad00a4
Nov 24 18:58:24 /netbsd: mec0: mec_rxintr: status = 0x8000956ec2ad00a4
mec0: mec_rxintr: status = 0x80002edad2ad006d
Nov 24 18:58:25 /netbsd: mec0: mec_rxintr: status = 0x80002edad2ad006d
mec0: mec_rxintr: status = 0x8000318732ad016c
Nov 24 18:58:32 /netbsd: mec0: mec_rxintr: status = 0x8000318732ad016c
mec0: mec_rxintr: status = 0x8000800f4bad006d
Nov 24 18:58:35 /netbsd: mec0: mec_rxintr: status = 0x8000800f4bad006d
mec0: mec_rxintr: status = 0x800047a37bad00a4
Nov 24 18:58:38 /netbsd: mec0: mec_rxintr: status = 0x800047a37bad00a4
mec0: mec_rxintr: status = 0x800088658bad016c
Nov 24 18:58:39 /netbsd: mec0: mec_rxintr: status = 0x800088658bad016c
as soon as network is configured. Needless to say that no data is flowing. Just once I was able to get one or two pings after a reboot before the errors started.
>How-To-Repeat:
install 2.1 on an O2 10k and configure network
>Fix: