public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dhaval Giani <dhaval@linux.vnet.ibm.com>
To: linville@tuxdriver.com, davem@davemloft.net
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: WARNING: at net/mac80211/rx.c:2234 __ieee80211_rx+0x7f/0x559 [mac80211]()
Date: Tue, 6 Jan 2009 22:37:40 +0530	[thread overview]
Message-ID: <20090106170740.GD11588@linux.vnet.ibm.com> (raw)

Hi,

I see this on current git. Not sure how to reproduce it, has happened on
two random occasions. At both times, I was not connected to a wireless
network, but to wired networks.

------------[ cut here ]------------
WARNING: at net/mac80211/rx.c:2234 __ieee80211_rx+0x7f/0x559
[mac80211]()
Hardware name: 2007CS3
Modules linked in: tun fuse radeon drm ipt_MASQUERADE iptable_nat nf_nat
bridge stp bnep sco l2cap bluetooth ip6t_REJECT nf_conntrack_ipv6
ip6table_filter ip6_tables ipv6 cpufreq_ondemand acpi_cpufreq
dm_multipath kvm_intel kvm uinput snd_hda_codec_analog snd_hda_intel
snd_hd
a_codec snd_hwdep snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq
arc4 snd_seq_device ecb snd_pcm_oss ath5k mac80211 snd_mixer_oss
thinkpad_acpi snd_pcm rfkill hwmon snd_timer i2c_i801 snd iTCO_wdt
yenta_socket pcspkr joydev nsc_ircc i2c_core iTCO_vendor_support
rsrc_non
static cfg80211 soundcore irda snd_page_alloc video output crc_ccitt
[last unloaded: scsi_wait_scan]
Pid: 0, comm: swapper Not tainted 2.6.28 #5
Call Trace:
 [<c043180f>] warn_slowpath+0x76/0xad
 [<c04512d8>] ? __lock_acquire+0xb3b/0xb4a
 [<c044f3bd>] ? trace_hardirqs_off+0xb/0xd
 [<f80d4192>] __ieee80211_rx+0x7f/0x559 [mac80211]
 [<f80a19f4>] ath5k_tasklet_rx+0x4f7/0x53b [ath5k]
 [<c06f6edb>] ? _spin_unlock_irq+0x27/0x34
 [<c04360fc>] tasklet_action+0x84/0xef
 [<c0436802>] __do_softirq+0x9d/0x157
 [<c0436765>] ? __do_softirq+0x0/0x157
 <IRQ>  [<c0470e78>] ? handle_fasteoi_irq+0x0/0xb6
 [<c0436493>] ? irq_exit+0x49/0x85
 [<c04055df>] ? do_IRQ+0xf5/0x10b
 [<c04042ac>] ? common_interrupt+0x2c/0x34
 [<c045017e>] ? trace_hardirqs_on+0xb/0xd
 [<c045007b>] ? trace_hardirqs_on_caller+0x5c/0x154
 [<c058cf89>] ? acpi_idle_enter_bm+0x281/0x2d0
 [<c0665273>] ? cpuidle_idle_call+0x65/0x96
 [<c0402c96>] ? cpu_idle+0x84/0xae
 [<c06e2e1b>] ? rest_init+0x53/0x55
---[ end trace e5a3692e59279535 ]---

Thanks,
-- 
regards,
Dhaval

             reply	other threads:[~2009-01-06 17:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-06 17:07 Dhaval Giani [this message]
2009-01-07 13:51 ` [PATCH 1/1] ath5k: fix hw rate index condition Jiri Slaby
2009-01-07 14:36   ` Jiri Slaby
2009-01-07 15:22     ` Dhaval Giani
2009-01-07 15:30       ` Jiri Slaby
2009-02-02  7:57         ` Dhaval Giani
2009-02-15 13:47           ` Bob Copeland
2009-02-28 23:08             ` Jiri Slaby
2009-03-30  8:59               ` Dhaval Giani
2009-03-30 16:58                 ` Bob Copeland
2009-03-30 17:59                   ` Dhaval Giani
2009-03-30 18:13                     ` Bob Copeland
2009-03-31  3:51                       ` Dhaval Giani
2009-03-31 12:23                         ` Bob Copeland
2009-04-08 15:22                           ` [ath5k-devel] " Bob Copeland
2009-03-15 21:27     ` Stefan Lippers-Hollmann
2009-03-15 21:35       ` Michael Buesch
2009-03-23  0:45       ` Stefan Lippers-Hollmann
2009-03-23  2:31         ` Bob Copeland

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=20090106170740.GD11588@linux.vnet.ibm.com \
    --to=dhaval@linux.vnet.ibm.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox