From owner-freebsd-current@FreeBSD.ORG Wed Oct 27 19:01:17 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB90216A4CE for ; Wed, 27 Oct 2004 19:01:17 +0000 (GMT) Received: from error404.nls.net (error404.nls.net [216.144.36.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7015B43D46 for ; Wed, 27 Oct 2004 19:01:17 +0000 (GMT) (envelope-from ketrien@error404.nls.net) Received: from [192.168.0.100] (eiterra.achedra.org [192.168.0.100]) by error404.nls.net (8.12.10/8.12.10) with ESMTP id i9RJ1FqP035820; Wed, 27 Oct 2004 15:01:16 -0400 (EDT) (envelope-from ketrien@error404.nls.net) Message-ID: <417FF0BC.30609@error404.nls.net> Date: Wed, 27 Oct 2004 15:02:20 -0400 From: "Ketrien I. Saihr-Kesenchedra" User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Engberg , freebsd-current@freebsd.org References: <200410271733.i9RHX7l13702@d1o409.telia.com> In-Reply-To: <200410271733.i9RHX7l13702@d1o409.telia.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: AMD PCnet/PCI Fast Ethernet driver issues in 5.3RC1 / 5.3-STABLE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2004 19:01:17 -0000 Daniel Engberg wrote: >Hi, the dmesg output is the following. >pcn0: port 0xe400-0xe41f mem >0xe2001000-0xe200101f irq 11 at device 10.0 on pci0 >miibus0: on pcn0 >lxtphy0: on miibus0 >lxtphy0: 100baseFX, 100baseFX-FDX, 10baseT, 10baseT-FDX, 100baseTX, >100baseTX-FDX, audio >pcn0: Ethernet address: 00:60:b0:eb:c3:c6 >pcn0: if_start running deferred for Giant >pcn0: [GIANT-LOCKED] > I must have missed earlier posts in this thread. (Not a surprise, I usually only have time to skip over -current.) The problem you are describing here is nearly identical to pcm-as-module here, with a generic/unknown PHY. I haven't had time to properly debug, since the pcn on the system in question is a) onboard and b) the only working NIC with driver currently in the system. The symptoms I saw were specifically that if pcn was compiled as module and loaded, it seemed not to attach PHY properly. Can you try compiling pcn as a module, and seeing if the behavior is identical on load? Then try unloading and reloading the driver? -ksaihr