Bug#605200: linux-image-2.6.32-5-686: ipw2100 fatal interrupts using TKIP (WPA2-PSK)

2011-02-15 Thread Albin Stjerna
I, too, have this problem, but with standard unencrypted connections. At least 
on my home network, WPA2-PSK does not give the same result. This is using 
ipw2100 on a newly-installed squeeze on a Thinkpad X31 using cnetworkmanager to 
connect.


pgpLVGslHNSUH.pgp
Description: PGP signature


Bug#605200: linux-image-2.6.32-5-686: ipw2100 fatal interrupts using TKIP (WPA2-PSK)

2010-11-27 Thread Andrew Pimlott
Package: linux-2.6
Version: 2.6.32-27
Severity: normal

I set up a new wireless router and started getting frequent network
dropouts associated with the message ipw2100: Fatal interrupt.
Scheduling firmware restart.  I have narrowed down the problem to TKIP
encryption in WPA2-PSK.  If I use WEP or no encryption, or if I switch
my encryption to AES, I don't have this problem.

computer
- IBM Thinkpad X40
- Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04)
- ipw2100 firmware 1.3
- Debian unstable
- linux-image-2.6.32-5-686 (no other kernel/driver versions tested)
- wpa_supplicant 0.6.10-2 with a hand-edited wpa_supplicant.conf.  My
  entry for this network is:

network={
ssid=ESSID
key_mgmt=WPA-PSK
psk=passphrase
}

access point
- Ubee (Ambit) U10C019
- All advanced wireless settings at their default (I played with them,
  but none made a difference)
- WPA2-PSK set to enabled, WPA-PSK set to disabled (I don't WPA vs WPA2
  makes a difference though)

Then, I switch the option WPA/WPA2 Encryption between TKIP and AES.
In the first case only, I get frequent fatal interrupts.  They coincide
with me initiating network activity and happen very reliably, ie, an
interactive ssh session is unusable.

I have used other WPA-PSK networks in the past without trouble, but I
don't know whether they were using TKIP.

Let me know if I can provide more information.

Andrew

-- Package-specific info:
** Version:
Linux version 2.6.32-5-686 (Debian 2.6.32-27) (m...@debian.org) (gcc version 
4.3.5 (Debian 4.3.5-4) ) #1 SMP Sat Oct 30 22:47:19 UTC 2010

** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 
root=UUID=73cf35da-d145-4e4b-b662-3849f9a0ae64 ro

** Not tainted

** Kernel log:
[535890.008817] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[535900.432028] eth1: no IPv6 routers present
[535936.909959] ipw2100: Fatal interrupt. Scheduling firmware restart.
[535940.454914] ADDRCONF(NETDEV_UP): eth1: link is not ready
[535942.552687] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[535952.932024] eth1: no IPv6 routers present
[536157.662633] ADDRCONF(NETDEV_UP): eth1: link is not ready
[536183.396795] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[536193.756138] eth1: no IPv6 routers present
[537151.793914] ipw2100: Fatal interrupt. Scheduling firmware restart.
[537180.200072] ipw2100: Fatal interrupt. Scheduling firmware restart.
[537183.648274] ADDRCONF(NETDEV_UP): eth1: link is not ready
[537185.444772] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[537196.296144] eth1: no IPv6 routers present
[537236.830482] ipw2100: Fatal interrupt. Scheduling firmware restart.
[537273.668774] ipw2100: Fatal interrupt. Scheduling firmware restart.
[537277.457861] ADDRCONF(NETDEV_UP): eth1: link is not ready
[537279.448683] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[537289.548137] eth1: no IPv6 routers present
[537302.730971] ipw2100: Fatal interrupt. Scheduling firmware restart.
[537316.785067] ipw2100: Fatal interrupt. Scheduling firmware restart.
[537328.839142] ipw2100: Fatal interrupt. Scheduling firmware restart.
[537405.981689] ipw2100: Fatal interrupt. Scheduling firmware restart.
[537416.051722] ipw2100: Fatal interrupt. Scheduling firmware restart.
[537425.833668] ipw2100: Fatal interrupt. Scheduling firmware restart.
[537435.119690] ipw2100: Fatal interrupt. Scheduling firmware restart.
[537448.773420] ipw2100: Fatal interrupt. Scheduling firmware restart.
[537461.787196] ipw2100: Fatal interrupt. Scheduling firmware restart.
[537469.185193] ipw2100: Fatal interrupt. Scheduling firmware restart.
[537488.759275] ipw2100: Fatal interrupt. Scheduling firmware restart.
[537516.269445] ipw2100: Fatal interrupt. Scheduling firmware restart.
[537519.809102] ADDRCONF(NETDEV_UP): eth1: link is not ready
[537522.784864] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[537532.824135] eth1: no IPv6 routers present
[537759.989349] ipw2100: Fatal interrupt. Scheduling firmware restart.
[537829.116000] ipw2100: Fatal interrupt. Scheduling firmware restart.
[537973.187184] ipw2100: Fatal interrupt. Scheduling firmware restart.
[537985.113332] ipw2100: Fatal interrupt. Scheduling firmware restart.
[538002.191421] ipw2100: Fatal interrupt. Scheduling firmware restart.
[538026.917427] ipw2100: Fatal interrupt. Scheduling firmware restart.
[538077.083697] ipw2100: Fatal interrupt. Scheduling firmware restart.
[538091.265583] ipw2100: Fatal interrupt. Scheduling firmware restart.
[538547.819491] ipw2100: Fatal interrupt. Scheduling firmware restart.
[538551.373429] ADDRCONF(NETDEV_UP): eth1: link is not ready
[538553.800688] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[538564.068035] eth1: no IPv6 routers present
[538593.374828] ADDRCONF(NETDEV_UP): eth1: link is not ready
[538595.436766] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[538606.396146] eth1: no IPv6 routers present
[538621.281997] ipw2100: Fatal interrupt. Scheduling firmware restart.