Please note: This project is no longer active. The website is kept online for historic purposes only.
If you´re looking for a Linux driver for your Atheros WLAN device, you should continue here .

Ticket #1683 (new defect)

Opened 14 years ago

Last modified 14 years ago

when fragmentation is ON the STA does not send the packet

Reported by: anonymous Assigned to:
Priority: major Milestone:
Component: madwifi: other Version: trunk
Keywords: Cc:
Patch is attached: 0 Pending:

Description (Last modified by mrenzmann)

svn version r2992

I have checked it on various systems ( from Pentium M to pentium D ) and different cards. The Dmesg is also flooded with "ath_mgtstart: discard, no xmit buf" message.

I guess some one tempered with txq queue and left some thing broken.

I have switched back to the stable revision as packets are sent successfully even when fragmented.

Let me know if you need further information.

The AP and stations all use the same version of driver (r2992).

dmesg output:

wlan: 0.8.4.2 (svn r2992)
ath_pci: 0.9.4.5 (svn r2992)
intel8x0_measure_ac97_clock: measured 55343 usecs
intel8x0: clocking to 48000
PCI: Enabling device 0000:00:1e.3 (0000 -> 0001)
ACPI: PCI Interrupt 0000:00:1e.3[B] -> GSI 17 (level, low) -> IRQ 201
PCI: Setting latency timer of device 0000:00:1e.3 to 64
MC'97 1 converters and GPIO not ready (0xff00)
PCI: Enabling device 0000:04:00.0 (0000 -> 0002)
ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 19 (level, low) -> IRQ 177
ath_pci: switching rfkill capability off
ath_rate_sample: 1.2 (svn r2992)
ath_pci: switching per-packet transmit power control off
wifi0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
wifi0: turboA rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
wifi0: turboG rates: 6Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
wifi0: H/W encryption support: WEP AES AES_CCM TKIP
wifi0: mac 5.9 phy 4.3 radio 3.6
wifi0: Use hw queue 1 for WME_AC_BE traffic
wifi0: Use hw queue 0 for WME_AC_BK traffic
wifi0: Use hw queue 2 for WME_AC_VI traffic
wifi0: Use hw queue 3 for WME_AC_VO traffic
wifi0: Use hw queue 8 for CAB traffic
wifi0: Use hw queue 9 for beacons
wifi0: Atheros 5212: mem=0x32000000, irq=177

Attachments

madwifi-frag.dump.bz2 (54.0 kB) - added by onelektra@gmx.net on 02/22/08 08:29:39.
tcpdump file from VAP

Change History

12/04/07 06:02:43 changed by mrenzmann

  • version set to trunk.
  • description changed.

Please verify if latest trunk still suffers from this problem.

(follow-up: ↓ 3 ) 12/04/07 06:07:46 changed by a DOT malik AT ee DOT unimelb DOT edu DOT au

I will do that shortly ( hopefully today )

(in reply to: ↑ 2 ) 02/05/08 09:14:29 changed by onelektra@gmx.net

It is still an issue. Tested it today in ad-hoc mode with madwifi-ng-r3334-20080204. How can I help? Hope this is fixed soon, we need it to test mesh protocols in a grid of 7x7 nodes. A good chance to find issues with the driver in ad-hoc.

02/05/08 10:11:00 changed by onelektra@gmx.net

I can confirm that fragmentation works in ad-hoc with 0.9.3.3. So the bug came in after the release.

(follow-up: ↓ 6 ) 02/05/08 10:32:20 changed by mrenzmann

Can you please try whether the bug exists in release candidate 2 of v0.9.4? A snapshot is available for download here.

(in reply to: ↑ 5 ; follow-up: ↓ 7 ) 02/05/08 13:22:44 changed by onelektra@gmx.net

Replying to mrenzmann: The fragmentation bug is present in 0.9.4-rc2 as well. I have tested with two X86 machines using kernel 2.6.22. 0.9.3.3 works, 0.9.4 doesn't.

(in reply to: ↑ 6 ) 02/05/08 13:49:40 changed by mrenzmann

Replying to onelektra@gmx.net:

The fragmentation bug is present in 0.9.4-rc2 as well. I have tested with two X86 machines using kernel 2.6.22. 0.9.3.3 works, 0.9.4 doesn't.

Thanks for testing and feedback. This might become a showstopper for 0.9.4. See also here.

02/22/08 08:29:39 changed by onelektra@gmx.net

  • attachment madwifi-frag.dump.bz2 added.

tcpdump file from VAP

02/22/08 08:30:59 changed by onelektra@gmx.net

The fragmentation bug is also present in 0.9.3.3. It just occurs randomly, and I have the impression it happens more often with 0.9.4 than 0.9.3.3 but this is just a vague guess. I tried to reproduce the behavior with two machines running 0.9.4 on 2.6.22 but it didn't happen. I was running floodping -s 1500 from both sides (WRAP and Notebook) for 30 minutes and it didn't occur. Meanwhile the problem occurred again in our mesh grid. So that gave us an opportunity to measure.

I did: Ping from 172.30.1.17 (meshnode) -> 172.30.1.1 (notebook) with ping -s 1400, while listening to the traffic on 172.30.1.1 with monitor vap. I don't know if the attached dump is helpful.

If you need further information I am glad to help.