Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751347Ab0DJGyJ (ORCPT ); Sat, 10 Apr 2010 02:54:09 -0400 Received: from he.sipsolutions.net ([78.46.109.217]:60672 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750982Ab0DJGyH (ORCPT ); Sat, 10 Apr 2010 02:54:07 -0400 Subject: Re: Warning in ath9k after update from 2.6.33.1 to 2.6.33.2 From: Johannes Berg To: Thomas =?ISO-8859-1?Q?B=E4chler?= Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org In-Reply-To: <4BBF6206.2070103@archlinux.org> References: <4BBF6206.2070103@archlinux.org> Content-Type: text/plain; charset="UTF-8" Date: Sat, 10 Apr 2010 08:54:02 +0200 Message-ID: <1270882442.4760.0.camel@jlt3.sipsolutions.net> Mime-Version: 1.0 X-Mailer: Evolution 2.29.92.1 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3668 Lines: 69 On Fri, 2010-04-09 at 19:21 +0200, Thomas Bächler wrote: > Since I upgraded from 2.6.33.1 to .2, I get the following warning > sometimes, related to wireless: > > ------------[ cut here ]------------ > WARNING: at kernel/softirq.c:143 local_bh_enable_ip+0x82/0xb0() > Hardware name: TECRA A11 > Modules linked in: ipv6 rfcomm sco bnep l2cap bridge stp llc > cpufreq_ondemand tun ext3 jbd btusb bluetooth uvcvideo videodev > snd_seq_dummy v4l1_compat arc4 snd_seq_oss ecb v4l2_compat_ioctl32 > snd_seq_midi_event snd_hda_codec_intelhdmi snd_seq snd_seq_device > tpm_infineon snd_hda_codec_realtek ath9k snd_pcm_oss ath9k_common > snd_mixer_oss snd_hda_intel snd_hda_codec mac80211 snd_hwdep snd_pcm > snd_timer ath9k_hw snd joydev soundcore ath sdhci_pci kvm_intel > snd_page_alloc ehci_hcd iTCO_wdt evdev sdhci iTCO_vendor_support kvm > usbcore mmc_core e1000e psmouse tpm_tis cfg80211 tpm toshiba_acpi > acpi_cpufreq led_class tpm_bios rfkill toshiba_bluetooth serio_raw > pcspkr sr_mod thermal cdrom battery sg ac freq_table processor rtc_cmos > rtc_core rtc_lib fpu aesni_intel cryptd aes_x86_64 aes_generic xts > gf128mul dm_crypt dm_mod sd_mod ahci libata scsi_mod ext4 mbcache jbd2 > crc16 i915 drm_kms_helper drm i2c_algo_bit button i2c_core video output > intel_agp [last unloaded: microcode] > Pid: 2571, comm: wpa_supplicant Not tainted 2.6.33-ARCH #1 > Call Trace: > [] warn_slowpath_common+0x78/0xb0 > [] warn_slowpath_null+0xf/0x20 > [] local_bh_enable_ip+0x82/0xb0 > [] _raw_spin_unlock_bh+0x1f/0x30 > [] ath_tx_node_cleanup+0x19d/0x1c0 [ath9k] > [] ath9k_sta_notify+0x57/0xb0 [ath9k] > [] __sta_info_unlink+0x174/0x220 [mac80211] > [] sta_info_unlink+0x38/0x60 [mac80211] > [] ieee80211_set_disassoc+0x1e9/0x290 [mac80211] > [] ieee80211_mgd_deauth+0x159/0x160 [mac80211] > [] ? default_wake_function+0x0/0x10 > [] ieee80211_deauth+0x19/0x20 [mac80211] > [] __cfg80211_mlme_deauth+0xee/0x130 [cfg80211] > [] ? __mutex_lock_slowpath+0x26d/0x370 > [] __cfg80211_disconnect+0x159/0x1d0 [cfg80211] > [] cfg80211_wext_siwmlme+0x8c/0xa0 [cfg80211] > [] ioctl_standard_iw_point+0x207/0x3a0 > [] ? cfg80211_wext_siwmlme+0x0/0xa0 [cfg80211] > [] ? ioctl_standard_call+0x0/0xd0 > [] ioctl_standard_call+0x99/0xd0 > [] ? __dev_get_by_name+0xa0/0xc0 > [] wext_ioctl_dispatch+0x1f7/0x210 > [] ? ioctl_private_call+0x0/0xa0 > [] wext_handle_ioctl+0x41/0x90 > [] dev_ioctl+0x679/0x850 > [] sock_ioctl+0xe2/0x290 > [] ? sys_recvfrom+0x13d/0x160 > [] vfs_ioctl+0x38/0xd0 > [] do_vfs_ioctl+0x80/0x560 > [] sys_ioctl+0x81/0xa0 > [] ? do_device_not_available+0x9/0x10 > [] system_call_fastpath+0x16/0x1b > ---[ end trace 8dbf12cb72787a6d ]--- I think the problem is that the locking for sta_notify changed, and a patch that was written for the new locking was backported to the old, irq-disabled, locking. johannes -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/