From owner-freebsd-bugs@FreeBSD.ORG Tue May 10 18:30:09 2011 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D190F106566B for ; Tue, 10 May 2011 18:30:09 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id AF6218FC18 for ; Tue, 10 May 2011 18:30:09 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p4AIU9Xc023707 for ; Tue, 10 May 2011 18:30:09 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p4AIU9GD023706; Tue, 10 May 2011 18:30:09 GMT (envelope-from gnats) Resent-Date: Tue, 10 May 2011 18:30:09 GMT Resent-Message-Id: <201105101830.p4AIU9GD023706@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Ratko Gospodnetic Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 00554106566B for ; Tue, 10 May 2011 18:28:59 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id E4B3D8FC16 for ; Tue, 10 May 2011 18:28:58 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.4/8.14.4) with ESMTP id p4AISv3e052728 for ; Tue, 10 May 2011 18:28:57 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.4/8.14.4/Submit) id p4AISvMD052727; Tue, 10 May 2011 18:28:57 GMT (envelope-from nobody) Message-Id: <201105101828.p4AISvMD052727@red.freebsd.org> Date: Tue, 10 May 2011 18:28:57 GMT From: Ratko Gospodnetic To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: conf/156935: Atheros AR8132 connectivity problem to Gigabit switch X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 May 2011 18:30:09 -0000 >Number: 156935 >Category: conf >Synopsis: Atheros AR8132 connectivity problem to Gigabit switch >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue May 10 18:30:09 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Ratko Gospodnetic >Release: 8.0 >Organization: ZI5 d.o.o. Zagreb Croatia >Environment: FreeBSD freenas.local 8.2-RELEASE-p1 FreeBSD 8.2-RELEASE-p1 #4: Sat Apr 30 10:39:46 PDT 2011 jpaetzel@servant.iXsystems.com:/usr/home/jpaetzel/freenas/obj.amd64/usr/home/jpaetzel/freenas/FreeBSD/src/sys/FREENAS.amd64 amd64 >Description: When FreeNAS PC Atheros AR8132 NIC is connected to Planet 24 port Gigabit Internet switch (10/100/1000), FreeNAS could not be pinged and FreeNAS cannot see other computers on the same network. pciconf -lv | grep -B3 network confirms that Atheros Network Card is recognized. When same FreeNAS computer is connected to 8 port 10/100 Internet switch which is further connected to above mentioned Planet Gigabit switch everything works fine. FreeNAS can be pinged from other computers and managed through GUI interface. When same PC is booted with Windows XP Pro and connected to Planet 24 port Gigabit Internet switch (10/100/1000) exactly like FreeNAS, everything works OK! PC could see other computers on LAN and could be pinged and accessed from other computers in the network. >How-To-Repeat: Always repeatable in the same environment. >Fix: Please see attached file: _ReadMe_02.03.txt Patch attached with submission follows: 2011-05-10 _ReadMe_02.03.txt ************************************************************************************ TEMPORARY MANUAL SOLUTION FOR ATHEROS AR8132 PROBLEM ON FreeNAS v8.0 ************************************************************************************ ------------------------------------------------------------------------------------ Problem with FreeNAS Atheros AR8132 NIC PC when connected to 10/100/1000 Mbps switch. PC and NIC are not recognised on LAN Reason for problem is that (probably) "media autoselect" feature in AR8132 driver is notworking according to specification and switch does not recognize NIC. With command mode change in NIC interface config from "media autoselect" to "media 100baseTX" NIC is recognized and computer can communicate on LAN. This is just temporary solution and it will not survive next boot! For permanent solution: * comands must be added to boot stream so update for NIC config is automatic or * FreeBSD/FreeNAS OS driver for Atheros AR8132 should be updated or after connection is established with shell commmands correction Windows GUI should be used and option field for NIC set to "media 100baseTX" and corrections will stay after next boot but not survive next installation :)) ------------------------------------------------------------------------------------ Atheros AR8132 Network interface card supports only 10/100 Mbps connections. Complete list of supported options could be isted with "ifconfig -m alc0" supported media: media autoselect mediaopt flowcontrol media autoselect media 100baseTX mediaopt full-duplex,flowcontrol media 100baseTX mediaopt full-duplex media 100baseTX media 10baseT/UTP mediaopt full-duplex,flowcontrol media 10baseT/UTP mediaopt full-duplex media 10baseT/UTP media noned with ifconfig -m alc0 ------------------------------------------------------------------------------------ 0. Boot FreeNAS v8.0 1. Connect PC with Atheros AR8132 NIC to Gigabit switch 2. LAN/switch connection is not active From Console Setup menu choose: 7) Shell 3. Check NIC status with command where "alc0" is device name ifconfig -m alc0 or for simplicity ifconfig -m Result of "ifconfig" command reports details about NIC status and configuration 4. Set NIC config atribute for media to 100baseTx, where "alc0" is device name ifconfig alc0 media 100baseTX 5. Put NIC down ifconfig alc0 down 6. Put NIC Up and NIC interface is reset automaticaly ifconfig alc0 up 7. Check status with: ifconfig -m alc0 8. LED indicators on 10/100/1000 switch should confirm that NIS is connected and working in 100baseTX mode 9. LAN connection is active 10. Activate any Internet Browser on Windows PC connected to same LAN 11. Activate FreeNAS GUI by entering computer name (eg. freenas) or IP address (eg 192.168.1.100) into address field 12. Enter admin logon data (eg admin/freenas) 13. Open from main menu item "Interfaces" 14. From "Interfaces" submenu choose "View All Interfaces" 15. Click on Edit button for Atheros driven device with conectivity problem 16. Type "media 100baseTX" (without ") into "Options" field and click on "OK" button 17. NIC will be reconfigured and setup remembered 18. This change will survive boot but not next FreeNAS reinstall :) ------------------------------------------------------------------------------------ List of commands that should be executed for temporary correction: ifconfig -m alc0 ifconfig alc0 media 100baseTX ifconfig alc0 down ifconfig alc0 up ifconfig -m alc0 ------------------------------------------------------------------------------------ >Release-Note: >Audit-Trail: >Unformatted: