Re: [ath5k-devel] A weird hw crypto bug...
Well, unless that vendor spun their own silicon, or there's something funky on the board that'd change crypto behaviour, the only thing I can really think of are EEPROM settings. Or maybe the MAC revision is slightly different, I dunno. Adrian ___ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
Re: [ath5k-devel] A weird hw crypto bug...
The same problem described in this thread appear AR2414 hardware. Loading ath5k with nohwcrypt = 1 everything works fine, attached information and evidence that I hope will be useful. If you need more please just ask. # lspci -vvnn -s 03:00.0 03:00.0 Ethernet controller [0200]: Atheros Communications Inc. Atheros AR5001X+ Wireless Network Adapter [168c:0013] (rev 01) Subsystem: Atheros Communications Inc. TRENDnet TEW-443PI Wireless PCI Adapter [168c:2051] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 168 (2500ns min, 7000ns max), Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 17 Region 0: Memory at fbb1 (32-bit, non-prefetchable) [size=64K] Capabilities: [44] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=2 PME- Kernel driver in use: ath5k Kernel modules: ath5k # dmesg|grep -i AR2 [5.617221] ath5k phy0: Atheros AR2414 chip found (MAC: 0x79, PHY: 0x45) # nohwcrypt=1 # ping -M do -s 596 www.google.com -c 10 PING www.l.google.com (173.194.66.104) 596(624) bytes of data. 72 bytes from we-in-f104.1e100.net (173.194.66.104): icmp_req=1 ttl=47 (truncated) 72 bytes from we-in-f104.1e100.net (173.194.66.104): icmp_req=2 ttl=47 (truncated) 72 bytes from we-in-f104.1e100.net (173.194.66.104): icmp_req=3 ttl=47 (truncated) 72 bytes from we-in-f104.1e100.net (173.194.66.104): icmp_req=4 ttl=47 (truncated) 72 bytes from we-in-f104.1e100.net (173.194.66.104): icmp_req=5 ttl=47 (truncated) 72 bytes from we-in-f104.1e100.net (173.194.66.104): icmp_req=6 ttl=47 (truncated) 72 bytes from we-in-f104.1e100.net (173.194.66.104): icmp_req=7 ttl=47 (truncated) 72 bytes from we-in-f104.1e100.net (173.194.66.104): icmp_req=8 ttl=47 (truncated) 72 bytes from we-in-f104.1e100.net (173.194.66.104): icmp_req=9 ttl=47 (truncated) 72 bytes from we-in-f104.1e100.net (173.194.66.104): icmp_req=10 ttl=47 (truncated) --- www.l.google.com ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9010ms rtt min/avg/max/mdev = 102.736/108.539/115.692/4.053 ms # ping -M do -s 597 www.google.com -c 10 PING www.l.google.com (173.194.66.103) 597(625) bytes of data. 72 bytes from we-in-f103.1e100.net (173.194.66.103): icmp_req=1 ttl=47 (truncated) 72 bytes from we-in-f103.1e100.net (173.194.66.103): icmp_req=2 ttl=47 (truncated) 72 bytes from we-in-f103.1e100.net (173.194.66.103): icmp_req=3 ttl=47 (truncated) 72 bytes from we-in-f103.1e100.net (173.194.66.103): icmp_req=4 ttl=47 (truncated) 72 bytes from we-in-f103.1e100.net (173.194.66.103): icmp_req=5 ttl=47 (truncated) 72 bytes from we-in-f103.1e100.net (173.194.66.103): icmp_req=6 ttl=47 (truncated) 72 bytes from we-in-f103.1e100.net (173.194.66.103): icmp_req=7 ttl=47 (truncated) 72 bytes from we-in-f103.1e100.net (173.194.66.103): icmp_req=8 ttl=47 (truncated) 72 bytes from we-in-f103.1e100.net (173.194.66.103): icmp_req=9 ttl=47 (truncated) 72 bytes from we-in-f103.1e100.net (173.194.66.103): icmp_req=10 ttl=47 (truncated) --- www.l.google.com ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9011ms rtt min/avg/max/mdev = 96.366/98.926/100.854/1.570 ms # nohwcrypt=0 # ping -M do -s 596 www.google.com -c 10 PING www.l.google.com (173.194.66.105) 596(624) bytes of data. 72 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=1 ttl=47 (truncated) 72 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=2 ttl=47 (truncated) 72 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=3 ttl=47 (truncated) 72 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=4 ttl=47 (truncated) 72 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=5 ttl=47 (truncated) 72 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=6 ttl=47 (truncated) 72 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=7 ttl=47 (truncated) 72 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=8 ttl=47 (truncated) 72 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=9 ttl=47 (truncated) 72 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=10 ttl=47 (truncated) --- www.l.google.com ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9010ms rtt min/avg/max/mdev = 102.150/107.126/119.493/5.145 ms # ping -M do -s 597 www.google.com -c 10 PING www.l.google.com (173.194.66.104) 597(625) bytes of data. --- www.l.google.com ping statistics --- 10 packets transmitted, 0 received, 100% packet loss, time 8999ms # ath_info # ./ath_info fbb1 -==Device Information==- MAC Revision: 2414 (0x79) Device type: 1 2GHz PHY
[ath5k-devel] A weird hw crypto bug...
The same problem described in this thread appear AR2414 hardware. Loading ath5k with nohwcrypt = 1 everything works fine, attached information and evidence that I hope will be useful. Devel if you need more please just ask. # lspci -vvnn -s 03:00.0 03:00.0 Ethernet controller [0200]: Atheros Communications Inc. Atheros AR5001X+ Wireless Network Adapter [168c:0013] (rev 01) Subsystem: Atheros Communications Inc. TRENDnet TEW-443PI Wireless PCI Adapter [168c:2051] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 168 (2500ns min, 7000ns max), Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 17 Region 0: Memory at fbb1 (32-bit, non-prefetchable) [size=64K] Capabilities: [44] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=2 PME- Kernel driver in use: ath5k Kernel modules: ath5k # dmesg|grep -i AR2 [5.617221] ath5k phy0: Atheros AR2414 chip found (MAC: 0x79, PHY: 0x45) # nohwcrypt=1 # ping -M do -s 596 www.google.com -c 10 PING www.l.google.com (173.194.66.104) 596(624) bytes of data. 72 bytes from we-in-f104.1e100.net (173.194.66.104): icmp_req=1 ttl=47 (truncated) 72 bytes from we-in-f104.1e100.net (173.194.66.104): icmp_req=2 ttl=47 (truncated) 72 bytes from we-in-f104.1e100.net (173.194.66.104): icmp_req=3 ttl=47 (truncated) 72 bytes from we-in-f104.1e100.net (173.194.66.104): icmp_req=4 ttl=47 (truncated) 72 bytes from we-in-f104.1e100.net (173.194.66.104): icmp_req=5 ttl=47 (truncated) 72 bytes from we-in-f104.1e100.net (173.194.66.104): icmp_req=6 ttl=47 (truncated) 72 bytes from we-in-f104.1e100.net (173.194.66.104): icmp_req=7 ttl=47 (truncated) 72 bytes from we-in-f104.1e100.net (173.194.66.104): icmp_req=8 ttl=47 (truncated) 72 bytes from we-in-f104.1e100.net (173.194.66.104): icmp_req=9 ttl=47 (truncated) 72 bytes from we-in-f104.1e100.net (173.194.66.104): icmp_req=10 ttl=47 (truncated) --- www.l.google.com ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9010ms rtt min/avg/max/mdev = 102.736/108.539/115.692/4.053 ms # ping -M do -s 597 www.google.com -c 10 PING www.l.google.com (173.194.66.103) 597(625) bytes of data. 72 bytes from we-in-f103.1e100.net (173.194.66.103): icmp_req=1 ttl=47 (truncated) 72 bytes from we-in-f103.1e100.net (173.194.66.103): icmp_req=2 ttl=47 (truncated) 72 bytes from we-in-f103.1e100.net (173.194.66.103): icmp_req=3 ttl=47 (truncated) 72 bytes from we-in-f103.1e100.net (173.194.66.103): icmp_req=4 ttl=47 (truncated) 72 bytes from we-in-f103.1e100.net (173.194.66.103): icmp_req=5 ttl=47 (truncated) 72 bytes from we-in-f103.1e100.net (173.194.66.103): icmp_req=6 ttl=47 (truncated) 72 bytes from we-in-f103.1e100.net (173.194.66.103): icmp_req=7 ttl=47 (truncated) 72 bytes from we-in-f103.1e100.net (173.194.66.103): icmp_req=8 ttl=47 (truncated) 72 bytes from we-in-f103.1e100.net (173.194.66.103): icmp_req=9 ttl=47 (truncated) 72 bytes from we-in-f103.1e100.net (173.194.66.103): icmp_req=10 ttl=47 (truncated) --- www.l.google.com ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9011ms rtt min/avg/max/mdev = 96.366/98.926/100.854/1.570 ms # nohwcrypt=0 # ping -M do -s 596 www.google.com -c 10 PING www.l.google.com (173.194.66.105) 596(624) bytes of data. 72 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=1 ttl=47 (truncated) 72 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=2 ttl=47 (truncated) 72 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=3 ttl=47 (truncated) 72 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=4 ttl=47 (truncated) 72 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=5 ttl=47 (truncated) 72 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=6 ttl=47 (truncated) 72 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=7 ttl=47 (truncated) 72 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=8 ttl=47 (truncated) 72 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=9 ttl=47 (truncated) 72 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=10 ttl=47 (truncated) --- www.l.google.com ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9010ms rtt min/avg/max/mdev = 102.150/107.126/119.493/5.145 ms # ping -M do -s 597 www.google.com -c 10 PING www.l.google.com (173.194.66.104) 597(625) bytes of data. --- www.l.google.com ping statistics --- 10 packets transmitted, 0 received, 100% packet loss, time 8999ms # ath_info # ./ath_info fbb1 -==Device Information==- MAC Revision: 2414 (0x79) Device type: 1 2GHz PHY
Re: [ath5k-devel] A weird hw crypto bug...
On 21 November 2011 19:16, Albert Gall ss3...@gmail.com wrote: The same problem described in this thread appear AR2414 hardware. Loading ath5k with nohwcrypt = 1 everything works fine, attached information and evidence that I hope will be useful. If you need more please just ask. Well, what would be useful is figuring out why the frames are being dropped in the first place. Nick, did you get verification whether this is a bug with crypto TX, RX or both? Adrian ___ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
Re: [ath5k-devel] A weird hw crypto bug...
On Mon, Nov 21, 2011 at 9:01 AM, Adrian Chadd adr...@freebsd.org wrote: Well, unless that vendor spun their own silicon, or there's something funky on the board that'd change crypto behaviour, the only thing I can really think of are EEPROM settings. Or maybe the MAC revision is slightly different, I dunno. Adrian My guess is that they are using some king of ES/pre-production silicon that should have been destroyed, but was instead dumped on the black/grey-market. -- Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-) ___ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
Re: [ath5k-devel] A weird hw crypto bug...
2011/11/22 Gábor Stefanik netrolller...@gmail.com: My guess is that they are using some king of ES/pre-production silicon that should have been destroyed, but was instead dumped on the black/grey-market. That should be pretty clear by the MAC major/minor revision. Maybe if someone can write down the exact part number from the MAC itself. Adrian ___ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
