NetBSD Problem Report #43018

From www@NetBSD.org  Fri Mar 19 18:23:44 2010
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
	by www.NetBSD.org (Postfix) with ESMTP id 373CF63B86C
	for <gnats-bugs@gnats.NetBSD.org>; Fri, 19 Mar 2010 18:23:44 +0000 (UTC)
Message-Id: <20100319182343.B620263B11D@www.NetBSD.org>
Date: Fri, 19 Mar 2010 18:23:43 +0000 (UTC)
From: bernhard@sdg.de
Reply-To: bernhard@sdg.de
To: gnats-bugs@NetBSD.org
Subject: ale0/atphy0 NIC driver failure on Asus EeePC 901
X-Send-Pr-Version: www-1.0

>Number:         43018
>Category:       kern
>Synopsis:       ale0/atphy0 NIC driver failure on Asus EeePC 901
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Mar 19 18:25:00 +0000 2010
>Last-Modified:  Sat Mar 26 01:17:50 +0000 2011
>Originator:     Bernhard Riedel
>Release:        5-stable
>Organization:
>Environment:
NetBSD atom 5.0_STABLE NetBSD 5.0_STABLE (GENERIC) #0: Sun Mar  7 21:22:12 CET 2010  root@monitor.crg.de:/sdata/test-5/obj/sys/arch/i386/compile/GENERIC i386

>Description:
http://netbsd.org/ports/i386/netbook.html says about the Asus EeePC 901:

Ethernet: supported in 4.1
Wireless: supported in 4.0 (with patch)

I tested with 5-stable-201002180000Z/i386 and HEAD-201003180000Z/i386,
 both interfaces seem pretty useless.
the Ethernet attaches to ale0: (address partially obscured by me)

ale0 at pci2 dev 0 function 0: Attansic/Atheros L1E Ethernet
ale0: AR8113 (L2E RevA), ioapic0 pin 17
ale0: Ethernet address 00:23:54:xx:xx:xx
atphy0 at ale0 phy 0: L1 10/100/1000 PHY, rev. 9
atphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

# ifconfig ale0
ale0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        address: 00:23:54:xx:xx:xx
        media: Ethernet autoselect (none loopback)
        status: no carrier

, but ifconfig inet ... up only results in a stream of PHY register access error messages until I ifconfig down again.

Testing this with -current even made the NIC disappear completely,
 not even BIOS could see it anymore. I had to remove the battery to
 fix that!

Wireless shows up as
vendor 0x1814 product 0x0781 (miscellaneous network) at pci4 dev 0 function 0 not configured

Didn't try the patchset for wireless, yet, plain old ethernet would be more useful.

>How-To-Repeat:
install NetBSD-5-stable or NetBSD-current (versions see above) on an Asus
EeePC 901 netbook, enable NIC in BIOS, connect NIC to switch, watch kernel messages, try to ifconfig up.
>Fix:
no fix... this belongs to >1 category (misc,kern,port-i386?) and class (doc-bug,sw-bug). I'm not sure if severity/priority are appropriate, either;)

>Release-Note:

>Audit-Trail:

Responsible-Changed-From-To: misc-bug-people->kern-bug-people
Responsible-Changed-By: dholland@NetBSD.org
Responsible-Changed-When: Tue, 23 Mar 2010 16:59:36 +0000
Responsible-Changed-Why:
Problems in machine-independent drivers are generally best filed under "kern".
Meanwhile, a problem that causes hardware to disappear to the 
BIOS seems like "critical/high" to me. Adjusted accordingly.


>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD: gnats_config.sh,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.