From owner-freebsd-current@FreeBSD.ORG Fri Aug 13 19:45:33 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E6E61065698 for ; Fri, 13 Aug 2010 19:45:33 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by mx1.freebsd.org (Postfix) with ESMTP id 5D84B8FC08 for ; Fri, 13 Aug 2010 19:45:33 +0000 (UTC) Received: by pvg4 with SMTP id 4so1113794pvg.13 for ; Fri, 13 Aug 2010 12:45:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=LgPd9hRYFycm1OedfLnjjJ4HwQx8sucxVS1co3i2KHQ=; b=wAdG8M8ys4Z1Kwy1R9PTN/z190cev5awrS0KiruN1PrE2JSYByPIXafX7llDRiBb5H CvyQ9dXRetR6VOghPc0Ms84/b9KLPet3v+s7l7cS36c/xhQB/iEnc/A0gvwEOJSPgC8W MR/f97aHZIt6vwhKHQ3yfFXH0HvyHgmtbGlIY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=hl3gOYFB/fmNyVUz97kMutgS+T+FcNSXaIh0lQqT/gsT6efNH1/WV8m/gSiPGBTqWM 0ZysfM+ZCuVmEMAhsm7georymEXu4R5jOBWHGuSokBoKLub2SUtruPCnB3VFFmq9/7B4 cBkZkVzp7o8/Fjbnac+aKG7msLw+ZPAsX4grI= Received: by 10.142.172.1 with SMTP id u1mr1609042wfe.286.1281728731986; Fri, 13 Aug 2010 12:45:31 -0700 (PDT) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id v13sm1142321wfv.5.2010.08.13.12.45.27 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 13 Aug 2010 12:45:28 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Fri, 13 Aug 2010 12:45:29 -0700 From: Pyun YongHyeon Date: Fri, 13 Aug 2010 12:45:29 -0700 To: "Sergey V. Dyatko" Message-ID: <20100813194529.GB25752@michelle.cdnetworks.com> References: <20100813102206.1756fbe9@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100813102206.1756fbe9@gmail.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org Subject: Re: if_alc trouble X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Aug 2010 19:45:33 -0000 On Fri, Aug 13, 2010 at 10:22:06AM +0300, Sergey V. Dyatko wrote: > Hi all, > I have strange problem: > > NIC: > alc0@pci0:2:0:0: class=0x020000 card=0x38a317aa chip=0x10621969 > rev=0xc0 hdr=0x00 vendor = 'Attansic (Now owned by Atheros)' > device = 'Atheros AR8132 PCI-E Fast Ethernet Controller > (AR8132)' class = network > subclass = ethernet > > % uname -a > FreeBSD laptop.minsk.domain 9.0-CURRENT FreeBSD 9.0-CURRENT #8 r209973: > Tue Jul 13 10:17:08 EEST 2010 > root@laptop.minsk.domain:/usr/obj/usr/src/sys/b450 i386 > > I'm using if_alc as a kernel module, when I boot with plugged in > cable all works fine, but when I booting with unplugged > cable - network doesn't work. > > I'm trying kenv hw.alc.msi_disable=1 and kldload if_alc.. > from messages: > > Aug 13 09:06:12 laptop kernel: alc0: Ethernet> port 0x3000-0x307f mem 0x96100000-0x9613ffff ir q 16 at > Ethernet> device 0.0 on pci2 > Aug 13 09:06:12 laptop kernel: alc0: 15872 Tx FIFO, 15360 Rx FIFO > Aug 13 09:06:12 laptop kernel: miibus0: on alc0 > Aug 13 09:06:12 laptop kernel: atphy0: PHY > 0 on miibus0 Aug 13 09:06:12 laptop kernel: atphy0: 10baseT, > 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Aug 13 09:06:12 laptop > kernel: alc0: Ethernet address: 00:1f:16:2e:fa:49 Aug 13 09:06:12 > laptop kernel: alc0: [FILTER] Aug 13 09:06:12 laptop kernel: alc0: link > state changed to DOWN Aug 13 09:06:15 laptop kernel: alc0: link state > changed to UP Aug 13 09:06:15 laptop kernel: alc0: DMA write error! -- > resetting Aug 13 09:06:15 laptop kernel: alc0: link state changed to > DOWN Aug 13 09:06:16 laptop kernel: alc0: promiscuous mode enabled > Aug 13 09:06:17 laptop kernel: alc0: link state changed to UP > Aug 13 09:06:18 laptop kernel: alc0: DMA write error! -- resetting > Aug 13 09:06:18 laptop kernel: alc0: link state changed to DOWN > Aug 13 09:06:20 laptop kernel: alc0: link state changed to UP > Aug 13 09:06:21 laptop kernel: alc0: DMA write error! -- resetting > > > how to repeat: > 1) boot with unplugged cable (if_alc_load="YES" on loader.conf) > 2) plug-in cable > 3) dhclient alc0 > 4) tcpdump -ni alc0 -vvv -> http://tiger.ipfw.ru/files/tcpdump.txt > 5) reboot with plugged cable.. > 6) dhclient alc0 > .... > [tiger@laptop]~%ifconfig alc0 > alc0: flags=8843 metric 0 mtu > 1500 > options=c3198 > ether 00:1f:16:2e:fa:49 inet 192.168.9.150 netmask 0xffffff00 broadcast > 192.168.9.255 media: Ethernet autoselect (100baseTX ) > status: active > > now I can unplug cable, unload if_alc, load it again, plug cable -- all > works fine.. > I'm working on it but I was not able to reproduce the issue on my AR8131/AR8132/AR8151/AR8152 sample boards. However it seems AR8132 is the only controller that shows this issue and I vaguely remember a couple of users reported the issue. I'll update PR 148772 if I manage to find some clue.