[Solved] Hard freezes with kernel 2.6.33 - possibly ath9k?

hokasch · 2010-04-20 12:54:50

These hard freezes started recently, but are quite random. I ran some hardwarechecks and found nothing. After it crashed about 8 times in one day I downgraded to 2.6.32 and had no lockups now for two days. Booted up 2.6.33-ck today (used .33-ck before, identical symptoms as with the arch kernel) - didn't take long, and "zappp"...

Freeze!
- monitor freezes
- sound stutters loopily
- capslock blinking
- completely unresponsive, no dice with sysrq either

There is nothing in the log files directly related to the crash, but I get this warning since 2.6.33:

Apr 16 15:03:54 arch kernel: WARNING: at kernel/softirq.c:143 local_bh_enable_ip+0x82/0xb0()
Apr 16 15:03:54 arch kernel: Hardware name: Extensa 5635ZG   
Apr 16 15:03:54 arch kernel: Modules linked in: cryptd aes_x86_64 aes_generic ath_pci wlan ath_hal arc4 snd_seq_dummy ecb snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss snd_hda_codec_conexant ath9k ath9k_common snd_hda_intel mac80211 snd_hda_codec snd_hwdep ath9k_hw ath snd_pcm snd_timer cpufreq_ondemand cfg80211 rfkill video snd soundcore joydev output led_class wmi battery ac thermal button snd_page_alloc acpi_cpufreq iTCO_wdt iTCO_vendor_support i2c_i801 sr_mod uhci_hcd nvidia(P) cdrom intel_agp i2c_core ehci_hcd atl1c evdev psmouse sg serio_raw freq_table processor usbhid hid usbcore fuse rtc_cmos rtc_core rtc_lib sd_mod ahci libata scsi_mod ext4 jbd2 crc16 ext3 jbd mbcache
Apr 16 15:03:54 arch kernel: Pid: 3914, comm: wpa_supplicant Tainted: P           2.6.33-ARCH #1
Apr 16 15:03:54 arch kernel: Call Trace:
Apr 16 15:03:54 arch kernel: [<ffffffff81052a08>] warn_slowpath_common+0x78/0xb0
Apr 16 15:03:54 arch kernel: [<ffffffff81052a4f>] warn_slowpath_null+0xf/0x20
Apr 16 15:03:54 arch kernel: [<ffffffff81059682>] local_bh_enable_ip+0x82/0xb0
Apr 16 15:03:54 arch kernel: [<ffffffff8135d42f>] _raw_spin_unlock_bh+0x1f/0x30
Apr 16 15:03:54 arch kernel: [<ffffffffa0e918ed>] ath_tx_node_cleanup+0x19d/0x1c0 [ath9k]
Apr 16 15:03:54 arch kernel: [<ffffffffa0e8c607>] ath9k_sta_notify+0x57/0xb0 [ath9k]
Apr 16 15:03:54 arch kernel: [<ffffffffa0e47bc4>] __sta_info_unlink+0x174/0x220 [mac80211]
Apr 16 15:03:54 arch kernel: [<ffffffffa0e47ca8>] sta_info_unlink+0x38/0x60 [mac80211]
Apr 16 15:03:54 arch kernel: [<ffffffffa0e4e639>] ieee80211_set_disassoc+0x1e9/0x290 [mac80211]
Apr 16 15:03:54 arch kernel: [<ffffffffa0e4ee89>] ieee80211_mgd_deauth+0x159/0x160 [mac80211]
Apr 16 15:03:54 arch kernel: [<ffffffff8104d5c7>] ? try_to_wake_up+0x257/0x390
Apr 16 15:03:54 arch kernel: [<ffffffffa0e55b69>] ieee80211_deauth+0x19/0x20 [mac80211]
Apr 16 15:03:54 arch kernel: [<ffffffffa0d906de>] __cfg80211_mlme_deauth+0xee/0x130 [cfg80211]
Apr 16 15:03:54 arch kernel: [<ffffffff8135baad>] ? __mutex_lock_slowpath+0x26d/0x370
Apr 16 15:03:54 arch kernel: [<ffffffffa0d94839>] __cfg80211_disconnect+0x159/0x1d0 [cfg80211]
Apr 16 15:03:54 arch kernel: [<ffffffffa0d96f9c>] cfg80211_wext_siwmlme+0x8c/0xa0 [cfg80211]
Apr 16 15:03:54 arch kernel: [<ffffffff8133e6b7>] ioctl_standard_iw_point+0x207/0x3a0
Apr 16 15:03:54 arch kernel: [<ffffffffa0d96f10>] ? cfg80211_wext_siwmlme+0x0/0xa0 [cfg80211]
Apr 16 15:03:54 arch kernel: [<ffffffff8133e850>] ? ioctl_standard_call+0x0/0xd0
Apr 16 15:03:54 arch kernel: [<ffffffff8133e8e9>] ioctl_standard_call+0x99/0xd0
Apr 16 15:03:54 arch kernel: [<ffffffff812b2660>] ? __dev_get_by_name+0xa0/0xc0
Apr 16 15:03:54 arch kernel: [<ffffffff8133dce7>] wext_ioctl_dispatch+0x1f7/0x210
Apr 16 15:03:54 arch kernel: [<ffffffff8133f330>] ? ioctl_private_call+0x0/0xa0
Apr 16 15:03:54 arch kernel: [<ffffffff8133de91>] wext_handle_ioctl+0x41/0x90
Apr 16 15:03:54 arch kernel: [<ffffffff8111cab2>] ? mem_cgroup_update_file_mapped+0x12/0xe0
Apr 16 15:03:54 arch kernel: [<ffffffff812b8299>] dev_ioctl+0x679/0x850
Apr 16 15:03:54 arch kernel: [<ffffffff810dc3d2>] ? unlock_page+0x22/0x30
Apr 16 15:03:54 arch kernel: [<ffffffff810f6d49>] ? __do_fault+0x479/0x5a0
Apr 16 15:03:54 arch kernel: [<ffffffff812a0522>] sock_ioctl+0xe2/0x290
Apr 16 15:03:54 arch kernel: [<ffffffff810f90de>] ? handle_mm_fault+0x19e/0xa30
Apr 16 15:03:54 arch kernel: [<ffffffff811324c8>] vfs_ioctl+0x38/0xd0
Apr 16 15:03:54 arch kernel: [<ffffffff81132670>] do_vfs_ioctl+0x80/0x560
Apr 16 15:03:54 arch kernel: [<ffffffff811d1276>] ? __up_read+0xa6/0xd0
Apr 16 15:03:54 arch kernel: [<ffffffff81077e09>] ? up_read+0x9/0x10
Apr 16 15:03:54 arch kernel: [<ffffffff81132bd1>] sys_ioctl+0x81/0xa0
Apr 16 15:03:54 arch kernel: [<ffffffff81009fc2>] system_call_fastpath+0x16/0x1b
Apr 16 15:03:54 arch kernel: ---[ end trace 5e124dd48895d861 ]---

Now from the kernel log, it seems that the freeze most of the time comes shortly after this, i.e. in the next minutes, but not always. While the crashes happen rather randomly, they seem to increase under heavily load: at one point, I could trigger the freeze by verifying a 25gig torrent in transmission, or by compiling a kernel. Next day, not anymore. But it never happened with 2.6.32 so far.

ath9k has always been buggy for me (unstable connection etc), so I like to think of that module somehow being the culprit here. Since I have to do some work and can't really afford having my machine lock up randomly, I am a bit reluctant with testing 2.6.33 atm. But next thing would be using ethernet and blacklist ath9k, I guess. Will see if there is some time to try it out the next days.

Any other ideas on how to further proceed with this? Someone experiencing similar problems?

P.S.: some more infos:

Graphics: Nvidia G105m
Wlan: Atheros AR928x
lspci
full kernel logs(1,8MB)
The above warning goes with a disconnect of wireless. Connection hickups happen with the old kernel too, though without the warning.

Last edited by hokasch (2010-04-23 10:52:36)

maxol · 2010-04-20 19:04:58

I have exactly the same symptoms although I have no wireless connection.

archlinux 64 bit kernel 2.6.33-ARCH

Here's my lspci http://pastebin.org/162642

oldmerovingian · 2010-04-20 19:18:35

We all seem to be having this issue with ath9k. I have experienced it, and a few others on a few different posts. I am trying to find out if it is ath9k by disabling it in modules and using an ethernet cord to connect to the internet.

Another member said it started happening after a dhcpcd update, but mine happnened before that. I will report back if I can get the system to panic without ath9k.

Ultraman · 2010-04-20 19:27:24

This interests me as I recently experienced such a hard lockup on my Sony Vaio Y.
I'm not on it right now, but some specs:
- Intel Core 2 Duo SU7300 (1.3GHz)
- 4GB DDR3 (checks out after running a night of memtest86)
- Intel 4 Series chipset, I believe it's a GS45 or GM45, with X4500MHD video
- Intel HDA with Realtek ALC275 codec
- Atheros Gigabit Ethernet (atl1e)
- Atheros AR9285 Wifi-b/g/n (ath9k)

Running up-to-date Arch Linux x86_64. I've only had this for a week now, so I've only ran stock 2.6.33 on this.
Happened while playing some music via Youtube in a tab and browsing in several other tabs.
Happened to me also while playing a stream with mplayer and browsing at the same time (multiple tabs, big fat chance something in there used the Flash plugin).
So far I've not been able to replicate it without the use of a browser. But watching a YouTube 720p HD video seems to work fine when watching it actively. I've only had crashes when the Flash seems to be in the background away from my focus.
Both Chromium and Firefox have been used in my case.
I'm hoping to avoid any crashes, but if another happens to pop up, I'll report.

Last thing my log files mentioned was increasing the delta of the hpet to 22500ns (iirc)

Last edited by Ultraman (2010-04-20 19:28:26)

hokasch · 2010-04-20 20:36:34

OK, this evening I did not experience any lock ups with 2.6.33-ck and a) ath9k unloaded or b) today's compat-wireless ath9k module.
Not long enough to draw any conclusions yet, but if it got fixed with newer wireless-builds I'll be more than happy with that.
*knocks on wood*

@maxol
hmm, our systems seem to have completely different hardware, besides nvidia graphics.. does downgrading the kernel help?

@oldmerovingian
oh alright, I've seen a lot of moaning about ath9k stability, but didn't really find reports about it smashing the whole system. for me, this certainly has not been a big problem before 2.6.33.

@ultraman
flash's general annoyance level always makes it an easy suspect... although I haven't yet seen it tear down everything. firefox is hard to rule out here, since it is running all the time. I'll pay more attention to what's on the screen next time it crashes.

oldmerovingian · 2010-04-20 20:37:46

Ultraman wrote:

This interests me as I recently experienced such a hard lockup on my Sony Vaio Y.
I'm not on it right now, but some specs:
- Intel Core 2 Duo SU7300 (1.3GHz)
- 4GB DDR3 (checks out after running a night of memtest86)
- Intel 4 Series chipset, I believe it's a GS45 or GM45, with X4500MHD video
- Intel HDA with Realtek ALC275 codec
- Atheros Gigabit Ethernet (atl1e)
- Atheros AR9285 Wifi-b/g/n (ath9k)
Running up-to-date Arch Linux x86_64. I've only had this for a week now, so I've only ran stock 2.6.33 on this.
Happened while playing some music via Youtube in a tab and browsing in several other tabs.
Happened to me also while playing a stream with mplayer and browsing at the same time (multiple tabs, big fat chance something in there used the Flash plugin).
So far I've not been able to replicate it without the use of a browser. But watching a YouTube 720p HD video seems to work fine when watching it actively. I've only had crashes when the Flash seems to be in the background away from my focus.
Both Chromium and Firefox have been used in my case.
I'm hoping to avoid any crashes, but if another happens to pop up, I'll report.
Last thing my log files mentioned was increasing the delta of the hpet to 22500ns (iirc)

I also have a Sony Vaio, but the specs are a little different. My computer had panics on the 2.6.32 kernel as well, though they seemed less frequent. I did not have a chance to try 2.6.31.

When it fist started happening I thought it might have been flash since each time I had flash running. I was able to get it to crash with flash uninstalled. I also thought it may have been related to browser activity but I was able to get it to panic while just using Xchat. It seems like we are all having the same problem, and it seems to be the ath9k module.

Giacomo Ritucci · 2010-04-21 15:13:37

Same problem here:

ath9k: Two wiphys trying to scan at the same time
wlan0: direct probe to AP 00:25:9c:92:5a:13 (try 1)
wlan0: direct probe responded
wlan0: authenticate with AP 00:25:9c:92:5a:13 (try 1)
wlan0: authenticated
wlan0: associate with AP 00:25:9c:92:5a:13 (try 1)
wlan0: RX AssocResp from 00:25:9c:92:5a:13 (capab=0x431 status=0 aid=1)
wlan0: associated
padlock: VIA PadLock not detected.
composite sync not supported
composite sync not supported
composite sync not supported
composite sync not supported
No probe response from AP 00:25:9c:92:5a:13 after 500ms, disconnecting.
------------[ cut here ]------------
WARNING: at kernel/softirq.c:143 local_bh_enable_ip+0x68/0xa0()
Hardware name: 1005HA
Modules linked in: aes_i586 aes_generic ext2 ntfs nls_cp437 vfat fat snd_hda_codec_realtek arc4 snd_seq_dummy ecb snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_hda_intel ath9k ath9k_common snd_pcm_oss snd_hda_codec uvcvideo mac80211 snd_hwdep snd_mixer_oss videodev v4l1_compat ath9k_hw ath i915 snd_pcm cpufreq_ondemand drm_kms_helper joydev snd_timer cfg80211 drm i2c_algo_bit snd eeepc_laptop sparse_keymap uhci_hcd rfkill i2c_core soundcore intel_agp ehci_hcd pci_hotplug video snd_page_alloc output battery ac led_class thermal button acpi_cpufreq pcspkr agpgart usbcore evdev iTCO_wdt freq_table iTCO_vendor_support psmouse serio_raw atl1c sg processor rtc_cmos rtc_core rtc_lib ext4 mbcache jbd2 crc16 sd_mod ahci libata scsi_mod
Pid: 2215, comm: phy0 Not tainted 2.6.33-ARCH #1
Call Trace:
 [<c104314d>] warn_slowpath_common+0x6d/0xa0
 [<c1049c08>] ? local_bh_enable_ip+0x68/0xa0
 [<c1049c08>] ? local_bh_enable_ip+0x68/0xa0
 [<c1043195>] warn_slowpath_null+0x15/0x20
 [<c1049c08>] local_bh_enable_ip+0x68/0xa0
 [<c12d4248>] _raw_spin_unlock_bh+0x18/0x20
 [<f80d8bb7>] ath_tx_node_cleanup+0x147/0x170 [ath9k]
 [<f80d42c6>] ath9k_sta_notify+0x46/0xb0 [ath9k]
 [<f8a438e2>] __sta_info_unlink+0x132/0x1c0 [mac80211]
 [<f80d4280>] ? ath9k_sta_notify+0x0/0xb0 [ath9k]
 [<f8a4399e>] sta_info_unlink+0x2e/0x50 [mac80211]
 [<f8a4977e>] ieee80211_set_disassoc+0x19e/0x240 [mac80211]
 [<f8a4d2db>] ieee80211_sta_work+0x104b/0x1120 [mac80211]
 [<c12d1832>] ? schedule+0x292/0x9c0
 [<c105b993>] worker_thread+0x113/0x250
 [<f8a4c290>] ? ieee80211_sta_work+0x0/0x1120 [mac80211]
 [<c105fc60>] ? autoremove_wake_function+0x0/0x40
 [<c105b880>] ? worker_thread+0x0/0x250
 [<c105f83c>] kthread+0x6c/0x80
 [<c105f7d0>] ? kthread+0x0/0x80
 [<c1003e3e>] kernel_thread_helper+0x6/0x18
---[ end trace 8541dc21be857306 ]---

I'm using a eee 1005ha nettop.

hokasch · 2010-04-21 22:36:40

Well, not declaring success on this - I know from experience it will then instantly break again. But if you experience these symptoms, definitely try compat-wireless (04/20, in case of regressions).

The linux-wireless mailing list is way over my head, I couldn't identify anything related to this problem - so I will just assume this helped:

PATCH 10/10 wrote:

ath9k_htc: Fix sparse endian warnings
This patch fixes a bunch of endian issues that
were exposed by sparse. It's a miracle that the driver
worked at all till now.
The Lord be praised.

Indeed.

EDIT: OK, two days later I am more confident. Adding Solved...

Last edited by hokasch (2010-04-23 10:51:23)

kokoko3k · 2010-04-24 17:53:49

I haven't understood well.
Did you solved the problem by using the patch on linux wireless mailing list or by using compat-wireless?
Just in case, d'you know if the patch has gone to mainline and in what version will be shipped?

Sorry for the silly question.

hokasch · 2010-04-24 18:01:21

The problem was easily fixed for me by installing compat-wireless, although it didn't help for others - see the ath9k kernel panic thread.

No idea what this patch actually means, just stumbled about it when looking through the mailing list for reports about ath9k crashes and thought it sounded promising. Maybe I should report my experience there, but it seems like so little information/too much randomness to really be helpful. Well, if it breaks again in later revisions I'll write an email..

kokoko3k · 2010-04-24 21:12:47

understood, thanks for clarifying.

mariusz · 2010-04-24 21:19:32

I have the same problem. After upgrade kernel to 2.6.33 I have hard system freezes. Bellow I pasted some of the kernel.log messages.

Apr 19 23:56:51 asus kernel: ------------[ cut here ]------------
Apr 19 23:56:51 asus kernel: WARNING: at kernel/softirq.c:143 local_bh_enable_ip+0x68/0xa0()
Apr 19 23:56:51 asus kernel: Hardware name: K50IN                
Apr 19 23:56:51 asus kernel: Modules linked in: rfcomm ch341 usbserial ipv6 aes_i586 aes_generic sco bridge stp llc bnep l2cap bluetooth cpufreq_ondemand snd_hda_codec_realtek arc4 snd_seq_dummy ecb snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device ath9k ath9k_common snd_hda_intel mac80211 uvcvideo snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss video videodev snd_pcm ath9k_hw ath snd_timer v4l1_compat output asus_laptop ac battery button thermal wmi cfg80211 rfkill led_class snd soundcore snd_page_alloc nvidia(P) agpgart ohci_hcd ehci_hcd i2c_nforce2 i2c_core acpi_cpufreq usbcore r8169 mii shpchp pci_hotplug evdev sg psmouse serio_raw pcspkr freq_table processor rtc_cmos rtc_core rtc_lib ext4 mbcache jbd2 crc16 sr_mod sd_mod cdrom ahci libata scsi_mod
Apr 19 23:56:51 asus kernel: Pid: 4275, comm: wpa_supplicant Tainted: P           2.6.33-ARCH #1
Apr 19 23:56:51 asus kernel: Call Trace:
Apr 19 23:56:51 asus kernel: [<c104314d>] warn_slowpath_common+0x6d/0xa0
Apr 19 23:56:51 asus kernel: [<c1049c08>] ? local_bh_enable_ip+0x68/0xa0
Apr 19 23:56:51 asus kernel: [<c1049c08>] ? local_bh_enable_ip+0x68/0xa0
Apr 19 23:56:51 asus kernel: [<c1043195>] warn_slowpath_null+0x15/0x20
Apr 19 23:56:51 asus kernel: [<c1049c08>] local_bh_enable_ip+0x68/0xa0
Apr 19 23:56:51 asus kernel: [<c12d4248>] _raw_spin_unlock_bh+0x18/0x20
Apr 19 23:56:51 asus kernel: [<fa59ebb7>] ath_tx_node_cleanup+0x147/0x170 [ath9k]
Apr 19 23:56:51 asus kernel: [<fa59a2c6>] ath9k_sta_notify+0x46/0xb0 [ath9k]
Apr 19 23:56:51 asus kernel: [<fa4968e2>] __sta_info_unlink+0x132/0x1c0 [mac80211]
Apr 19 23:56:51 asus kernel: [<fa59a280>] ? ath9k_sta_notify+0x0/0xb0 [ath9k]
Apr 19 23:56:51 asus kernel: [<fa49699e>] sta_info_unlink+0x2e/0x50 [mac80211]
Apr 19 23:56:51 asus kernel: [<fa49c77e>] ieee80211_set_disassoc+0x19e/0x240 [mac80211]
Apr 19 23:56:51 asus kernel: [<fa49cf6e>] ieee80211_mgd_deauth+0x12e/0x140 [mac80211]
Apr 19 23:56:51 asus kernel: [<fa4a3554>] ieee80211_deauth+0x14/0x20 [mac80211]
Apr 20 09:23:09 asus kernel: [<fa1ddef8>] __cfg80211_mlme_deauth+0xd8/0x100 [cfg80211]
Apr 20 09:23:09 asus kernel: [<fa1e1705>] __cfg80211_disconnect+0x145/0x1b0 [cfg80211]
Apr 20 09:23:09 asus kernel: [<fa1e3b71>] cfg80211_wext_siwmlme+0x81/0xa0 [cfg80211]
Apr 20 09:23:09 asus kernel: [<c12bb059>] ioctl_standard_call+0x149/0x390
Apr 20 09:23:09 asus kernel: [<fa1e3af0>] ? cfg80211_wext_siwmlme+0x0/0xa0 [cfg80211]
Apr 20 09:23:09 asus kernel: [<c1241415>] ? __dev_get_by_name+0x85/0xb0
Apr 20 09:23:09 asus kernel: [<c12bb4bd>] wext_handle_ioctl+0x21d/0x240
Apr 20 09:23:09 asus kernel: [<fa1e3af0>] ? cfg80211_wext_siwmlme+0x0/0xa0 [cfg80211]
Apr 20 09:23:09 asus kernel: [<c12467c9>] dev_ioctl+0x629/0x740
Apr 20 09:23:09 asus kernel: [<c10bc959>] ? find_get_page+0x29/0xe0
Apr 20 09:23:09 asus kernel: [<c10be096>] ? filemap_fault+0x86/0x3e0
Apr 20 09:23:09 asus kernel: [<c1232873>] sock_ioctl+0x1c3/0x260
Apr 20 09:23:09 asus kernel: [<c1102bad>] vfs_ioctl+0x2d/0xb0
Apr 20 09:23:09 asus kernel: [<c12326b0>] ? sock_ioctl+0x0/0x260
Apr 20 09:23:09 asus kernel: [<c1102d7c>] do_vfs_ioctl+0x6c/0x580
Apr 20 09:23:09 asus kernel: [<c10d5783>] ? handle_mm_fault+0xe3/0x7b0
Apr 20 09:23:09 asus kernel: [<c104782f>] ? do_setitimer+0x15f/0x200
Apr 20 09:23:09 asus kernel: [<c1026cab>] ? do_page_fault+0x16b/0x330
Apr 20 09:23:09 asus kernel: [<c11032ef>] sys_ioctl+0x5f/0x80
Apr 20 09:23:09 asus kernel: [<c100389f>] sysenter_do_call+0x12/0x28
Apr 20 09:23:09 asus kernel: ---[ end trace b48613299e51f5d3 ]---

Apr 20 16:54:58 asus kernel: ------------[ cut here ]------------
Apr 20 16:54:58 asus kernel: WARNING: at kernel/softirq.c:143 local_bh_enable_ip+0x68/0xa0()
Apr 20 16:54:58 asus kernel: Hardware name: K50IN                
Apr 20 16:54:58 asus kernel: Modules linked in: cpufreq_powersave ipv6 aes_i586 aes_generic sco bridge stp llc bnep l2cap bluetooth cpufreq_ondemand snd_hda_codec_realtek snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq arc4 snd_seq_device ecb snd_pcm_oss snd_mixer_oss snd_hda_intel ath9k ath9k_common snd_hda_codec mac80211 ath9k_hw video snd_hwdep snd_pcm snd_timer uvcvideo videodev ath snd v4l1_compat output asus_laptop wmi ac battery thermal button cfg80211 rfkill led_class soundcore snd_page_alloc acpi_cpufreq i2c_nforce2 nvidia(P) agpgart i2c_core r8169 mii ohci_hcd ehci_hcd usbcore shpchp freq_table pci_hotplug sg evdev psmouse processor pcspkr serio_raw rtc_cmos rtc_core rtc_lib ext4 mbcache jbd2 crc16 sr_mod cdrom sd_mod ahci libata scsi_mod
Apr 20 16:54:58 asus kernel: Pid: 10100, comm: ifconfig Tainted: P           2.6.33-ARCH #1
Apr 20 16:54:58 asus kernel: Call Trace:
Apr 20 16:54:58 asus kernel: [<c104314d>] warn_slowpath_common+0x6d/0xa0
Apr 20 16:54:58 asus kernel: [<c1049c08>] ? local_bh_enable_ip+0x68/0xa0
Apr 20 16:54:58 asus kernel: [<c1049c08>] ? local_bh_enable_ip+0x68/0xa0
Apr 20 16:54:58 asus kernel: [<c1043195>] warn_slowpath_null+0x15/0x20
Apr 20 16:54:58 asus kernel: [<c1049c08>] local_bh_enable_ip+0x68/0xa0
Apr 20 16:54:58 asus kernel: [<c12d4248>] _raw_spin_unlock_bh+0x18/0x20
Apr 20 16:54:58 asus kernel: [<fa4cbbb7>] ath_tx_node_cleanup+0x147/0x170 [ath9k]
Apr 20 16:54:58 asus kernel: [<fa4c72c6>] ath9k_sta_notify+0x46/0xb0 [ath9k]
Apr 20 16:54:58 asus kernel: [<fa4328e2>] __sta_info_unlink+0x132/0x1c0 [mac80211]
Apr 20 16:54:58 asus kernel: [<fa4c7280>] ? ath9k_sta_notify+0x0/0xb0 [ath9k]
Apr 20 16:54:58 asus kernel: [<fa43299e>] sta_info_unlink+0x2e/0x50 [mac80211]
Apr 20 16:54:58 asus kernel: [<fa43877e>] ieee80211_set_disassoc+0x19e/0x240 [mac80211]
Apr 20 16:54:58 asus kernel: [<fa438f6e>] ieee80211_mgd_deauth+0x12e/0x140 [mac80211]
Apr 20 16:54:58 asus kernel: [<c103ebfb>] ? default_wake_function+0xb/0x10
Apr 20 16:54:58 asus kernel: [<c105fc7b>] ? autoremove_wake_function+0x1b/0x40
Apr 20 16:54:58 asus kernel: [<fa43f554>] ieee80211_deauth+0x14/0x20 [mac80211]
Apr 20 16:54:58 asus kernel: [<fa1f8ef8>] __cfg80211_mlme_deauth+0xd8/0x100 [cfg80211]
Apr 20 16:54:58 asus kernel: [<fa1fc705>] __cfg80211_disconnect+0x145/0x1b0 [cfg80211]
Apr 20 16:54:58 asus kernel: [<fa1ea22b>] cfg80211_netdev_notifier_call+0xfb/0x3e0 [cfg80211]
Apr 20 16:54:58 asus kernel: [<c1064ff3>] notifier_call_chain+0x43/0x60
Apr 20 16:54:58 asus kernel: [<c10650ba>] raw_notifier_call_chain+0x1a/0x20
Apr 20 16:54:58 asus kernel: [<c1244811>] call_netdevice_notifiers+0x11/0x20
Apr 20 16:54:58 asus kernel: [<c12452b4>] dev_close+0x44/0xb0
Apr 20 16:54:58 asus kernel: [<c12d4248>] ? _raw_spin_unlock_bh+0x18/0x20
Apr 20 16:54:58 asus kernel: [<c12424da>] ? dev_set_rx_mode+0x2a/0x40
Apr 20 16:54:58 asus kernel: [<c1244b80>] dev_change_flags+0x80/0x190
Apr 20 16:54:58 asus kernel: [<c12934a5>] devinet_ioctl+0x6e5/0x770
Apr 20 16:54:58 asus kernel: [<c124645b>] ? dev_ioctl+0x2bb/0x740
Apr 20 16:54:58 asus kernel: [<c10bc959>] ? find_get_page+0x29/0xe0
Apr 20 16:54:58 asus kernel: [<c129479d>] inet_ioctl+0x8d/0xb0
Apr 20 16:54:58 asus kernel: [<c1232718>] sock_ioctl+0x68/0x260
Apr 20 16:54:58 asus kernel: [<c10fd7f0>] ? path_put+0x20/0x30
Apr 20 16:54:58 asus kernel: [<c1102bad>] vfs_ioctl+0x2d/0xb0
Apr 20 16:54:58 asus kernel: [<c12326b0>] ? sock_ioctl+0x0/0x260
Apr 20 16:54:58 asus kernel: [<c1102d7c>] do_vfs_ioctl+0x6c/0x580
Apr 20 16:54:58 asus kernel: [<c10d5783>] ? handle_mm_fault+0xe3/0x7b0
Apr 20 16:54:58 asus kernel: [<c1026cab>] ? do_page_fault+0x16b/0x330
Apr 20 16:54:58 asus kernel: [<c11032ef>] sys_ioctl+0x5f/0x80
Apr 20 16:54:58 asus kernel: [<c100389f>] sysenter_do_call+0x12/0x28
Apr 20 16:54:58 asus kernel: ---[ end trace 059c2176ce1dc677 ]---

Apr 22 14:51:53 asus kernel: ------------[ cut here ]------------
Apr 22 14:51:53 asus kernel: WARNING: at drivers/usb/serial/usb-serial.c:410 serial_unthrottle+0x79/0x80 [usbserial]()
Apr 22 14:51:53 asus kernel: Hardware name: K50IN                
Apr 22 14:51:53 asus kernel: Modules linked in: usbhid hid ftdi_sio ch341 usbserial ipv6 sco bridge stp llc bnep l2cap bluetooth cpufreq_ondemand snd_hda_codec_realtek uvcvideo videodev v4l1_compat arc4 ecb snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss ath9k ath9k_common snd_hda_intel snd_mixer_oss mac80211 snd_hda_codec ath9k_hw ath snd_hwdep snd_pcm snd_timer ohci_hcd cfg80211 video snd soundcore output rfkill snd_page_alloc ehci_hcd ac battery asus_laptop led_class nvidia(P) wmi agpgart acpi_cpufreq i2c_nforce2 button thermal freq_table i2c_core usbcore psmouse sg r8169 mii evdev pcspkr serio_raw shpchp pci_hotplug processor rtc_cmos rtc_core rtc_lib ext4 mbcache jbd2 crc16 sr_mod sd_mod cdrom ahci libata scsi_mod
Apr 22 14:51:53 asus kernel: Pid: 7906, comm: gtkterm Tainted: P           2.6.33-ARCH #1
Apr 22 14:51:53 asus kernel: Call Trace:
Apr 22 14:51:53 asus kernel: [<c104314d>] warn_slowpath_common+0x6d/0xa0
Apr 22 14:51:53 asus kernel: [<f8900349>] ? serial_unthrottle+0x79/0x80 [usbserial]
Apr 22 14:51:53 asus kernel: [<f8900349>] ? serial_unthrottle+0x79/0x80 [usbserial]
Apr 22 14:51:53 asus kernel: [<c1043195>] warn_slowpath_null+0x15/0x20
Apr 22 14:51:53 asus kernel: [<f8900349>] serial_unthrottle+0x79/0x80 [usbserial]
Apr 22 14:51:53 asus kernel: [<c11f17d6>] tty_unthrottle+0x36/0x50
Apr 22 14:51:53 asus kernel: [<c11efe17>] reset_buffer_flags+0xc7/0x100
Apr 22 14:51:53 asus kernel: [<c11efe66>] n_tty_flush_buffer+0x16/0x80
Apr 22 14:51:53 asus kernel: [<c11f3507>] tty_ldisc_flush+0x27/0x40
Apr 22 14:51:53 asus kernel: [<c11f3f09>] tty_port_close_start+0xd9/0x1a0
Apr 22 14:51:53 asus kernel: [<c10e89da>] ? __free_slab+0x8a/0x100
Apr 22 14:51:53 asus kernel: [<c11f43d6>] tty_port_close+0x16/0x50
Apr 22 14:51:53 asus kernel: [<f890074a>] serial_close+0x2a/0x70 [usbserial]
Apr 22 14:51:53 asus kernel: [<c11eade9>] ? tty_fasync+0x59/0x150
Apr 22 14:51:53 asus kernel: [<c11ed5cc>] tty_release+0x12c/0x5e0
Apr 22 14:51:53 asus kernel: [<c1109044>] ? destroy_inode+0x34/0x40
Apr 22 14:51:53 asus kernel: [<c11057f9>] ? __d_free+0x29/0x40
Apr 22 14:51:53 asus kernel: [<c11057f9>] ? __d_free+0x29/0x40
Apr 22 14:51:53 asus kernel: [<c10f62ce>] __fput+0xce/0x1d0
Apr 22 14:51:53 asus kernel: [<c10f63e5>] fput+0x15/0x20
Apr 22 14:51:53 asus kernel: [<c10f2ec7>] filp_close+0x47/0x70
Apr 22 14:51:53 asus kernel: [<c1045463>] put_files_struct+0x63/0xb0
Apr 22 14:51:53 asus kernel: [<c10454f2>] exit_files+0x42/0x60
Apr 22 14:51:53 asus kernel: [<c1046d16>] do_exit+0x136/0x740
Apr 22 14:51:53 asus kernel: [<c105703d>] ? dequeue_signal+0x2d/0x170
Apr 22 14:51:53 asus kernel: [<c1047359>] do_group_exit+0x39/0xa0
Apr 22 14:51:53 asus kernel: [<c1056c07>] ? do_signal_stop+0x87/0x170
Apr 22 14:51:53 asus kernel: [<c1057605>] get_signal_to_deliver+0x255/0x490
Apr 22 14:51:53 asus kernel: [<c1002d89>] do_signal+0x69/0xa60
Apr 22 14:51:53 asus kernel: [<c10f4d3c>] ? do_sync_read+0x9c/0xd0
Apr 22 14:51:53 asus kernel: [<c115a6af>] ? security_file_permission+0xf/0x20
Apr 22 14:51:53 asus kernel: [<c10f4dcd>] ? rw_verify_area+0x5d/0xd0
Apr 22 14:51:53 asus kernel: [<c1069d85>] ? ktime_get_ts+0xd5/0x100
Apr 22 14:51:53 asus kernel: [<c10037dd>] do_notify_resume+0x5d/0x80
Apr 22 14:51:53 asus kernel: [<c12d4a70>] work_notifysig+0x13/0x1b
Apr 22 14:51:53 asus kernel: ---[ end trace d8aa40ac30bfae52 ]---

markc · 2010-05-11 07:15:04

I see this is marked as solved for the OP but I still get non-random total lockups about 5 minutes after starting sshfs which uses FUSE, so I am presuming in my case it's because of that kernel module (like I say, a total lockup so it must be kernel related). Toshiba core duo lappie running x86_64 from testing and kdemod.

Nexx · 2010-05-14 00:48:42

I'm getting hard freezes when enabling 802.11n on my ath9k AP. Under 802.11g it's *mostly* stable, but under 802.11n it usually freezes almost instantly. I'm using the 3rd May compat-wireless. These issues seem to have started since the change from GCC 4.4 to 4.5. Before then the AP worked solidly at 802.11n or g. Wireless n speeds weren't great, but 802.11g was always solid at 54mbps.

oldmerovingian · 2010-05-15 01:21:17

Nexx wrote:

I'm getting hard freezes when enabling 802.11n on my ath9k AP. Under 802.11g it's *mostly* stable, but under 802.11n it usually freezes almost instantly. I'm using the 3rd May compat-wireless. These issues seem to have started since the change from GCC 4.4 to 4.5. Before then the AP worked solidly at 802.11n or g. Wireless n speeds weren't great, but 802.11g was always solid at 54mbps.

I have never used compat wireless. Have you tried removing it to see if the freeze persists?

Nexx · 2010-05-16 01:01:35

The freezes happen with both 802.11g and n without compat-wireless. Currently I've configured hostapd to only run at g speeds and that seems stable enough so far, but the moment I configure it to use 802.11n and then connect a client the entire machine freezes. The machine is headless and no kernel output is logged from the crash.

oldmerovingian · 2010-05-17 00:56:14

Nexx wrote:

The freezes happen with both 802.11g and n without compat-wireless. Currently I've configured hostapd to only run at g speeds and that seems stable enough so far, but the moment I configure it to use 802.11n and then connect a client the entire machine freezes. The machine is headless and no kernel output is logged from the crash.

Hmm...That is odd. Every other post I have read in which the crashes were related to the ath9k module have been resolved with the recent kernel upgrade. I have been using n speeds for over a month now with no freezes. I know that is not much of a help, but I am not sure what else to say. Sorry.

Nexx · 2010-05-17 14:04:59

Just installed the 2.6.34 kernel from testing, 802.11n doesn't seem to hard-lock the machine any more, but my windows client can barely manage 200KB/sec when it's enabled.
Under 802.11g it manages 2.5-3MB/sec and maintains a full 54mbps lock to the AP. 802.11n reports varying speeds from 74-130mbps but like I said, the actual speed is worse than 802.11g.

Just to clarify, the ath9k module is powering a D-Link DWA-556 wireless NIC as an access point with hostapd, -not- a client.

Regardless, the crashing has stopped, so problem solved

Keep up the good work devs!

Arch Linux

#1 2010-04-20 12:54:50

[Solved] Hard freezes with kernel 2.6.33 - possibly ath9k?

#2 2010-04-20 19:04:58

Re: [Solved] Hard freezes with kernel 2.6.33 - possibly ath9k?

#3 2010-04-20 19:18:35

Re: [Solved] Hard freezes with kernel 2.6.33 - possibly ath9k?

#4 2010-04-20 19:27:24

Re: [Solved] Hard freezes with kernel 2.6.33 - possibly ath9k?

#5 2010-04-20 20:36:34

Re: [Solved] Hard freezes with kernel 2.6.33 - possibly ath9k?

#6 2010-04-20 20:37:46

Re: [Solved] Hard freezes with kernel 2.6.33 - possibly ath9k?

#7 2010-04-21 15:13:37

Re: [Solved] Hard freezes with kernel 2.6.33 - possibly ath9k?

#8 2010-04-21 22:36:40

Re: [Solved] Hard freezes with kernel 2.6.33 - possibly ath9k?

#9 2010-04-24 17:53:49

Re: [Solved] Hard freezes with kernel 2.6.33 - possibly ath9k?

#10 2010-04-24 18:01:21

Re: [Solved] Hard freezes with kernel 2.6.33 - possibly ath9k?

#11 2010-04-24 21:12:47

Re: [Solved] Hard freezes with kernel 2.6.33 - possibly ath9k?

#12 2010-04-24 21:19:32

Re: [Solved] Hard freezes with kernel 2.6.33 - possibly ath9k?

#13 2010-05-11 07:15:04

Re: [Solved] Hard freezes with kernel 2.6.33 - possibly ath9k?

#14 2010-05-14 00:48:42

Re: [Solved] Hard freezes with kernel 2.6.33 - possibly ath9k?

#15 2010-05-15 01:21:17

Re: [Solved] Hard freezes with kernel 2.6.33 - possibly ath9k?

#16 2010-05-16 01:01:35

Re: [Solved] Hard freezes with kernel 2.6.33 - possibly ath9k?

#17 2010-05-17 00:56:14

Re: [Solved] Hard freezes with kernel 2.6.33 - possibly ath9k?

#18 2010-05-17 14:04:59

Re: [Solved] Hard freezes with kernel 2.6.33 - possibly ath9k?

Board footer