iwlagn Intel 5100 authentication fails Linux 2.6.35

Bug #614537 reported by mycl
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I recently installed Maverick (Ubuntu 10.10) alpha 3 with kernel 2.6.35-14-generic
Under lucid wireless was working fine.
Now it won't associate.
Automatic data collected by ubuntu-bug is booting from old kernel 2.6.32-24-generic-phc which works fine. (Can't report under the new kernel very easily due to lack of network.)
Hardware is intel 5100 -- Lenovo X200
Access point is D-Link DIR-655. (802.11n)
Also failed with other unknown 802.11g access point at my office.
Behavior is the same with and without linux-backports-modules-wireless-maverick-generic
backports package is not required under 2.6.24

Under new kernel (2.6.35), which is broken, syslog has:

Aug 6 12:13:42 pad NetworkManager: <info> (wlan0): supplicant connection state: scanning -> associating
Aug 6 12:13:42 pad kernel: [ 201.792584] wlan0: direct probe to 00:22:b0:b2:1b:0e (try 1)
Aug 6 12:13:42 pad kernel: [ 201.990266] wlan0: direct probe to 00:22:b0:b2:1b:0e (try 2)
Aug 6 12:13:42 pad kernel: [ 202.190296] wlan0: direct probe to 00:22:b0:b2:1b:0e (try 3)
Aug 6 12:13:42 pad kernel: [ 202.390253] wlan0: direct probe to 00:22:b0:b2:1b:0e timed out
Aug 6 12:13:52 pad wpa_supplicant[1111]: Authentication with 00:22:b0:b2:1b:0e timed out.
Aug 6 12:13:52 pad NetworkManager: <info> (wlan0): supplicant connection state: associating -> disconnected

Under old kernel (2.6.32), which works, syslog has:

Aug 6 12:14:42 pad NetworkManager: <info> (wlan0): supplicant connection state: scanning -> associating
Aug 6 12:14:42 pad kernel: [ 22.868820] wlan0: direct probe to AP 00:22:b0:b2:1b:0e (try 1)
Aug 6 12:14:42 pad kernel: [ 22.873593] wlan0: direct probe responded
Aug 6 12:14:42 pad kernel: [ 22.873602] wlan0: authenticate with AP 00:22:b0:b2:1b:0e (try 1)
Aug 6 12:14:42 pad kernel: [ 22.875378] wlan0: authenticated
Aug 6 12:14:42 pad kernel: [ 22.875417] wlan0: associate with AP 00:22:b0:b2:1b:0e (try 1)
Aug 6 12:14:42 pad kernel: [ 22.878711] wlan0: RX AssocResp from 00:22:b0:b2:1b:0e (capab=0x431 status=0 aid=1)
Aug 6 12:14:42 pad kernel: [ 22.878720] wlan0: associated
Aug 6 12:14:42 pad wpa_supplicant[1012]: Associated with 00:22:b0:b2:1b:0e
Aug 6 12:14:42 pad NetworkManager: <info> (wlan0): supplicant connection state: associating -> associated

Also, while failing to connect to the unknown router at work (but not to the DIR-655) I got a bunch of these:

Aug 6 02:45:19 pad kernel: [ 500.795685] iwlagn 0000:03:00.0: Fail finding valid aggregation tid: 0
Aug 6 02:45:25 pad kernel: [ 506.649698] ata1.00: configured for UDMA/133
Aug 6 02:45:25 pad kernel: [ 506.649708] ata1: EH complete
Aug 6 02:45:25 pad kernel: [ 506.686680] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro,commit=0
Aug 6 02:45:25 pad kernel: [ 506.741512] iwlagn 0000:03:00.0: Microcode SW error detected. Restarting 0x2000000.
Aug 6 02:45:25 pad kernel: [ 506.741523] iwlagn 0000:03:00.0: Loaded firmware version: 8.24.2.12
Aug 6 02:45:25 pad kernel: [ 506.741543] iwlagn 0000:03:00.0: Start IWL Error Log Dump:
Aug 6 02:45:25 pad kernel: [ 506.741550] iwlagn 0000:03:00.0: Status: 0x000212E4, count: 5
Aug 6 02:45:25 pad kernel: [ 506.741697] iwlagn 0000:03:00.0: Desc Time data1 data2 line
Aug 6 02:45:25 pad kernel: [ 506.741707] iwlagn 0000:03:00.0: SYSASSERT (#05) 2336369206 0x0000008C 0x00000088 140
Aug 6 02:45:25 pad kernel: [ 506.741713] iwlagn 0000:03:00.0: pc blink1 blink2 ilink1 ilink2 hcmd
Aug 6 02:45:25 pad kernel: [ 506.741721] iwlagn 0000:03:00.0: 0x1F650 0x1F790 0x1F790 0x008B2 0x00000 0x4CD0010
Aug 6 02:45:25 pad kernel: [ 506.741727] iwlagn 0000:03:00.0: CSR values:
Aug 6 02:45:25 pad kernel: [ 506.741732] iwlagn 0000:03:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG)
Aug 6 02:45:25 pad kernel: [ 506.741742] iwlagn 0000:03:00.0: CSR_HW_IF_CONFIG_REG: 0X00480303
Aug 6 02:45:25 pad kernel: [ 506.741750] iwlagn 0000:03:00.0: CSR_INT_COALESCING: 0X0000ff40
Aug 6 02:45:25 pad kernel: [ 506.741759] iwlagn 0000:03:00.0: CSR_INT: 0X00000000
Aug 6 02:45:25 pad kernel: [ 506.741767] iwlagn 0000:03:00.0: CSR_INT_MASK: 0X00000000
Aug 6 02:45:25 pad kernel: [ 506.741776] iwlagn 0000:03:00.0: CSR_FH_INT_STATUS: 0X00000000
Aug 6 02:45:25 pad kernel: [ 506.741784] iwlagn 0000:03:00.0: CSR_GPIO_IN: 0X00000000
Aug 6 02:45:25 pad kernel: [ 506.741792] iwlagn 0000:03:00.0: CSR_RESET: 0X00000000
Aug 6 02:45:25 pad kernel: [ 506.741801] iwlagn 0000:03:00.0: CSR_GP_CNTRL: 0X080403c5
Aug 6 02:45:25 pad kernel: [ 506.741809] iwlagn 0000:03:00.0: CSR_HW_REV: 0X00000054
Aug 6 02:45:25 pad kernel: [ 506.741818] iwlagn 0000:03:00.0: CSR_EEPROM_REG: 0X00000000
Aug 6 02:45:25 pad kernel: [ 506.741826] iwlagn 0000:03:00.0: CSR_EEPROM_GP: 0X90000004
Aug 6 02:45:25 pad kernel: [ 506.741834] iwlagn 0000:03:00.0: CSR_OTP_GP_REG: 0X00060000
Aug 6 02:45:25 pad kernel: [ 506.741843] iwlagn 0000:03:00.0: CSR_GIO_REG: 0X00080046
Aug 6 02:45:25 pad kernel: [ 506.741851] iwlagn 0000:03:00.0: CSR_GP_UCODE_REG: 0X00001c77
Aug 6 02:45:25 pad kernel: [ 506.741860] iwlagn 0000:03:00.0: CSR_GP_DRIVER_REG: 0X00000000
Aug 6 02:45:25 pad kernel: [ 506.741869] iwlagn 0000:03:00.0: CSR_UCODE_DRV_GP1: 0X00000000
Aug 6 02:45:25 pad kernel: [ 506.741877] iwlagn 0000:03:00.0: CSR_UCODE_DRV_GP2: 0X00000000
Aug 6 02:45:25 pad kernel: [ 506.741885] iwlagn 0000:03:00.0: CSR_LED_REG: 0X00000058
Aug 6 02:45:25 pad kernel: [ 506.741894] iwlagn 0000:03:00.0: CSR_DRAM_INT_TBL_REG: 0X880b4c68
Aug 6 02:45:25 pad kernel: [ 506.741902] iwlagn 0000:03:00.0: CSR_GIO_CHICKEN_BITS: 0X27800200
Aug 6 02:45:25 pad kernel: [ 506.741911] iwlagn 0000:03:00.0: CSR_ANA_PLL_CFG: 0X00880300
Aug 6 02:45:25 pad kernel: [ 506.741919] iwlagn 0000:03:00.0: CSR_HW_REV_WA_REG: 0X0001001a
Aug 6 02:45:25 pad kernel: [ 506.741928] iwlagn 0000:03:00.0: CSR_DBG_HPET_MEM_REG: 0Xffff0000
Aug 6 02:45:25 pad kernel: [ 506.741934] iwlagn 0000:03:00.0: FH register values:
Aug 6 02:45:25 pad kernel: [ 506.741928] iwlagn 0000:03:00.0: CSR_DBG_HPET_MEM_REG: 0Xffff0000
Aug 6 02:45:25 pad kernel: [ 506.741934] iwlagn 0000:03:00.0: FH register values:
Aug 6 02:45:25 pad kernel: [ 506.741951] iwlagn 0000:03:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X037b7800
Aug 6 02:45:25 pad kernel: [ 506.741969] iwlagn 0000:03:00.0: FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X00b4c120
Aug 6 02:45:25 pad kernel: [ 506.741986] iwlagn 0000:03:00.0: FH_RSCSR_CHNL0_WPTR: 0X00000028
Aug 6 02:45:25 pad kernel: [ 506.742004] iwlagn 0000:03:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X80819104
Aug 6 02:45:25 pad kernel: [ 506.742022] iwlagn 0000:03:00.0: FH_MEM_RSSR_SHARED_CTRL_REG: 0X000000fc
Aug 6 02:45:25 pad kernel: [ 506.742039] iwlagn 0000:03:00.0: FH_MEM_RSSR_RX_STATUS_REG: 0X07030000
Aug 6 02:45:25 pad kernel: [ 506.742057] iwlagn 0000:03:00.0: FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X00000000
Aug 6 02:45:25 pad kernel: [ 506.742075] iwlagn 0000:03:00.0: FH_TSSR_TX_STATUS_REG: 0X07ff0001
Aug 6 02:45:25 pad kernel: [ 506.742092] iwlagn 0000:03:00.0: FH_TSSR_TX_ERROR_REG: 0X00000000
Aug 6 02:45:25 pad kernel: [ 506.742150] iwlagn 0000:03:00.0: Start IWL Event Log Dump: display last 20 entries
Aug 6 02:45:25 pad kernel: [ 506.742173] iwlagn 0000:03:00.0: EVT_LOGT:0025390938:0x00000024:1108
Aug 6 02:45:25 pad kernel: [ 506.742187] iwlagn 0000:03:00.0: EVT_LOGT:0025390938:0x00000001:1108
Aug 6 02:45:25 pad kernel: [ 506.742202] iwlagn 0000:03:00.0: EVT_LOGT:0025390939:0x00000033:1108
Aug 6 02:45:25 pad kernel: [ 506.742217] iwlagn 0000:03:00.0: EVT_LOGT:0025390944:0x00000088:0461
Aug 6 02:45:25 pad kernel: [ 506.742232] iwlagn 0000:03:00.0: EVT_LOGT:0025390945:0x00000088:0461
Aug 6 02:45:25 pad kernel: [ 506.742246] iwlagn 0000:03:00.0: EVT_LOGT:0025390963:0x00002806:1062
Aug 6 02:45:25 pad kernel: [ 506.742261] iwlagn 0000:03:00.0: EVT_LOGT:0025390967:0x02020202:1074
Aug 6 02:45:25 pad kernel: [ 506.742276] iwlagn 0000:03:00.0: EVT_LOGT:0025391971:0x00000325:1074
Aug 6 02:45:25 pad kernel: [ 506.742291] iwlagn 0000:03:00.0: EVT_LOGT:0025392023:0x000001cf:0601
Aug 6 02:45:25 pad kernel: [ 506.742305] iwlagn 0000:03:00.0: EVT_LOGT:0025392023:0x0000006f:0638
Aug 6 02:45:25 pad kernel: [ 506.742320] iwlagn 0000:03:00.0: EVT_LOGT:0025392027:0x000000c3:0601
Aug 6 02:45:25 pad kernel: [ 506.742335] iwlagn 0000:03:00.0: EVT_LOGT:0025392036:0x00000070:0631
Aug 6 02:45:25 pad kernel: [ 506.742349] iwlagn 0000:03:00.0: EVT_LOGT:0025397369:0x44cc0072:0401
Aug 6 02:45:25 pad kernel: [ 506.742364] iwlagn 0000:03:00.0: EVT_LOGT:0025397375:0x00000008:0600
Aug 6 02:45:25 pad kernel: [ 506.742378] iwlagn 0000:03:00.0: EVT_LOGT:0025397380:0x00000000:0475
Aug 6 02:45:25 pad kernel: [ 506.742393] iwlagn 0000:03:00.0: EVT_LOGT:0025397382:0x00000004:0451
Aug 6 02:45:25 pad kernel: [ 506.742408] iwlagn 0000:03:00.0: EVT_LOGT:0025397383:0x00000004:0451
Aug 6 02:45:25 pad kernel: [ 506.742422] iwlagn 0000:03:00.0: EVT_LOGT:0025397436:0x04cd0010:0401
Aug 6 02:45:25 pad kernel: [ 506.742437] iwlagn 0000:03:00.0: EVT_LOGT:0025397438:0x00000088:0451
Aug 6 02:45:25 pad kernel: [ 506.742451] iwlagn 0000:03:00.0: EVT_LOGT:0025397445:0x00000000:0125
Aug 6 02:45:25 pad kernel: [ 506.742490] iwlagn 0000:03:00.0: Command REPLY_RXON failed: FW Error
Aug 6 02:45:25 pad kernel: [ 506.742499] iwlagn 0000:03:00.0: Error clearing ASSOC_MSK (-5)

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image (not installed)
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-24.38~phc0-generic-phc 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic-phc x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: m 1947 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf2620000 irq 17'
   Mixer name : 'Conexant CX20561 (Hermosa)'
   Components : 'HDA:14f15051,17aa20ff,00100000'
   Controls : 14
   Simple ctrls : 7
Card29.Amixer.info:
 Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 7XHT21WW-1.03'
   Mixer name : 'ThinkPad EC 7XHT21WW-1.03'
   Components : ''
   Controls : 1
   Simple ctrls : 1
Card29.Amixer.values:
 Simple mixer control 'Console',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Date: Fri Aug 6 12:20:34 2010
HibernationDevice: RESUME=UUID=7eb972a0-46c9-4837-8193-938b60281a38
MachineType: LENOVO 7459GW2
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-24-generic-phc root=UUID=1e2d4209-a8a6-4f64-82f3-559067caef9d ro ipv6.disable=1
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.37
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
dmi.bios.date: 07/30/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 6DET28WW (1.05 )
dmi.board.name: 7459GW2
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: 1S7459GW2L3ABC4N
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6DET28WW(1.05):bd07/30/2008:svnLENOVO:pn7459GW2:pvrThinkPadX200:rvnLENOVO:rn7459GW2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 7459GW2
dmi.product.version: ThinkPad X200
dmi.sys.vendor: LENOVO

Revision history for this message
mycl (415fox) wrote :
Revision history for this message
mycl (415fox) wrote :

Solved this one. In order to make my card work with a previous kernel I needed the following modprobe options:

options iwlagn disable_hw_scan=1 swcrypto50=1 swcrypto=1

With the new kernel this messes it up. But removing the options, everything works fine.

Revision history for this message
Diego Schulz (dschulzg) wrote :

@mycl: I'm having the same issue here, but I couldn't find the file in wich you edited that line.
Was it in /etc/modules ?

rgrep iwlagn /etc/*

gives nothing resembling the line you described.

Revision history for this message
Frederik Möllers (fredfredfred) wrote :

I have/had a similar problem with the same error messages appearing (see bug #663298).
For me it worked again after I turned on Bluetooth (thanks to Zander Hill for the info).

Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
tags: removed: regression-potential
Revision history for this message
James M. Leddy (jm-leddy) wrote :

This is possibly a duplicate of bug 752829

Revision history for this message
penalvch (penalvch) wrote :

mycl, this bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in linux (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.