ath5k: can not connect; random system freeze
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Confirmed
|
Medium
|
|||
linux-backports-modules-2.6.27 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Hi!
I'm experiencing troubles with my Wifi.
@ home: WEP 128, link quality changes from 1 bar to 4 bars without any reason as the AP and the PC are in the same room with the same trafic.
@ University: WAP (2?), also has the problem of the link quality. After some usage Wifi disconnect and is no more able to reconnect. The dmesg becomes full of Call Trace (see below). I also experience system crash: nothing is responding anymore! If rhythmbox is playing, it keeps looping at the same sound. There's still output, but it is awful; ex: laaaaaaaaaa.... The only solution is pushing on the power button and waiting till the PC is shutted down.
I'm a bit confused with the following; lspci reports the chipset to be Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter (rev 01)
However, looking at the logs I got:
Dec 3 12:49:38 portant kernel: [ 14.188845] ath5k phy0: Atheros AR5414 chip found (MAC: 0xa0, PHY: 0x61)
Therefore I open a new bug.
Useful information and similar problems can be found there:
[1] https:/
[2] http://
Call Trace:
Dec 3 12:53:00 portant kernel: [ 222.596855] ------------[ cut here ]------------
Dec 3 12:53:00 portant kernel: [ 222.596863] WARNING: at /home/antoine/
Dec 3 12:53:00 portant kernel: [ 222.596866] Modules linked in: ipv6 nfs lockd nfs_acl sunrpc aes_x86_64 aes_generic af_packet radeon drm binfmt_misc ppdev acpi_cpufreq cpufreq_stats cpufreq_userspace cpufreq_powersave cpufreq_ondemand freq_table cpufreq_
Dec 3 12:53:00 portant kernel: [ 222.596959] Pid: 3057, comm: phy0 Tainted: G W 2.6.27-10-generic #1
Dec 3 12:53:00 portant kernel: [ 222.596963]
Dec 3 12:53:00 portant kernel: [ 222.596963] Call Trace:
Dec 3 12:53:00 portant kernel: [ 222.596972] [<ffffffff8024e
Dec 3 12:53:00 portant kernel: [ 222.596977] [<ffffffff80471
Dec 3 12:53:00 portant kernel: [ 222.596986] [<ffffffffa024a
Dec 3 12:53:00 portant kernel: [ 222.596992] [<ffffffff803a7
Dec 3 12:53:00 portant kernel: [ 222.596995] [<ffffffff80471
Dec 3 12:53:00 portant kernel: [ 222.597015] [<ffffffffa024d
Dec 3 12:53:00 portant kernel: [ 222.597028] [<ffffffffa0203
Dec 3 12:53:00 portant kernel: [ 222.597042] [<ffffffffa0207
Dec 3 12:53:00 portant kernel: [ 222.597055] [<ffffffffa0207
Dec 3 12:53:00 portant kernel: [ 222.597062] [<ffffffff80262
Dec 3 12:53:00 portant kernel: [ 222.597065] [<ffffffff80262
Dec 3 12:53:00 portant kernel: [ 222.597070] [<ffffffff80267
Dec 3 12:53:00 portant kernel: [ 222.597073] [<ffffffff80262
Dec 3 12:53:00 portant kernel: [ 222.597078] [<ffffffff80266
Dec 3 12:53:00 portant kernel: [ 222.597081] [<ffffffff80213
Dec 3 12:53:00 portant kernel: [ 222.597084] [<ffffffff80266
Dec 3 12:53:00 portant kernel: [ 222.597088] [<ffffffff80213
Dec 3 12:53:00 portant kernel: [ 222.597089]
Dec 3 12:53:00 portant kernel: [ 222.597091] ---[ end trace 92794ffd4e88ba3c ]---
Changed in linux: | |
status: | Unknown → Confirmed |
Changed in linux: | |
importance: | Unknown → Medium |
Hi,
I had the same issue, and after upgrading to latest version of ath5k, it disappear.
So thats really a duplicate of the bug #275423