[Solved] Kernel 2.6.32 and Intel 3945 wireless unstable

brianhanna · 2009-12-31 12:17:03

I'm having some issues with my Intel 3945 wireless card since the kernel upgrade. The connection is very unstable and drops completely after a few minutes

I get a new entry like this in my dmesg every few seconds.

iwl3945 0000:02:00.0: Microcode SW error detected. Restarting 0x82000008.
iwl3945 0000:02:00.0: Error Reply type 0x00000000 cmd REPLY_TX (0x1C) seq 0x0000 ser 0x00000000
Registered led device: iwl-phy0::radio
Registered led device: iwl-phy0::assoc
Registered led device: iwl-phy0::RX
Registered led device: iwl-phy0::TX

Last edited by brianhanna (2010-01-08 11:30:16)

brianhanna · 2009-12-31 13:23:43

I found this in the Ubuntu forums and tried it.

sudo rmmod -f iwl3945
sudo modprobe iwl3945 disable_hw_scan=1

It stays connected maybe a few minutes longer now but still fails. So far I've been able to get the card working again by restarting networking and reconnecting.

sudo /etc/rc.d/network restart
sudo iwconfig wlan0 essid 'myessid'
sudo dhcpcd wlan0

Anyone have any ideas what's causing the instability?

archlinuxsagi · 2009-12-31 14:37:20

how are you starting your wireless? through netcfg2?
I have a similar setup like yours and there is no such issues for me..
Maybe you can try re-install the kernel-firmware package based on the error:
iwl3945 0000:02:00.0: Microcode SW error detected. Restarting 0x82000008.
iwl3945 0000:02:00.0: Error Reply type 0x00000000 cmd REPLY_TX (0x1C) seq 0x0000 ser 0x00000000

brianhanna · 2009-12-31 14:46:58

I was using wicd but just to rule that out as a problem, I quit using that and went completely manual until I figure out the problem. I'll try your suggestion. Thanks.

Painless · 2010-01-01 17:54:17

Hi all,

I've also noticed problems with iwl3945 after I upgraded to 2.6.32.

My ssh connection to my server (local wireless LAN) keeps lagging and sometimes dropping. With web browsing, this was not a major issue, but with ssh dropping it is annoying. I've been experimenting with tmux (I used to run screen) and I though initially it was tmux, but I'm almost certain that it's the wifi connection.

There is nothing unusual which I can see in system logs.

I might have to revert to 2.6.31 if I can't find a fix.

I was using network manager. I've since changed back to netcfg, but this hasn't helped.

12o · 2010-01-01 20:21:48

I just started having the exact same problem after upgrading my kernel to 2.6.32 on ArchLinux x86_64. Now I get intermittent drops and messages of:

iwl3945 0000:02:00.0: Microcode SW error detected. Restarting 0x82000008.
iwl3945 0000:02:00.0: Error Reply type 0x00000000 cmd REPLY_TX (0x1C) seq 0x0000 ser 0x00000000
Registered led device: iwl-phy0::radio
Registered led device: iwl-phy0::assoc
Registered led device: iwl-phy0::RX
Registered led device: iwl-phy0::TX

I've been trolling forums and others are having the exact same problem, but unfortunately nobody seems to have the remotest clue as to how it could be happening. Might be a while before it's fixed, so reverting back to 2.6.31 is probably advisable.

Unfortunately, I just reinstalled ArchLinux due to a kernel update tanking halfway through with the rollback becoming corrupted somehow. I went right from CD to 2.6.32, and the wiki for kernel panics has absolutely no useful information about doing that, so I'm apparently screwed.

Otherwise, check the install CD for a package. For example, the version 2008.06 i686 CD contains addons/core-pkgs/kernel26-2.6.25.6-1-i686.pkg.tar.gz.

Since I'm still learning ArchLinux, the good ol' "1)do this, 2)*a miracle occurs*, 3) it works" bit doesn't really work for me.

Last edited by 12o (2010-01-01 20:31:00)

12o · 2010-01-02 00:45:23

As far as I can tell, having an instant messenger or IRC up and running (I use both) keeps the connection alive as someone suggested using ping constantly. I've had both up all day without problems, so that might work as a temporary fix for now.

Hope this helps.

TigTex · 2010-01-02 01:00:08

Last week I open a thread related with this issue here http://bbs.archlinux.org/viewtopic.php?id=87220

I also have unstable network but with intel 5100, never had this before on 2.6.31 (and older). My dmesg entries are different but the workaround is to ping constantly something (like 12o said)

Last edited by TigTex (2010-01-02 01:04:35)

12o · 2010-01-02 01:48:28

And wouldn't you know it. I spoke too soon, darn it. My connection dropped and wouldn't come back up. I had to kill wpa_supplicant and dhcpcd, then restart them again. Guess I'll just open up a terminal, set it ping my router, and minimize the box to see if that helps.

Thanks for the link and info, TigTex.

UPDATE
--------------------------------------------
Looking at the ping times to my router, I'm showing regularly timed spikes from a normal 0.7ms to 34ms. The really high ones seem to be the ones disconnecting. Anyone else showing that kind of difference?

Last edited by 12o (2010-01-02 02:16:31)

brianhanna · 2010-01-02 05:14:49

I've been trying a few things and it seems like a firmware issue but I'm not sure I can prove it yet.

chpln · 2010-01-02 06:08:34

I've an Intel 3945 and have been using kernel26 2.6.32 from testing for a month or so now without issue. Just to make sure I opened an ssh connection to my router and left the connection completely idle for 30 minutes or so; it was still fine.

Latency to my router is consistently within the 3-5ms range.

m7d1 · 2010-01-02 09:41:49

i have the same probelm with kernel 2.6.32 my netcfg wireless connection going down every few minutes, i am planning to downgrade the kernel.

dyscoria · 2010-01-02 13:09:14

12o wrote:

As far as I can tell, having an instant messenger or IRC up and running (I use both) keeps the connection alive as someone suggested using ping constantly. I've had both up all day without problems, so that might work as a temporary fix for now.
Hope this helps.

This seems to work for me aswell. For some reason inactivity causes disconnection.

12o · 2010-01-02 16:27:01

I left my connection up pinging my router all night and the connection never dropped. Just having IRSSI and Centerim running isn't enough. Pinging my router throughout the night kept the connection up without any disconnect. Looks like that's the remedy for now until the bug is fixed.

Last edited by 12o (2010-01-02 16:27:15)

Luis Sousa · 2010-01-02 16:39:48

My wireless card isnt intel, and after i wake it up from suspend, it doesnt connect automatically to wireless network (wicd). Also after kernel update...

12o · 2010-01-02 18:07:29

I connect manually and it does the same. It sounds like there are two solutions:

1) revert back to 2.6.31 kernel until the problem is fixed

2) open a terminal and set it to ping continuously

Not sure about your wireless card, Luis Sousa. But you could try one of the solutions we discussed in this thread (either 1 or 2). If it worked before your upgrade to 2.6.32, then reverting back should fix it. If you wouldn't mind, if you decide to revert back, could you mention in this thread if your solution did in fact work.

Or if anyone reverts their kernel back, could you post the result here? Just to make sure so that others have something to go on.

Thanks for the info. Hope this helps everyone.

Last edited by 12o (2010-01-02 18:09:02)

Luis Sousa · 2010-01-02 19:54:52

12o wrote:

Not sure about your wireless card, Luis Sousa. But you could try one of the solutions we discussed in this thread (either 1 or 2). If it worked before your upgrade to 2.6.32, then reverting back should fix it. If you wouldn't mind, if you decide to revert back, could you mention in this thread if your solution did in fact work.
Thanks for the info. Hope this helps everyone.

Not sure if i can revert kernel, gonna give it a try...

Last edited by Luis Sousa (2010-01-02 19:55:28)

Luis Sousa · 2010-01-02 21:03:34

Ok, first of all problem solved. Downgraded to kernel26-2.6.31.6-1 and also some packages that depended of 2.6.32-2 (ndiswrapper, open-vm-tools, nvidia and tiacx) and its working fine again. I dont think that the problem is in ndiswraper, 'cause im not using it.

Secondly, sorry but my card IS indeed a intel (stupid). It is a 'Intel Corporation PRO/Wireless 4965 AG or AGN' according to 'lspci'. Dont know why i think it wasnt, leftover alcohol from New Year, i think...

Lastly, is it me or lately updates have been more buggy than usual? It is not the first time in a very short period that i have to downgrade packages, a bit frustrating...

Last edited by Luis Sousa (2010-01-02 21:16:38)

12o · 2010-01-02 21:55:38

Looks like pinging the router only prolongs the inevitable. Just had a disconnect, so to make sure it never happens, the only real answer is to downgrade and wait. Since I had ping running in the background, it doesn't appear to be directly related to an idle connection (though having an idle connection certainly makes it happen a lot more).

Not sure how I'll do that since I went from a nine month old install CD right up to 2.6.32.

Luis Sousa · 2010-01-02 22:40:44

Easy, read this wiki. Then download kernel26-2.6.31.6-1 from one of the links in the page (i used the last one). Then 'pacman -U /where is located/kernel26-2.6.31.6-1.pkg.tar.gz' and if any package needs the most recent kernel (that was my case), just do the same before installing the kernel itself. Download and downgrade those packages (use -Ud). Then install kernel itself and you're on. Dont forget to reboot after.

http://wiki.archlinux.org/index.php/Downgrade_packages

brianhanna · 2010-01-03 02:17:00

I've tried lots of stuff the last couple days and it doesn't seem to be a firmware problem. Rolling back the kernel is the only thing that seems to work. Just for kicks I reinstalled 2009.08 and did a pacman -Syu with kernel26 ignored. Everything works so I guess it must be the new kernel.

broch · 2010-01-03 02:53:16

same card intel3945 and no problems with any of i686 2.6.31 - up to 2.6.33-rc2 kernels.
however I do not use either wicd or netcfg. Another fact is that I don't have Arch kernel installed, but I doubt that any difference would matter.

Maybe try different wireless manager (or even no wireless manager at all).
Unless you are on 64-bit and your problem is related to whatever 64-bit driver bug.

TigTex · 2010-01-03 03:03:53

I'm on 64bit and already tried just using iwconfig, still drops conectivity.

64bit bug maybe?

I will add dmesg from my other thread, to help reading

Registered led device: iwl-phy0::radio
Registered led device: iwl-phy0::assoc
Registered led device: iwl-phy0::RX
Registered led device: iwl-phy0::TX
wlan0: direct probe to AP 00:90:**:**:**:** (try 1)
wlan0: direct probe responded
wlan0: authenticate with AP 00:90:**:**:**:** (try 1)
wlan0: authenticated
wlan0: associate with AP 00:90:**:**:**:** (try 1)
wlan0: RX ReassocResp from 00:90:**:**:**:** (capab=0x431 status=12 aid=0)
wlan0: AP denied association (code=12)
wlan0: associate with AP 00:90:**:**:**:** (try 1)
wlan0: RX ReassocResp from 00:90:**:**:**:** (capab=0x431 status=12 aid=0)
wlan0: AP denied association (code=12)
wlan0: deauthenticating from 00:90:**:**:**:** by local choice (reason=3) < ------------ LOOK HERE
wlan0: deauthenticating from 00:90:**:**:**:** by local choice (reason=3)
Registered led device: iwl-phy0::radio
Registered led device: iwl-phy0::assoc
Registered led device: iwl-phy0::RX
Registered led device: iwl-phy0::TX
wlan0: direct probe to AP 00:90:**:**:**:** (try 1)
wlan0: direct probe responded
wlan0: authenticate with AP 00:90:**:**:**:** (try 1)
wlan0: authenticated
wlan0: associate with AP 00:90:**:**:**:** (try 1)
wlan0: RX ReassocResp from 00:90:**:**:**:** (capab=0x431 status=12 aid=0)
wlan0: AP denied association (code=12)
wlan0: associate with AP 00:90:**:**:**:** (try 1)
wlan0: RX ReassocResp from 00:90:**:**:**:** (capab=0x431 status=12 aid=0)
wlan0: AP denied association (code=12)
wlan0: deauthenticating from 00:90:**:**:**:** by local choice (reason=3)

folowed by (and this one looks bad...)

WARNING: at net/wireless/core.c:614 wdev_cleanup_work+0xe1/0x110 [cfg80211]()
Hardware name: G71V                
Modules linked in: cryptd aes_x86_64 aes_generic cpufreq_ondemand btusb bluetooth snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_hda_codec_nvhdmi snd_mixer_oss uvcvideo snd_hda_codec_realtek videodev v4l1_compat v4l2_compat_ioctl32 arc4 snd_hda_intel ecb snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore iwlagn joydev iwlcore snd_page_alloc sdhci_pci nvidia(P) mac80211 sdhci firewire_ohci iTCO_wdt uhci_hcd cfg80211 mmc_core intel_agp i2c_core iTCO_vendor_support ricoh_mmc firewire_core ehci_hcd r8169 mii crc_itu_t rfkill usbcore video output evdev asus_laptop acpi_cpufreq psmouse ac battery led_class thermal sg serio_raw button pcspkr freq_table processor rtc_cmos rtc_core rtc_lib dm_mirror dm_region_hash dm_log dm_mod ext4 mbcache jbd2 crc16 sd_mod ahci libata scsi_mod
Pid: 9, comm: events/0 Tainted: P           2.6.32-ARCH #1
Call Trace:
 [<ffffffff81055be3>] ? warn_slowpath_common+0x73/0xb0
 [<ffffffffa0203651>] ? wdev_cleanup_work+0xe1/0x110 [cfg80211]
 [<ffffffffa0203570>] ? wdev_cleanup_work+0x0/0x110 [cfg80211]
 [<ffffffff8106f6a3>] ? worker_thread+0x193/0x2f0
 [<ffffffff81074100>] ? autoremove_wake_function+0x0/0x30
 [<ffffffff8106f510>] ? worker_thread+0x0/0x2f0
 [<ffffffff81073d3e>] ? kthread+0x8e/0xa0
 [<ffffffff8101311a>] ? child_rip+0xa/0x20
 [<ffffffff81073cb0>] ? kthread+0x0/0xa0
 [<ffffffff81013110>] ? child_rip+0x0/0x20

maybe this is a different situation but with similar symptoms

Last edited by TigTex (2010-01-03 03:17:39)

chpln · 2010-01-03 03:16:07

TigTex wrote:

I'm on 64bit and already tried just using iwconfig, still drops conectivity.
64bit bug maybe?

x86_64 here and have been testing for problems for the last day or so. Still no issues.

Last edited by chpln (2010-01-03 03:17:28)

12o · 2010-01-03 04:43:21

Tried downgrading to kernel 2.6.31, but had to roll back my NVIDIA drivers also, otherwise video wouldn't work. NVIDIA drivers didn't work anyway, and every attempt was met with failure. I had to upgrade the kernel back in order to get it to work. Guess I'll have to wait.

Has anyone had success using the NVIDIA new 190 drivers with 2.6.31? I tried a force, but didn't get X working.

Last edited by 12o (2010-01-03 04:44:32)

Arch Linux

#1 2009-12-31 12:17:03

[Solved] Kernel 2.6.32 and Intel 3945 wireless unstable

#2 2009-12-31 13:23:43

Re: [Solved] Kernel 2.6.32 and Intel 3945 wireless unstable

#3 2009-12-31 14:37:20

Re: [Solved] Kernel 2.6.32 and Intel 3945 wireless unstable

#4 2009-12-31 14:46:58

Re: [Solved] Kernel 2.6.32 and Intel 3945 wireless unstable

#5 2010-01-01 17:54:17

Re: [Solved] Kernel 2.6.32 and Intel 3945 wireless unstable

#6 2010-01-01 20:21:48

Re: [Solved] Kernel 2.6.32 and Intel 3945 wireless unstable

#7 2010-01-02 00:45:23

Re: [Solved] Kernel 2.6.32 and Intel 3945 wireless unstable

#8 2010-01-02 01:00:08

Re: [Solved] Kernel 2.6.32 and Intel 3945 wireless unstable

#9 2010-01-02 01:48:28

Re: [Solved] Kernel 2.6.32 and Intel 3945 wireless unstable

#10 2010-01-02 05:14:49

Re: [Solved] Kernel 2.6.32 and Intel 3945 wireless unstable

#11 2010-01-02 06:08:34

Re: [Solved] Kernel 2.6.32 and Intel 3945 wireless unstable

#12 2010-01-02 09:41:49

Re: [Solved] Kernel 2.6.32 and Intel 3945 wireless unstable

#13 2010-01-02 13:09:14

Re: [Solved] Kernel 2.6.32 and Intel 3945 wireless unstable

#14 2010-01-02 16:27:01

Re: [Solved] Kernel 2.6.32 and Intel 3945 wireless unstable

#15 2010-01-02 16:39:48

Re: [Solved] Kernel 2.6.32 and Intel 3945 wireless unstable

#16 2010-01-02 18:07:29

Re: [Solved] Kernel 2.6.32 and Intel 3945 wireless unstable

#17 2010-01-02 19:54:52

Re: [Solved] Kernel 2.6.32 and Intel 3945 wireless unstable

#18 2010-01-02 21:03:34

Re: [Solved] Kernel 2.6.32 and Intel 3945 wireless unstable

#19 2010-01-02 21:55:38

Re: [Solved] Kernel 2.6.32 and Intel 3945 wireless unstable

#20 2010-01-02 22:40:44

Re: [Solved] Kernel 2.6.32 and Intel 3945 wireless unstable

#21 2010-01-03 02:17:00

Re: [Solved] Kernel 2.6.32 and Intel 3945 wireless unstable

#22 2010-01-03 02:53:16

Re: [Solved] Kernel 2.6.32 and Intel 3945 wireless unstable

#23 2010-01-03 03:03:53

Re: [Solved] Kernel 2.6.32 and Intel 3945 wireless unstable

#24 2010-01-03 03:16:07

Re: [Solved] Kernel 2.6.32 and Intel 3945 wireless unstable

#25 2010-01-03 04:43:21

Re: [Solved] Kernel 2.6.32 and Intel 3945 wireless unstable

Board footer