ath5k deadlock w/ blob transfer
Hi,
Guess, this is better suited in here:
Quoted 5 lines
- ath5k: when starting a blob transfer eg. ssh summer.jpg to the notebook with the ath5k driver running, the wNIC freezes almost immediately! Dead device. This is unfortunately too easily reproducible. In fact, this is a blocker, wireless blob transfer via ssh (other means not tested) is not possible w/o locking it up.
But wait! I just remembered another case. Using the (incomprehensibly) "obsolete" madwifi diver (note aside: this driver _does_ reduce the _felt_ deadlock frequency or kernel panics, referenced by http://lkml.org/lkml/2010/5/3/229, but not entirely make them go away). It evenly locks the wireless NIC while transferring blobs.
So where should I be posting this? When both drivers deadlock it's either a common base in the wireless driver premisses or yet up the path somewhere in the kernel code.
Ideas?
Thanks,
Nils
Quoted 8 lines · Nils Radtke
Hi,
Guess, this is better suited in here:
Quoted 3 lines
- ath5k: when starting a blob transfer eg. ssh summer.jpg to the notebook with the ath5k driver running, the wNIC freezes almost immediately! Dead device. This is unfortunately too easily reproducible.
So where should I be posting this?
You're in the right place...
Quoted 3 lines
When both drivers deadlock it's either a common
base in the wireless driver premisses or yet up the path somewhere in the kernel code.
(Or hardware. madwifi doesn't use mac80211 so it is probably not common code, but ath5k could have inherited a bug from it.)
Quoted 1 line
Ideas?
I missed the first email. What type of machine? System lockup or the connection drops? Do you get any output on the console or in dmesg? (try switching to a text console before your scp test.) If not, any output after lockup booting with nmi_watchdog=1?
Signature · 1 line
Bob Copeland %% www.bobcopeland.com
Hi,
Quoted 4 lines
I missed the first email. What type of machine? System lockup or the connection drops? Do you get any output on the console or in dmesg? (try switching to a text console before your scp test.) If not, any output after lockup booting with nmi_watchdog=1?
IRC, no system lockup, only driver lockup. But I avoided using wireless for blob transfer for the reliability of the lockups, so it's a couple of months since I deliberately crashed it.. Maybe once in a while it lead to a complete system lockup, but treat this as rumble in my memories (and could be due to the other BUGs reported, also)..
notebook: ACER Extensa 5220
kernels since Linux host 2.6.32.2 #4 PREEMPT Wed Dec 30 15:19:58 CET 2009 i686 and even before lspci:
04:00.0 Ethernet controller: Atheros Communications Inc. AR5001 Wireless Network Adapter (rev 01)
Subsystem: Device 1a32:0105
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+
+FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR-
+<PERR- INTx-
Interrupt: pin A routed to IRQ 17
Region 0: Memory at f8000000 (64-bit, non-prefetchable) [size=64K]
Capabilities: <access denied>
There's another bugreport for this machine, w/ hw info: http://lkml.org/lkml/2010/2/18/104
Ok, trying to lockup the machine once more, will report back then.
Thanks,
Nils