Bug#550534: Segmentation fault with trace on iwlagn
Severity: serious
Hi again,
Just got a trace from a iwlagn segmentation fault while using the
wireless 5300AGN:
[25208.585510] iwlagn 0000:0e:00.0: iwl_tx_agg_start on ra =
00:24:b2:d5:47:0a tid = 0
[27064.940420] iwlagn 0000:0e:00.0: iwl_tx_agg_start on ra =
00:24:b2:d5:47:0a tid = 1
[30506.841622] iwlagn 0000:0e:00.0: iwl_tx_agg_start on ra =
00:24:b2:d5:47:0a tid = 6
[30829.235684] iwlagn 0000:0e:00.0: Microcode SW error detected.
Restarting 0x2000000.
[30829.279187] Registered led device: iwl-phy0::radio
[30829.279231] Registered led device: iwl-phy0::assoc
[30829.279273] Registered led device: iwl-phy0::RX
[30829.279314] Registered led device: iwl-phy0::TX
[33014.697681] wlan0: deauthenticated from 00:24:b2:d5:47:0a (Reason: 2)
[33014.697706] iwlagn 0000:0e:00.0: Stopping AGG while state not ON or
starting
[33014.697714] iwlagn 0000:0e:00.0: queue number out of range: 0, must
be 10 to 19
[33014.697722] ------------[ cut here ]------------
[33014.697753] WARNING: at
/build/mattems-linux-2.6_2.6.32-9-amd64-NYTFdD/linux-2.6-2.6.32-9/debian/build/source_amd64_none/net/mac80211/agg-tx.c:150
___ieee80211_stop_tx_ba_session+0x72/0x76 [mac80211]()
[33014.697762] Hardware name: Vostro 1320
[33014.697766] Modules linked in: tun cryptd aes_x86_64 aes_generic
nvidia(P) vboxnetadp vboxnetflt vboxdrv microcode acpi_cpufreq
cpufreq_conservative cpufreq_stats cpufreq_userspace cpufreq_powersave
uinput fuse coretemp loop firewire_sbp2 joydev snd_hda_codec_idt
snd_hda_intel arc4 snd_hda_codec snd_hwdep ecb snd_pcm_oss snd_mixer_oss
snd_pcm snd_seq_midi snd_rawmidi iwlagn snd_seq_midi_event snd_seq
iwlcore mac80211 uvcvideo cfg80211 btusb videodev snd_timer psmouse
dell_laptop snd_seq_device v4l1_compat snd bluetooth v4l2_compat_ioctl32
soundcore rfkill i2c_i801 snd_page_alloc i2c_core serio_raw dcdbas
battery ac processor evdev ext4 mbcache jbd2 crc16 usbhid hid sg sr_mod
sd_mod crc_t10dif cdrom ahci libata uhci_hcd video output intel_agp
sdhci_pci sdhci ehci_hcd firewire_ohci firewire_core crc_itu_t button
r8169 mii mmc_core led_class scsi_mod usbcore nls_base thermal fan
thermal_sys [last unloaded: scsi_wait_scan]
[33014.697928] Pid: 840, comm: phy0 Tainted: P W 2.6.32-3-amd64 #1
[33014.697933] Call Trace:
[33014.697952] [<ffffffffa029e448>] ?
___ieee80211_stop_tx_ba_session+0x72/0x76 [mac80211]
[33014.697970] [<ffffffffa029e448>] ?
___ieee80211_stop_tx_ba_session+0x72/0x76 [mac80211]
[33014.697983] [<ffffffff8104dbf0>] ? warn_slowpath_common+0x77/0xa3
[33014.698000] [<ffffffffa029e448>] ?
___ieee80211_stop_tx_ba_session+0x72/0x76 [mac80211]
[33014.698018] [<ffffffffa029e54b>] ?
__ieee80211_stop_tx_ba_session+0x3f/0x54 [mac80211]
[33014.698036] [<ffffffffa029dfae>] ?
ieee80211_sta_tear_down_BA_sessions+0x1a/0x38 [mac80211]
[33014.698054] [<ffffffffa02a06c7>] ? ieee80211_set_disassoc+0xd9/0x1d8
[mac80211]
[33014.698073] [<ffffffffa02a082a>] ?
ieee80211_rx_mgmt_deauth+0x64/0x95 [mac80211]
[33014.698091] [<ffffffffa02a2b12>] ? ieee80211_sta_work+0x1ad/0xe77
[mac80211]
[33014.698103] [<ffffffff8105a9c0>] ? __mod_timer+0x141/0x153
[33014.698113] [<ffffffff8106146b>] ? worker_thread+0x188/0x21d
[33014.698131] [<ffffffffa02a2965>] ? ieee80211_sta_work+0x0/0xe77
[mac80211]
[33014.698141] [<ffffffff81064a56>] ? autoremove_wake_function+0x0/0x2e
[33014.698149] [<ffffffff810612e3>] ? worker_thread+0x0/0x21d
[33014.698156] [<ffffffff81064789>] ? kthread+0x79/0x81
[33014.698166] [<ffffffff81011baa>] ? child_rip+0xa/0x20
[33014.698176] [<ffffffff812a61d6>] ? unix_dgram_poll+0x0/0x139
[33014.698183] [<ffffffff81064710>] ? kthread+0x0/0x81
[33014.698190] [<ffffffff81011ba0>] ? child_rip+0x0/0x20
[33014.698196] ---[ end trace 0cc039d2a11f7b23 ]---
[33014.698242] iwlagn 0000:0e:00.0: Stopping AGG while state not ON or
starting
[33014.698283] iwlagn 0000:0e:00.0: Stopping AGG while state not ON or
starting
I was using the connection heavily - both in bandwidth and in number in
connections. This happens together with the Microcode error, restarting
and the start on ra error. This is rendering my wireless unusable, as I
cannot connect to some wifi hotspots too, the connection stop working
just after connection, even if the connection itself is not dropped.
Reply to: