From owner-freebsd-current@FreeBSD.ORG Thu Oct 28 16:44:42 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 20B4716A4CE for ; Thu, 28 Oct 2004 16:44:42 +0000 (GMT) Received: from av3-2-sn4.m-sp.skanova.net (av3-2-sn4.m-sp.skanova.net [81.228.10.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77C6943D2F for ; Thu, 28 Oct 2004 16:44:41 +0000 (GMT) (envelope-from diizzy@telia.com) Received: by av3-2-sn4.m-sp.skanova.net (Postfix, from userid 502) id D576937E8A; Thu, 28 Oct 2004 18:44:40 +0200 (CEST) Received: from smtp2-2-sn4.m-sp.skanova.net (smtp2-2-sn4.m-sp.skanova.net [81.228.10.182]) by av3-2-sn4.m-sp.skanova.net (Postfix) with ESMTP id C73E637E63; Thu, 28 Oct 2004 18:44:40 +0200 (CEST) Received: from d1o402.telia.com (d1o402.telia.com [195.67.227.92]) by smtp2-2-sn4.m-sp.skanova.net (Postfix) with ESMTP id 8EE9037E5C; Thu, 28 Oct 2004 18:44:40 +0200 (CEST) Received: by d1o402.telia.com (8.11.1/8.10.1) id i9SGiex00380; Thu, 28 Oct 2004 18:44:40 +0200 (CEST) Date: Thu, 28 Oct 2004 18:44:40 +0200 (CEST) Message-Id: <200410281644.i9SGiex00380@d1o402.telia.com> X-Authentication-Warning: d1o402.telia.com: www set sender to diizzy@telia.com using -f From: "DiiZzY" To: "Ketrien I. Saihr-Kesenchedra" X-Mailer: SF Webmail X-SF-webmail-clientstamp: [217.210.253.102] 2004-10-28 18:44:40 cc: freebsd-current@freebsd.org 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 Reply-To: DiiZzY List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Oct 2004 16:44:42 -0000 quoting "Ketrien I. Saihr-Kesenchedra" : > 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 > Hmm, unfortunately your tip didn't solve my issue but it was worth a try. I recompiled the kernel without pcn and lnc (since lnc will attach if pcn is not found) and here's how it went: kldload if_pcn ifconfig pcn0 inet 192.168.1.40 netmask 255.255.255.0 ping 192.168.1.1 - 100% loss kldunload if_pcn kldload if_pcn ifconfig pcn0 inet 192.168.1.40 netmask 255.255.255.0 ping 192.168.1.1 - 100% loss kldunload pcn kldload if_lnc ifconfig lnc1 inet 192.168.1.40 netmask 255.255.255.0 - lnc1: Initialisation failed If you reboot and load lnc without touching the pcn driver the nic works fine (including ping etc). //Danne