From: "Carlos R. Mafra" <crmafra2@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: linux-wireless@vger.kernel.org
Subject: iwlagn warning in 2.6.29-rc6
Date: Mon, 23 Feb 2009 22:26:15 +0100 [thread overview]
Message-ID: <20090223212615.GA5047@Pilar.Speedport_W_303V_Typ_A> (raw)
I've just got this warning in my Vaio laptop:
------------[ cut here ]------------
WARNING: at drivers/net/wireless/iwlwifi/iwl-tx.c:1254 iwl_tx_cmd_complete+0x28a/0x2e0()
Hardware name: VGN-FZ240E
wrong command queue 31, sequence 0x7FFF readp=241 writep=241
Modules linked in: usbhid nvram snd_hda_codec_idt snd_hda_intel snd_hda_codec uvcvideo snd_hwdep snd_pcm iwlagn videodev snd_timer sky2 v4l1_compat v4l2_compat_ioctl32 evdev sg i2c_i801 snd_page_alloc sr_mod ata_piix ahci libata sd_mod scsi_mod uhci_hcd ohci_hcd ehci_hcd usbcore [last unloaded: scsi_wait_scan]
Pid: 0, comm: swapper Not tainted 2.6.29-rc6 #37
Call Trace:
<IRQ> [<ffffffff8023d850>] warn_slowpath+0xd0/0x130
[<ffffffff8025072d>] ? queue_work_on+0x4d/0x60
[<ffffffff802508da>] ? queue_work+0x1a/0x20
[<ffffffff8053bb70>] ? ieee80211_sta_rx_mgmt+0xc0/0xf0
[<ffffffff80540f45>] ? ieee80211_invoke_rx_handlers+0x12c5/0x1650
[<ffffffff80233530>] ? enqueue_task_fair+0x190/0x2d0
[<ffffffff8022ecc0>] ? enqueue_task+0x50/0x60
[<ffffffff8025c049>] ? getnstimeofday+0x59/0xe0
[<ffffffff80234c24>] ? find_busiest_group+0x234/0x760
[<ffffffff8041eb3a>] iwl_tx_cmd_complete+0x28a/0x2e0
[<ffffffffa0124245>] iwl_rx_handle+0x115/0x4a0 [iwlagn]
[<ffffffffa01249ef>] iwl_irq_tasklet+0x41f/0xb30 [iwlagn]
[<ffffffff8025c049>] ? getnstimeofday+0x59/0xe0
[<ffffffff80242c39>] tasklet_action+0x69/0xf0
[<ffffffff80243784>] __do_softirq+0x94/0x160
[<ffffffff8020d57c>] call_softirq+0x1c/0x30
[<ffffffff8020ef35>] do_softirq+0x45/0x90
[<ffffffff80243435>] irq_exit+0x75/0xa0
[<ffffffff8020f196>] do_IRQ+0x86/0x110
[<ffffffff8020ce53>] ret_from_intr+0x0/0xa
<EOI> [<ffffffff803a0322>] ? acpi_idle_enter_bm+0x2bf/0x344
[<ffffffff803a0318>] ? acpi_idle_enter_bm+0x2b5/0x344
[<ffffffff802587cf>] ? notifier_call_chain+0x3f/0x80
[<ffffffff80455345>] ? cpuidle_idle_call+0xa5/0x100
[<ffffffff8020b492>] ? cpu_idle+0x62/0xc0
[<ffffffff80549c7c>] ? rest_init+0x5c/0x70
---[ end trace 281a546e35661751 ]---
The wireless connection still seems to be good after this (I've
found this warning after a curious look in the dmesg), but I
thought I should send the warning to lkml just in case it has
a deeper meaning to people out there.
The card is this one,
Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61)
I can provide the whole dmesg output if needed too.
next reply other threads:[~2009-02-23 21:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 21:26 Carlos R. Mafra [this message]
2009-02-23 22:45 ` reinette chatre
2009-02-24 12:38 ` Carlos R. Mafra
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=20090223212615.GA5047@Pilar.Speedport_W_303V_Typ_A \
--to=crmafra2@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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
all inboxes | Powered by JetHome®