Skip to contentSkip to conversation

ath9k very unstable and kills file-system.

DISCUSSION Ben Greear 4 participants 4 messages Nov 20, 2010

lore
Share & tools
lore

Ben Greear

author
#0 lore raw

It's been another frustrating week for using ath9k.

With a patched wpa_supplicant (found here:
https://github.com/greearb/hostap-ct/tree/)
I can reliably cause ath9k to spew all sorts of DMA warnings and evidently crash the hard-drive controller and/or corrupt the file system so bad that fsck cannot fix it. (Back up anything you want to keep before attempting to reproduce this.)

The test case is simply create 30 or so STA interfaces, run one instance of the patched wpa_supplicant to control the 30 interfaces, and send a bit of traffic across the interfaces. It's not even needed to send any significant data...probably just the supplicant associate logic is enough.

You'll want the xmit locking patch Felix posted or it will likely spew lockdep warnings and/or lockup before it gets a chance to crash your hard drive.

There are no other /n NICs that can do virtual stations, so I must either get ath9k functional or give up on that feature set entirely.

If anyone wants to help with this and cannot easily reproduce it, please let me know and I'll furnish scripts etc to make it easier to reproduce.

I'm also happy to help test patches.

Thanks,
Ben

Signature · 2 lines
Ben Greear <[email protected]>
Candela Technologies Inc  http://www.candelatech.com
#1 lore raw
Quoted 19 lines · Ben Greear

It's been another frustrating week for using ath9k.

With a patched wpa_supplicant (found here:
https://github.com/greearb/hostap-ct/tree/)
I can reliably cause ath9k to spew all sorts of DMA warnings and evidently crash the hard-drive controller and/or corrupt the file system so bad that fsck cannot fix it.  (Back up anything you want to keep before attempting to reproduce this.)

The test case is simply create 30 or so STA interfaces, run one instance of the patched wpa_supplicant to control the 30 interfaces, and send a bit of traffic across the interfaces.  It's not even needed to send any significant data...probably just the supplicant associate logic is enough.

You'll want the xmit locking patch Felix posted or it will likely spew lockdep warnings and/or lockup before it gets a chance to crash your hard drive.

Quoted 8 lines

There are no other /n NICs that can do virtual stations, so I must either get ath9k functional or give up on that feature set entirely.

If anyone wants to help with this and cannot easily reproduce it, please let me know and I'll furnish scripts etc to make it easier to reproduce.

I'm also happy to help test patches.

If you can provide scripts it will help. The easier it is to reproduce the easier it can get fixed.

Luis

#2 lore raw
In reply to Ben Greear
Quoted 8 lines · Ben Greear

It's been another frustrating week for using ath9k.

With a patched wpa_supplicant (found here:
https://github.com/greearb/hostap-ct/tree/)
I can reliably cause ath9k to spew all sorts of DMA warnings and evidently crash the hard-drive controller and/or corrupt the file system so bad that fsck cannot fix it. (Back up anything you want to keep before attempting to reproduce this.)

The rx dma warnings went away on my devices with my patch "ath9k: fix timeout on stopping rx dma"
Please try that one and see if it helps with your corruption issues.

- Felix

#3 lore raw
In reply to Ben Greear
Quoted 2 lines · Ben Greear

There are no other /n NICs that can do virtual stations, so I must either get ath9k functional or give up on that feature set entirely.

Ben, I for one really appreciate the work you've put into testing ath9k. I'm quite sure that the fixes found through your efforts have increased ath9k quality a great deal, also for more common use-cases.

For the sake of all our hard-drives, please don't give up. ;)

/Björn