Bug 587727
| Summary: | kerneloops after wireless connection established | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | John W. Linville <linville> |
| Component: | kernel | Assignee: | John W. Linville <linville> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 12 | CC: | anton, dmaxel, dougsland, gansalmon, itamar, jonathan, kernel-maint, misc, nospam |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | kernel-2.6.32.12-115.fc12 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 585072 | Environment: | |
| Last Closed: | 2010-06-14 21:09:33 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 585072 | ||
| Bug Blocks: | |||
|
Description
John W. Linville
2010-04-30 17:44:02 UTC
kernel-2.6.32.12-115.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/kernel-2.6.32.12-115.fc12 kernel-2.6.32.12-115.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update kernel'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/kernel-2.6.32.12-115.fc12 I think my problem is more accurately described by this bug:https://bugzilla.redhat.com/show_bug.cgi?id=544497 but that bug has been closed and I was referred to this bug. I am using fedora 12 on an atom based system that uses an Atheros AR9285 wireless card (so ath9k driver) and trying to configure as an access point using hostapd 0.6.9-7 (also have tried 0.7.2). I've also tried updating the ath9k driver using compat-wireless with no help. I've tried this updated kernel (kernel-2.6.32.12-115.fc12.i686), the good news is that I don't get the kernel crash report in the messages log. The bad news is that I still loose wireless connectivity (just no reports in the log) or the system just totally locks up and becomes unresponsive. Here's what I get in the main-line (kernel 2.6.32.11-99.fc12.i686): May 6 11:10:25 localhost hostapd: wlan0: STA 00:18:f3:49:f5:d2 IEEE 802.11: deauthenticated due to local deauth request May 6 11:10:25 localhost kernel: ------------[ cut here ]------------ May 6 11:10:25 localhost kernel: WARNING: at kernel/softirq.c:143 _local_bh_enable_ip+0x3b/0x77() May 6 11:10:25 localhost kernel: Hardware name: nT-330i May 6 11:10:25 localhost kernel: Modules linked in: aes_i586 aes_generic ipt_MASQUERADE iptable_nat nf_nat ip6t_REJECT nf_conntrack_ipv6 ip6table_filter ip6_tables ipv6 snd_hda_codec_nvhdmi snd_hda_codec_realtek arc4 snd_hda_intel ecb snd_hda_codec snd_hwdep ath9k snd_seq snd_seq_device mac80211 snd_pcm snd_timer snd ath soundcore cfg80211 wmi i2c_nforce2 serio_raw snd_page_alloc atl1c rfkill usb_storage nouveau ttm drm_kms_helper drm i2c_algo_bit i2c_core [last unloaded: scsi_wait_scan] May 6 11:10:25 localhost kernel: Pid: 1281, comm: hostapd Not tainted 2.6.32.11-99.fc12.i686 #1 May 6 11:10:25 localhost kernel: Call Trace: May 6 11:10:25 localhost kernel: [<c043a479>] warn_slowpath_common+0x6a/0x81 May 6 11:10:25 localhost kernel: [<c0440da3>] ? _local_bh_enable_ip+0x3b/0x77 May 6 11:10:25 localhost kernel: [<c043a4a2>] warn_slowpath_null+0x12/0x15 May 6 11:10:25 localhost kernel: [<c0440da3>] _local_bh_enable_ip+0x3b/0x77 May 6 11:10:25 localhost kernel: [<c0440dec>] local_bh_enable_ip+0xd/0xf May 6 11:10:25 localhost kernel: [<c079383b>] _spin_unlock_bh+0x13/0x15 May 6 11:10:25 localhost kernel: [<fb10254e>] ath_tx_node_cleanup+0xf3/0x10b [ath9k] May 6 11:10:25 localhost kernel: [<c041fe00>] ? native_irq_disable+0x8/0xb May 6 11:10:25 localhost kernel: [<c058917b>] ? selinux_netlink_recv+0x58/0x73 May 6 11:10:25 localhost kernel: [<fb0fe9d2>] ath9k_sta_notify+0x79/0x7d [ath9k] May 6 11:10:25 localhost kernel: [<fb07b345>] __sta_info_unlink+0x11e/0x16e [mac80211] May 6 11:10:25 localhost kernel: [<fb0fe959>] ? ath9k_sta_notify+0x0/0x7d [ath9k] May 6 11:10:25 localhost kernel: [<fb07b3bd>] sta_info_unlink+0x28/0x36 [mac80211] May 6 11:10:25 localhost kernel: [<fb08636d>] ? ieee80211_del_station+0x0/0x52 [mac80211] May 6 11:10:25 localhost kernel: [<fb0863a6>] ieee80211_del_station+0x39/0x52 [mac80211] May 6 11:10:25 localhost kernel: [<fab877c8>] nl80211_del_station+0x70/0x92 [cfg80211] May 6 11:10:25 localhost kernel: [<c0722978>] genl_rcv_msg+0x1a7/0x1c4 May 6 11:10:25 localhost kernel: [<c07227d1>] ? genl_rcv_msg+0x0/0x1c4 May 6 11:10:25 localhost kernel: [<c0721afe>] netlink_rcv_skb+0x35/0x7b May 6 11:10:25 localhost kernel: [<c07227ca>] genl_rcv+0x20/0x27 May 6 11:10:25 localhost kernel: [<c0721920>] netlink_unicast+0xec/0x149 May 6 11:10:25 localhost kernel: [<c0721fd3>] netlink_sendmsg+0x21b/0x228 May 6 11:10:25 localhost kernel: [<c06fde28>] __sock_sendmsg+0x4a/0x53 May 6 11:10:25 localhost kernel: [<c06fe4a1>] sock_sendmsg+0xbb/0xd1 May 6 11:10:25 localhost kernel: [<c06fe4a1>] ? sock_sendmsg+0xbb/0xd1 May 6 11:10:25 localhost kernel: [<c0454371>] ? autoremove_wake_function+0x0/0x34 May 6 11:10:25 localhost kernel: [<c05be4bf>] ? might_fault+0x1e/0x20 May 6 11:10:25 localhost kernel: [<c05be4f3>] ? copy_from_user+0x32/0x119 May 6 11:10:25 localhost kernel: [<c0706052>] ? verify_iovec+0x43/0x71 May 6 11:10:25 localhost kernel: [<c06fe643>] sys_sendmsg+0x18c/0x1f0 May 6 11:10:25 localhost kernel: [<c04870c3>] ? call_rcu_sched+0x12/0x14 May 6 11:10:25 localhost kernel: [<c04870d2>] ? call_rcu+0xd/0xf May 6 11:10:25 localhost kernel: [<c05bae57>] ? radix_tree_delete+0xe5/0x171 May 6 11:10:25 localhost kernel: [<c05020ef>] ? fsnotify_clear_marks_by_inode+0x21/0xa2 May 6 11:10:25 localhost kernel: [<c06fd79d>] ? sock_destroy_inode+0x15/0x17 May 6 11:10:25 localhost kernel: [<c04eae64>] ? destroy_inode+0x24/0x35 May 6 11:10:25 localhost kernel: [<c04e88d6>] ? __d_free+0x3d/0x40 May 6 11:10:25 localhost kernel: [<c04e8903>] ? d_free+0x2a/0x3c May 6 11:10:25 localhost kernel: [<c04ee3f0>] ? mntput_no_expire+0x1e/0xba May 6 11:10:25 localhost kernel: [<c06ff97b>] sys_socketcall+0x163/0x195 May 6 11:10:25 localhost kernel: [<c040abae>] ? syscall_trace_leave+0xaa/0xbd May 6 11:10:25 localhost kernel: [<c040365c>] syscall_call+0x7/0xb May 6 11:10:25 localhost kernel: ---[ end trace fb82fbc53375f354 ]--- May 6 11:10:31 localhost hostapd: wlan0: STA 00:18:f3:49:f5:d2 IEEE 802.11: authenticated May 6 11:10:31 localhost hostapd: wlan0: STA 00:18:f3:49:f5:d2 IEEE 802.11: associated (aid 1) May 6 11:10:31 localhost hostapd: wlan0: STA 00:18:f3:49:f5:d2 RADIUS: starting accounting session 4BE2E796-00000001 May 6 11:10:31 localhost hostapd: wlan0: STA 00:18:f3:49:f5:d2 WPA: pairwise key handshake completed (RSN) May 6 11:20:22 localhost hostapd: wlan0: STA 00:18:f3:49:f5:d2 WPA: group key handshake completed (RSN) Please let me know if there is any additional information I can provide to help figure out what is causing the problem. Ok, this is frustrating.. Now TWO bugs that have to do with the issues i'm having have been closed and it's still not working for me. Am I not doing something correctly when I post to the bug since there was no response to my last post and the bug was just closed without any type of resolution that I can see??? Thanks, Ron Ron, you need to ensure that your comments are pertinent to the bug where you make them. In the first case, you commented in bug 544497 about what seems to have been the same issue as the one that prompted this bug. So, I asked you to test -115.fc12 and comment on this bug. In comment 3, you seem to confirm that -115.fc12 resovle the issue for you ("the good news is that I don't get the kernel crash report in the messages log"). Unfortunately, you went on to comment about an issue that is not at all clearly related. Rather than discussing the other issue here, you would be better off opening a new bug for that issue. John, Thanks for your response. I think the issue is still releated, but that the system is crashing harder and therefore no logging happens, I think my post wasn't clear on that. Basically the same thing happens that happened before but the system just locks up. I'll do as you suggest and open a new bug, I'm just not sure what I'll post since the logs (as far as I can tell) aren't giving any useful information. 2.6.33.5-112.fc13.x86_64 x86_64 is working great for me, Ron, aside from the usual Xorg slowness recovering from suspend. It reconnects to wireless and does not crash. I know it's a whale of a solution, but perhaps you could try upgrading to F13. |