Re: if_alc trouble
Pyun YongHyeon wrote: 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. I have the same problem with the alc on my compaq mini. Perhaps it is related to the PHY mismatch. For some reason they coupled a GE PHY with a FE controller. I need to stop my switch advertising 1000M for the laptop to autonegotiate the link speed. alc0: Atheros AR8132 PCIe Fast Ethernet port 0xec80-0xecff mem 0xfebc-0xfebf irq 17 at device 0.0 on pci2 alc0: 15872 Tx FIFO, 15360 Rx FIFO alc0: Using 1 MSI message(s). miibus0: MII bus on alc0 atphy0: Atheros F1 10/100/1000 PHY PHY 0 on miibus0 atphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto alc0: Ethernet address: 00:25:b3:7e:b7:2d alc0: [FILTER] Ian -- Ian Freislich ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: if_alc trouble
Hi! Pyun YongHyeon wrote: 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. I have the same problem with the alc on my compaq mini. Perhaps it is related to the PHY mismatch. For some reason they coupled a GE PHY with a FE controller. I need to stop my switch advertising 1000M for the laptop to autonegotiate the link speed. I had it on a 10/100 hub, still observed the problem. -- p...@opsec.eu+49 171 310137210 years to go ! ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: if_alc trouble
Kurt Jaeger wrote: Hi! Pyun YongHyeon wrote: 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. I have the same problem with the alc on my compaq mini. Perhaps it is related to the PHY mismatch. For some reason they coupled a GE PHY with a FE controller. I need to stop my switch advertising 1000M for the laptop to autonegotiate the link speed. I had it on a 10/100 hub, still observed the problem. I meant that the problem is the wierd PHY/MAC arangement on this chip, not what it's plugged into. Ian -- Ian Freislich ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: if_alc trouble
On Sat, 14 Aug 2010, Ian FREISLICH wrote: Pyun YongHyeon wrote: 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. I have the same problem with the alc on my compaq mini. Perhaps it is related to the PHY mismatch. For some reason they coupled a GE PHY with a FE controller. I need to stop my switch advertising 1000M for the laptop to autonegotiate the link speed. Acer Aspire One D250 has the same chip and problem (8.1-stable): alc0: Atheros AR8132 PCIe Fast Ethernet port 0x2000-0x207f mem 0x5500-0x5503 irq 18 at device 0.0 on pci3 alc0: 15872 Tx FIFO, 15360 Rx FIFO alc0: Using 1 MSI message(s). miibus0: MII bus on alc0 atphy0: Atheros F1 10/100/1000 PHY PHY 0 on miibus0 atphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto alc0: Ethernet address: 00:23:5a:80:d8:7a alc0: [FILTER] Forcing it to a fixed speed works: ifconfig_alc0=SYNCDHCP media 100baseTX ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: if_alc trouble
Hi! NIC: a...@pci0:2:0:0:class=0x02 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 There's a ticket with a patch: kern/148772 and it's being worked on. Please check, whether the latest patch solves your problem. -- p...@opsec.eu+49 171 310137210 years to go ! ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: if_alc trouble
On Fri, Aug 13, 2010 at 10:22:06AM +0300, Sergey V. Dyatko wrote: Hi all, I have strange problem: NIC: a...@pci0:2:0:0:class=0x02 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 r...@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: Atheros AR8132 PCIe Fast Ethernet port 0x3000-0x307f mem 0x9610-0x9613 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: MII bus on alc0 Aug 13 09:06:12 laptop kernel: atphy0: Atheros F1 10/100/1000 PHY 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 [ti...@laptop]~%ifconfig alc0 alc0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=c3198VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MCAST,WOL_MAGIC,VLAN_HWTSO,LINKSTATE ether 00:1f:16:2e:fa:49 inet 192.168.9.150 netmask 0xff00 broadcast 192.168.9.255 media: Ethernet autoselect (100baseTX full-duplex) 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. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
