Subject: kern/21057: bge(4) hangs for a few seconds on "ifconfig -a"
To: None <gnats-bugs@gnats.netbsd.org>
From: Matthias Scheler <tron@colwyn.zhadum.de>
List: netbsd-bugs
Date: 04/07/2003 22:28:58
>Number: 21057
>Category: kern
>Synopsis: bge(4) hangs for a few seconds on "ifconfig -a"
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: kern-bug-people
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon Apr 07 13:30:00 PDT 2003
>Closed-Date:
>Last-Modified:
>Originator:
>Release: NetBSD 1.6Q (2003-04-07 sources, also NetBSD 1.6.1)
>Organization:
Matthias Scheler http://scheler.de/~matthias/
>Environment:
System: NetBSD lyssa.zhadum.de 1.6Q NetBSD 1.6Q (LYSSA) #0: Mon Apr 7 12:54:05 CEST 2003 tron@lyssa.zhadum.de:/src/sys/compile/LYSSA i386
Architecture: i386
Machine: i386
>Description:
I've two NetBSD-i386 systems (1.6.1 and 1.6Q) with Netgear GA302T cards
which are recognized by NetBSD like this:
bge0 at pci2 dev 9 function 0: Altima AC9100 Gigabit Ethernet
bge0: interrupting at apic 2 int 21 (irq 9)
bge0: ASIC BCM5701 B5, Ethernet address 00:09:5b:1c:28:56
brgphy0 at bge0 phy 1: BCM5701 1000BASE-T media interface, rev. 0
The card works fine but I experience short 1-2 seconds hangs from time to
time. On the NetBSD 1.6.1 I always get this kernel message in this case:
bge0: gigabit link up
The NetBSD 1.6Q system would probably print them, too, if I wouldn't have
disabled these message in revision 1.38 of "src/sys/dev/pci/if_bge.c".
The hang can be reproduced by using "ifconfig -a" on both systems. My
guess is that probing the PHY causes this problem.
>How-To-Repeat:
1.) Perform a remote login into a system using bge(4) via an interface which
uses that driver.
2.) Type "ifconfig -a".
>Fix:
None provided.
>Release-Note:
>Audit-Trail:
>Unformatted: