From: "Carlos R. Mafra" <crmafra@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: "Luis R. Rodriguez" <mcgrof@qca.qualcomm.com>,
ath9k-devel@venema.h4ckr.net
Subject: [3.3-rc2+] Thousands of ath9k warnings on dmesg before laptop froze
Date: Mon, 6 Feb 2012 00:29:07 +0000 [thread overview]
Message-ID: <20120206002907.GA1899@Pilar.site> (raw)
I'm testing the latest kernel 3.3.0-rc2+ I pulled from git
this morning.
My laptop just froze, and when I rebooted I noticed that /var/log/messages
contained 48 thousand (!) warnings coming from ath9k since a few hours
ago. I'm pasting the first one:
------------[ cut here ]------------
WARNING: at /home/mafra/linux-2.6/drivers/net/wireless/ath/ath9k/rc.c:697 ath_rc_get_highest_rix+0x156/0x210 [ath9k]()
Hardware name: VPCEB4X1E
Modules linked in: dvb_usb_dib0700 dib0090 dib7000p dib7000m dib0070 dib8000 dib3000mc dibx000_common af_packet snd_pcm_oss snd_mixer_oss microcode arc4 sr_mod cdrom sg ath9k mac80211 uvcvideo ath9k_common ath9k_hw videobuf2_core videobuf2_vmalloc videobuf2_memops ath i2c_i801 cfg80211 sony_laptop rfkill radeon ttm drm_kms_helper drm i2c_algo_bit
Pid: 48, comm: kworker/u:6 Not tainted 3.3.0-rc2+ #6
Call Trace:
[<ffffffff81032f2a>] warn_slowpath_common+0x7a/0xb0
[<ffffffff81032f75>] warn_slowpath_null+0x15/0x20
[<ffffffffa0298eb6>] ath_rc_get_highest_rix+0x156/0x210 [ath9k]
[<ffffffffa0298ff3>] ath_get_rate+0x83/0x480 [ath9k]
[<ffffffffa024f006>] rate_control_get_rate+0x86/0x160 [mac80211]
[<ffffffffa025a112>] invoke_tx_handlers+0x7b2/0x1420 [mac80211]
[<ffffffff81061a00>] ? load_balance+0x90/0x8a0
[<ffffffffa025af22>] ieee80211_tx+0x82/0xf0 [mac80211]
[<ffffffffa025b030>] ieee80211_xmit+0xa0/0x100 [mac80211]
[<ffffffffa025c23a>] ieee80211_tx_skb_tid+0x5a/0x70 [mac80211]
[<ffffffffa0246f56>] ieee80211_send_nullfunc+0x56/0x70 [mac80211]
[<ffffffffa0248460>] ieee80211_dynamic_ps_enable_work+0x240/0x310 [mac80211]
[<ffffffffa0248220>] ? ieee80211_dynamic_ps_disable_work+0x50/0x50 [mac80211]
[<ffffffff81048d67>] process_one_work+0x117/0x390
[<ffffffff81049899>] worker_thread+0x169/0x350
[<ffffffff81049730>] ? manage_workers+0x240/0x240
[<ffffffff8104f096>] kthread+0x96/0xa0
[<ffffffff814f7714>] kernel_thread_helper+0x4/0x10
[<ffffffff8104f000>] ? flush_kthread_worker+0xb0/0xb0
[<ffffffff814f7710>] ? gs_change+0xb/0xb
---[ end trace 7a4892c93f508f3a ]---
------------[ cut here ]------------
I must say that until the laptop froze, I didn't notice anything unusual
to the point of checking my dmesg. Sometimes the internet was slow,
but I thought it was unrelated to the kernel.
Is there any other info I should provide or the above warning is enough?
next reply other threads:[~2012-02-06 0:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 0:29 Carlos R. Mafra [this message]
2012-02-06 22:57 ` [ath9k-devel] [3.3-rc2+] Thousands of ath9k warnings on dmesg before laptop froze Pavel Roskin
2012-02-07 12:23 ` Carlos R. Mafra
2012-02-08 22:29 ` Calvin Owens
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=20120206002907.GA1899@Pilar.site \
--to=crmafra@gmail.com \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@qca.qualcomm.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