From: Steve Brown <sbrown@cortland.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] AR9260 hang during connection to AP
Date: Thu, 19 Feb 2009 14:19:04 -0500 [thread overview]
Message-ID: <499DB0A8.1040706@cortland.com> (raw)
In-Reply-To: <18835.426.261949.207749@gargle.gargle.HOWL>
(forgot to cc the list)
Sujith wrote:
> Alex Williams wrote:
>
>> Thank you for reply!
>> Please, tell me: did you saw working card on ar9160 ever??? May be
>> with other interfaces, such as PCI or USB? Is support for ar9160
>> finished? Or it's now unusable?
>>
>
> No idea. But I found a mini-PCI AR9160 card and it works fine here.
>
>
>> insmod ath9k.ko debug=0x2000
>> [ 121.839737] ath9k 0000:00:05.0: PCI INT A -> Link[LN_B] -> GSI 10
>> (level, low) -> IRQ 10
>> modprobe: FATAL: Could not load
>> /lib/modules/2.6.29-rc4-wl/modules.dep: No such file or directory
>> [ 123.479199] cfg80211: Calling CRDA for country: US
>> [ 123.507201] udev: renamed network interface wlan0 to wlan1
>> [ 123.512965] Registered led device: ath9k-phy0::radio
>> [ 123.546520] Registered led device: ath9k-phy0::assoc
>> [ 123.589623] Registered led device: ath9k-phy0::tx
>> [ 123.614561] cfg80211: Regulatory domain changed to country: US
>> [ 123.620474] (start_freq - end_freq @ bandwidth),
>> (max_antenna_gain, max_eirp)
>> [ 123.628382] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
>> [ 123.635228] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
>> [ 123.642074] (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
>> [ 123.648921] (5490000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
>> [ 123.655907] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
>> [ 123.685508] Registered led device: ath9k-phy0::rx
>> [ 123.727397] phy0: Atheros AR9160 MAC/BB Rev:1 AR5133 RF Rev:b0:
>> mem=0xcf520000, irq=10
>> insert ath9k.ko
>> [ 124.070622] ADDRCONF(NETDEV_UP): wlan1: link is not ready
>>
>
> CONFIG_ATH9K_DEBUG should be enabled in your kernel .config to enable debugging.
> See: http://wireless.kernel.org/en/users/Drivers/ath9k
>
>
>>> Are you able to at least scan, before trying to associate with an AP ?
>>> If so, then switch to a VT and try to associate and see if the kernel panics.
>>> A digital photograph of the panic (if one occurs) would be great.
>>>
>> To perform scan, we need to "up" interface. Strange, but now, after
>> ifconfig wlan1 up - system hang deadly without any explanations! T_T
>> But sometimes it continue work after module load...
>>
>
> Did you switch to a VT to see if a panic happens on bringing up the interface ?
>
>
>> Really??? ^_^ It's impossible! Is there some datasheet on ar9160???
>> How about register addresses and their purpose? How can you write
>> driver for device if you do not know how it actually works? Writing
>> drivers it's like an embedded programming on microcontrolles without
>> OS - you should know every register and it's purpose. And even this
>> knowledge not guarantee errors proof... Sorry, I'm just wondering how
>> this possible... I heards that for ath9k Atheros released
>> specifications, or they writing in-house driver?.. Please, more info,
>> how it's really developing... =)
>>
>>
>
> AR9160 is supported by ath9k, so no worries here.
>
>
>> How to enable additional debug info? Can I use KDBG + /dev/ttyS0 to
>> search for the problem? :)
>>
>
> Search for serial console / netconsole debugging guides on the net.
>
>
>> Please, give me a link to git tutorial. I want to modifi some wireless
>> files, but keep ability to update them by "git pull"... Sorry, I'm
>> newbie...
>>
>
> http://wireless.kernel.org/en/developers/Documentation/git-guide
>
> Sujith
>
I'm having the same problem. The driver loads and the device scans. The
oops happens while networkmanager is trying to associate with an AP.
01:0b.0 Network controller: Atheros Communications Inc. AR9160
802.11abgn Wireless PCI Adapter (rev 01)
01:0b.0 0280: 168c:0027 (rev 01)
Subsystem: 168c:2082
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 5
Memory at fe5e0000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [44] Power Management version 2
Kernel modules: ath9k
The card is a Sparklan WMIA-199N.
The machine is a P4 2.80GHz running ubuntu and v2.6.29-rc5-14641-g562bdf5
The driver on loading:
Feb 19 09:16:23 ubuntu kernel: [ 4676.662134] ath9k 0000:01:0b.0: PCI
INT A -> Link[LNKG] -> GSI 5 (level, low) -> IRQ 5
Feb 19 09:16:24 ubuntu kernel: [ 4679.635453] phy2: Selected rate
control algorithm 'ath9k_rate_control'
Feb 19 09:16:24 ubuntu kernel: [ 4679.676985] cfg80211: Calling CRDA for
country: AM
Feb 19 09:16:24 ubuntu kernel: [ 4679.677041] Registered led device:
ath9k-phy2::radio
Feb 19 09:16:24 ubuntu kernel: [ 4679.677060] Registered led device:
ath9k-phy2::assoc
Feb 19 09:16:24 ubuntu kernel: [ 4679.677078] Registered led device:
ath9k-phy2::tx
Feb 19 09:16:24 ubuntu kernel: [ 4679.677103] Registered led device:
ath9k-phy2::rx
Feb 19 09:16:24 ubuntu kernel: [ 4679.677113] phy2: Atheros AR9160
MAC/BB Rev:1 AR5133 RF Rev:b0: mem=0xf80c0000, irq=5
Feb 19 09:16:24 ubuntu kernel: [ 4679.701984] udev: renamed network
interface wlan0 to wlan2
The netconsole output is attached.
Hope I haven't missed anything.
Steve
------------------------------------------------------------------------
Feb 19 12:51:12 192.168.1.7 [ 307.761386] ------------[ cut here ]------------
Feb 19 12:51:12 192.168.1.7 [ 307.761399] kernel BUG at drivers/net/wireless/ath9k/rc.c:745!
Feb 19 12:51:12 192.168.1.7 [ 307.761404] invalid opcode: 0000 [#1]
Feb 19 12:51:12 192.168.1.7
Feb 19 12:51:12 192.168.1.7 [ 307.761411] last sysfs file: /sys/devices/pci0000:00/0000:00:1e.0/0000:01:0b.0/net/wlan2/flags
Feb 19 12:51:12 192.168.1.7 [ 307.761417] Modules linked in:
Feb 19 12:51:12 arc4
Feb 19 12:51:12 ecb
Feb 19 12:51:12 ath9k
Feb 19 12:51:12 mac80211
Feb 19 12:51:12 rfkill
Feb 19 12:51:12 cfg80211
Feb 19 12:51:12 led_class
Feb 19 12:51:12 netconsole
Feb 19 12:51:12 configfs
Feb 19 12:51:12 i915
Feb 19 12:51:12 drm
Feb 19 12:51:12 i2c_algo_bit
Feb 19 12:51:12 i2c_core
Feb 19 12:51:12 af_packet
Feb 19 12:51:12 ppdev
Feb 19 12:51:12 speedstep_lib
Feb 19 12:51:12 cpufreq_conservative
Feb 19 12:51:12 cpufreq_powersave
Feb 19 12:51:12 cpufreq_userspace
Feb 19 12:51:12 cpufreq_ondemand
Feb 19 12:51:12 cpufreq_stats
Feb 19 12:51:12 freq_table
Feb 19 12:51:13 rfcomm
Feb 19 12:51:13 sco
Feb 19 12:51:13 bridge
Feb 19 12:51:13 stp
Feb 19 12:51:13 bnep
Feb 19 12:51:13 l2cap
Feb 19 12:51:13 bluetooth
Feb 19 12:51:13 binfmt_misc
Feb 19 12:51:13 ipv6
Feb 19 12:51:13 battery
Feb 19 12:51:13 sbs
Feb 19 12:51:13 sbshc
Feb 19 12:51:13 video
Feb 19 12:51:13 output
Feb 19 12:51:13 container
Feb 19 12:51:13 pci_slot
Feb 19 12:51:13 snd_intel8x0
Feb 19 12:51:13 snd_ac97_codec
Feb 19 12:51:13 ac97_bus
Feb 19 12:51:13 snd_pcm_oss
Feb 19 12:51:13 snd_mixer_oss
Feb 19 12:51:13 snd_pcm
Feb 19 12:51:13 snd_seq_dummy
Feb 19 12:51:13 snd_seq_oss
Feb 19 12:51:13 snd_seq_midi
Feb 19 12:51:13 snd_rawmidi
Feb 19 12:51:13 snd_seq_midi_event
Feb 19 12:51:13 snd_seq
Feb 19 12:51:13 snd_timer
Feb 19 12:51:13 snd_seq_device
Feb 19 12:51:13 snd
Feb 19 12:51:13 psmouse
Feb 19 12:51:14 serio_raw
Feb 19 12:51:14 pcspkr
Feb 19 12:51:14 soundcore
Feb 19 12:51:14 snd_page_alloc
Feb 19 12:51:14 evdev
Feb 19 12:51:14 iTCO_wdt
Feb 19 12:51:14 iTCO_vendor_support
Feb 19 12:51:14 button
Feb 19 12:51:14 shpchp
Feb 19 12:51:14 pci_hotplug
Feb 19 12:51:14 intel_agp
Feb 19 12:51:14 agpgart
Feb 19 12:51:14 parport_pc
Feb 19 12:51:14 lp
Feb 19 12:51:14 parport
Feb 19 12:51:14 ac
Feb 19 12:51:14 iptable_filter
Feb 19 12:51:14 ip_tables
Feb 19 12:51:14 x_tables
Feb 19 12:51:14 ext3
Feb 19 12:51:14 jbd
Feb 19 12:51:14 mbcache
Feb 19 12:51:14 usbhid
Feb 19 12:51:14 hid
Feb 19 12:51:14 sr_mod
Feb 19 12:51:14 cdrom
Feb 19 12:51:14 sd_mod
Feb 19 12:51:14 crc_t10dif
Feb 19 12:51:14 sg
Feb 19 12:51:14 ata_piix
Feb 19 12:51:14 pata_acpi
Feb 19 12:51:14 ata_generic
Feb 19 12:51:14 libata
Feb 19 12:51:15 scsi_mod
Feb 19 12:51:15 ehci_hcd
Feb 19 12:51:15 uhci_hcd
Feb 19 12:51:15 e100
Feb 19 12:51:15 mii
Feb 19 12:51:15 usbcore
Feb 19 12:51:15 thermal
Feb 19 12:51:15 processor
Feb 19 12:51:15 fan
Feb 19 12:51:15 fuse
Feb 19 12:51:15 192.168.1.7
Feb 19 12:51:15 192.168.1.7 [ 307.761748]
Feb 19 12:51:15 192.168.1.7 [ 307.761753] Pid: 5611, comm: phy0 Not tainted (2.6.29-rc5-wl #6) To Be Filled By O.E.M.
Feb 19 12:51:15 192.168.1.7 [ 307.761758] EIP: 0060:[<f87a7bcf>] EFLAGS: 00010246 CPU: 0
Feb 19 12:51:15 192.168.1.7 [ 307.761771] EIP is at ath_get_rate+0x28f/0x620 [ath9k]
Feb 19 12:51:15 192.168.1.7 [ 307.761776] EAX: 00000000 EBX: 0000001c ECX: 00000000 EDX: f87c4980
Feb 19 12:51:15 192.168.1.7 [ 307.761780] ESI: 0000001c EDI: f87c4980 EBP: dfeb7d2c ESP: dfeb7cdc
Feb 19 12:51:15 192.168.1.7 [ 307.761786] DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068
Feb 19 12:51:15 192.168.1.7 [ 307.761792] Process phy0 (pid: 5611, ti=dfeb6000 task=dfd63cf0 task.ti=dfeb6000)
Feb 19 12:51:15 192.168.1.7 [ 307.761795] Stack:
Feb 19 12:51:15 192.168.1.7 [ 307.761799] df307d08
Feb 19 12:51:15 c013fcc3
Feb 19 12:51:15 ee059860
Feb 19 12:51:15 dfeb7d08
Feb 19 12:51:15 00000046
Feb 19 12:51:15 2aeb7d20
Feb 19 12:51:15 dfd32800
Feb 19 12:51:15 d870eb00
Feb 19 12:51:15 192.168.1.7
Feb 19 12:51:15 192.168.1.7 [ 307.761824]
Feb 19 12:51:15 00000148
Feb 19 12:51:15 ee14fe00
Feb 19 12:51:16 e7dda410
Feb 19 12:51:16 ee14fe20
Feb 19 12:51:16 00002863
Feb 19 12:51:16 00001e50
Feb 19 12:51:16 f87c4980
Feb 19 12:51:16 0000001c
Feb 19 12:51:16 192.168.1.7
Feb 19 12:51:16 192.168.1.7 [ 307.761931]
Feb 19 12:51:16 1d1c000a
Feb 19 12:51:16 f87c3500
Feb 19 12:51:16 ee14fe20
Feb 19 12:51:16 ee1b0b80
Feb 19 12:51:16 dfeb7d50
Feb 19 12:51:16 f845d82d
Feb 19 12:51:16 dfeb7ddc
Feb 19 12:51:16 f87c3500
Feb 19 12:51:16 192.168.1.7
Feb 19 12:51:16 192.168.1.7 [ 307.761964] Call Trace:
Feb 19 12:51:16 192.168.1.7 [ 307.761968]
Feb 19 12:51:16 [<c013fcc3>] ? getnstimeofday+0x53/0x110
Feb 19 12:51:16 192.168.1.7 [ 307.761986]
Feb 19 12:51:16 [<f845d82d>] ? rate_control_get_rate+0xbd/0xd0 [mac80211]
Feb 19 12:51:16 192.168.1.7 [ 307.762011]
Feb 19 12:51:16 [<f8464d38>] ? invoke_tx_handlers+0x648/0x10b0 [mac80211]
Feb 19 12:51:16 192.168.1.7 [ 307.762029]
Feb 19 12:51:16 [<c0199043>] ? __slab_alloc+0xb3/0x4f0
Feb 19 12:51:16 192.168.1.7 [ 307.762040]
Feb 19 12:51:16 [<c02ce4f8>] ? skb_release_data+0x68/0xa0
Feb 19 12:51:16 192.168.1.7 [ 307.762048]
Feb 19 12:51:17 [<f8464184>] ? __ieee80211_tx_prepare+0x184/0x340 [mac80211]
Feb 19 12:51:17 192.168.1.7 [ 307.762068]
Feb 19 12:51:17 [<f8466cac>] ? ieee80211_master_start_xmit+0x24c/0x550 [mac80211]
Feb 19 12:51:17 192.168.1.7 [ 307.762091]
Feb 19 12:51:17 [<c02d797b>] ? dev_hard_start_xmit+0x25b/0x2f0
Feb 19 12:51:17 192.168.1.7 [ 307.762102]
Feb 19 12:51:17 [<c02e8bd4>] ? __qdisc_run+0x194/0x1f0
Feb 19 12:51:17 192.168.1.7 [ 307.762174]
Feb 19 12:51:17 [<c01023f4>] ? __switch_to+0xa4/0x190
Feb 19 12:51:17 192.168.1.7 [ 307.762180]
Feb 19 12:51:17 [<c02d89ff>] ? dev_queue_xmit+0x32f/0x580
Feb 19 12:51:17 192.168.1.7 [ 307.762187]
Feb 19 12:51:17 [<c02ced2d>] ? __alloc_skb+0x4d/0x110
Feb 19 12:51:17 192.168.1.7 [ 307.762195]
Feb 19 12:51:17 [<f84689c2>] ? ieee80211_tx_skb+0x52/0x60 [mac80211]
Feb 19 12:51:17 192.168.1.7 [ 307.762212]
Feb 19 12:51:17 [<f8458ded>] ? ieee80211_send_nullfunc+0xbd/0x100 [mac80211]
Feb 19 12:51:17 192.168.1.7 [ 307.762227]
Feb 19 12:51:17 [<c01209cb>] ? __cond_resched+0x1b/0x40
Feb 19 12:51:17 192.168.1.7 [ 307.762235]
Feb 19 12:51:17 [<f8455b2a>] ? ieee80211_scan_completed+0x2da/0x360 [mac80211]
Feb 19 12:51:17 192.168.1.7 [ 307.762251]
Feb 19 12:51:17 [<f8455bb0>] ? ieee80211_scan_work+0x0/0x190 [mac80211]
Feb 19 12:51:17 192.168.1.7 [ 307.762266]
Feb 19 12:51:17 [<f8455d09>] ? ieee80211_scan_work+0x159/0x190 [mac80211]
Feb 19 12:51:17 192.168.1.7 [ 307.762287]
Feb 19 12:51:17 [<c0356f8b>] ? schedule+0x31b/0x4a0
Feb 19 12:51:17 192.168.1.7 [ 307.762297]
Feb 19 12:51:17 [<f8455bb0>] ? ieee80211_scan_work+0x0/0x190 [mac80211]
Feb 19 12:51:17 192.168.1.7 [ 307.762318]
Feb 19 12:51:18 [<c013460b>] ? run_workqueue+0x5b/0x110
Feb 19 12:51:18 192.168.1.7 [ 307.762387]
Feb 19 12:51:18 [<c0134adf>] ? worker_thread+0x7f/0xe0
Feb 19 12:51:18 192.168.1.7 [ 307.762394]
Feb 19 12:51:18 [<c0138150>] ? autoremove_wake_function+0x0/0x50
Feb 19 12:51:18 192.168.1.7 [ 307.762402]
Feb 19 12:51:18 [<c0134a60>] ? worker_thread+0x0/0xe0
Feb 19 12:51:18 192.168.1.7 [ 307.762407]
Feb 19 12:51:18 [<c0137c6a>] ? kthread+0x3a/0x70
Feb 19 12:51:18 192.168.1.7 [ 307.762416]
Feb 19 12:51:18 [<c0137c30>] ? kthread+0x0/0x70
Feb 19 12:51:18 192.168.1.7 [ 307.762422]
Feb 19 12:51:18 [<c0103d27>] ? kernel_thread_helper+0x7/0x10
Feb 19 12:51:18 192.168.1.7 [ 307.762430] Code:
Feb 19 12:51:18 192.168.1.7 8b
Feb 19 12:51:18 192.168.1.7 44
Feb 19 12:51:18 192.168.1.7 c2
Feb 19 12:51:18 192.168.1.7 04
Feb 19 12:51:18 192.168.1.7 85
Feb 19 12:51:18 192.168.1.7 c0
Feb 19 12:51:18 192.168.1.7 74
Feb 19 12:51:18 192.168.1.7 09
Feb 19 12:51:18 192.168.1.7 8b
Feb 19 12:51:18 192.168.1.7 5d
Feb 19 12:51:18 192.168.1.7 c8
Feb 19 12:51:18 192.168.1.7 80
Feb 19 12:51:18 192.168.1.7 7b
Feb 19 12:51:18 192.168.1.7 55
Feb 19 12:51:18 192.168.1.7 00
Message from syslogd at 192.168.1.7 at Feb 19 12:51:24 ...
f>
Feb 19 12:51:24 192.168.1.7 74
Feb 19 12:51:24 192.168.1.7 38
Feb 19 12:51:24 192.168.1.7 8b
Feb 19 12:51:24 192.168.1.7 75
Feb 19 12:51:24 192.168.1.7 ec
Feb 19 12:51:24 192.168.1.7 8b
Feb 19 12:51:24 192.168.1.7 7d
Feb 19 12:51:24 192.168.1.7 e8
Feb 19 12:51:24 192.168.1.7 8d
Feb 19 12:51:24 192.168.1.7 04
Feb 19 12:51:24 192.168.1.7 b6
Feb 19 12:51:24 192.168.1.7 8b
Feb 19 12:51:24 192.168.1.7 44
Feb 19 12:51:24 192.168.1.7 c7
Feb 19 12:51:24 192.168.1.7 08
Feb 19 12:51:24 192.168.1.7 85
Feb 19 12:51:24 192.168.1.7 c0
Feb 19 12:51:24 192.168.1.7 74
Feb 19 12:51:24 192.168.1.7 09
Feb 19 12:51:24 192.168.1.7 8b
Feb 19 12:51:24 192.168.1.7 45
Feb 19 12:51:24 192.168.1.7 c8
Feb 19 12:51:24 192.168.1.7 80
Feb 19 12:51:24 192.168.1.7 78
Feb 19 12:51:24 192.168.1.7 55
Feb 19 12:51:24 192.168.1.7 00
Feb 19 12:51:24 192.168.1.7 75
Feb 19 12:51:24 192.168.1.7 1e
Feb 19 12:51:24 192.168.1.7 f>
Feb 19 12:51:24 192.168.1.7 0b
Feb 19 12:51:24 192.168.1.7 eb
Feb 19 12:51:24 192.168.1.7 fe
Feb 19 12:51:25 192.168.1.7 90
Feb 19 12:51:25 192.168.1.7 8d
Feb 19 12:51:25 192.168.1.7 74
Feb 19 12:51:25 192.168.1.7 26
Feb 19 12:51:25 192.168.1.7 00
Feb 19 12:51:25 192.168.1.7 38
Feb 19 12:51:25 192.168.1.7 d3
Feb 19 12:51:25 192.168.1.7 0f
Feb 19 12:51:25 192.168.1.7 8e
Feb 19 12:51:25 192.168.1.7 5e
Feb 19 12:51:25 192.168.1.7 fe
Feb 19 12:51:25 192.168.1.7 ff
Feb 19 12:51:25 192.168.1.7 ff
Feb 19 12:51:25 192.168.1.7 89
Feb 19 12:51:25 192.168.1.7 d3
Feb 19 12:51:25 192.168.1.7 8d
Feb 19 12:51:25 192.168.1.7 b6
Feb 19 12:51:25 192.168.1.7
Feb 19 12:51:25 192.168.1.7 [ 307.763062] EIP: [<f87a7bcf>]
Feb 19 12:51:25 192.168.1.7 ath_get_rate+0x28f/0x620 [ath9k]
Feb 19 12:51:25 SS: ESP 0068:dfeb7cdc
Feb 19 12:51:25 192.168.1.7 [ 307.763091] ---[ end trace fdaf4ee84daa2dc6 ]---
=======================================
messages
next prev parent reply other threads:[~2009-02-19 19:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 14:17 [ath9k-devel] AR9260 hang during connection to AP Alex Williams
2009-02-11 14:38 ` Sujith
2009-02-11 16:05 ` Alex Williams
2009-02-11 16:49 ` Sujith
2009-02-11 21:00 ` Alex Williams
2009-02-13 12:02 ` Alex Williams
2009-02-19 19:19 ` Steve Brown [this message]
2009-02-20 16:16 ` Steve Brown
2009-02-23 15:36 ` Sujith
2009-02-24 4:42 ` Sujith
2009-02-24 7:51 ` Steve Brown
2009-02-24 9:52 ` Sujith
2009-02-24 18:41 ` Steve Brown
2009-02-25 4:13 ` Sujith
2009-02-25 8:17 ` Steve Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=499DB0A8.1040706@cortland.com \
--to=sbrown@cortland.com \
--cc=ath9k-devel@lists.ath9k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.