[maverick regression] Intel 4965 cannot connect using WPA2

Bug #670394 reported by Marco Cimmino
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I installed Kubuntu Maverick 10.10 and my wifi is not connecting anymore to the office wifi that is a WPA2 5 Ghz hotspot, it is not using n protocol. And even when I manage to connect (after many tries) it is very unstable.
Rebooting using Lucid kernel (2.6.32) then it works perfectly, so I guess there is a regression in the iwlagn module?

In the dmesg.log you can see 1st try is connecting to this wifi that fails all the time, finally I connected to a unprotected wifi and got connected at 1st try.

Revision history for this message
Marco Cimmino (cimmo) wrote :
Revision history for this message
Marco Cimmino (cimmo) wrote :
Revision history for this message
Marco Cimmino (cimmo) wrote :
Revision history for this message
Marco Cimmino (cimmo) wrote :
description: updated
Revision history for this message
Marco Cimmino (cimmo) wrote :

I also noticed that on another WIFI connection, sometimes it drops and dmesg shows:
[61911.077783] iwlagn 0000:03:00.0: Microcode SW error detected. Restarting 0x82000000.
[61911.077793] iwlagn 0000:03:00.0: Loaded firmware version: 228.61.2.24
[61911.077816] iwlagn 0000:03:00.0: Start IWL Error Log Dump:
[61911.077823] iwlagn 0000:03:00.0: Status: 0x000213E4, count: 5
[61911.077997] iwlagn 0000:03:00.0: Desc Time data1 data2 line
[61911.078009] iwlagn 0000:03:00.0: FH_ERROR (#12) 1197200616 0x00000008 0x03130000 208
[61911.078017] iwlagn 0000:03:00.0: pc blink1 blink2 ilink1 ilink2 hcmd
[61911.078027] iwlagn 0000:03:00.0: 0x0046C 0x07A10 0x004C2 0x006DE 0x07A2A 0x212001C
[61911.078034] iwlagn 0000:03:00.0: FH register values:
[61911.078056] iwlagn 0000:03:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X033bb700
[61911.078079] iwlagn 0000:03:00.0: FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X0033bb60
[61911.078102] iwlagn 0000:03:00.0: FH_RSCSR_CHNL0_WPTR: 0X00000008
[61911.078124] iwlagn 0000:03:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X00819004
[61911.078146] iwlagn 0000:03:00.0: FH_MEM_RSSR_SHARED_CTRL_REG: 0X0000003c
[61911.078168] iwlagn 0000:03:00.0: FH_MEM_RSSR_RX_STATUS_REG: 0X03130000
[61911.078191] iwlagn 0000:03:00.0: FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X00000000
[61911.078213] iwlagn 0000:03:00.0: FH_TSSR_TX_STATUS_REG: 0X07ff0002
[61911.078235] iwlagn 0000:03:00.0: FH_TSSR_TX_ERROR_REG: 0X00000000
[61911.078304] iwlagn 0000:03:00.0: Start IWL Event Log Dump: display last 20 entries
[61911.078332] iwlagn 0000:03:00.0: EVT_LOGT:1197199273:0x000000c4:0303
[61911.078351] iwlagn 0000:03:00.0: EVT_LOGT:1197199286:0x00000107:0106
[61911.078368] iwlagn 0000:03:00.0: EVT_LOGT:1197199288:0x00000000:0302
[61911.078386] iwlagn 0000:03:00.0: EVT_LOGT:1197199323:0x000000d4:0321
[61911.078404] iwlagn 0000:03:00.0: EVT_LOGT:1197199325:0x00000000:1350
[61911.078422] iwlagn 0000:03:00.0: EVT_LOGT:1197199325:0x00000000:1351
[61911.078440] iwlagn 0000:03:00.0: EVT_LOGT:1197199326:0x00000000:1352
[61911.078457] iwlagn 0000:03:00.0: EVT_LOGT:1197199326:0x00000003:1353
[61911.078475] iwlagn 0000:03:00.0: EVT_LOGT:1197199334:0x0000000c:0357
[61911.078493] iwlagn 0000:03:00.0: EVT_LOGT:1197200432:0x00000107:0106
[61911.078511] iwlagn 0000:03:00.0: EVT_LOGT:1197200433:0x00000000:0301
[61911.078528] iwlagn 0000:03:00.0: EVT_LOGT:1197200540:0x000000c4:0303
[61911.078546] iwlagn 0000:03:00.0: EVT_LOGT:1197200553:0x00000107:0106
[61911.078564] iwlagn 0000:03:00.0: EVT_LOGT:1197200555:0x00000000:0302
[61911.078581] iwlagn 0000:03:00.0: EVT_LOGT:1197200598:0x000000d4:0321
[61911.078599] iwlagn 0000:03:00.0: EVT_LOGT:1197200599:0x00000000:1350
[61911.078617] iwlagn 0000:03:00.0: EVT_LOGT:1197200600:0x00000000:1351
[61911.078634] iwlagn 0000:03:00.0: EVT_LOGT:1197200600:0x00000000:1352
[61911.078652] iwlagn 0000:03:00.0: EVT_LOGT:1197200601:0x00000003:1353
[61911.078669] iwlagn 0000:03:00.0: EVT_LOGT:1197200619:0x00000000:0125

Any idea when this can get fixed?

Revision history for this message
dasdas (geamgiulagresiv) wrote :

I have the same problem as described above. Same output from dmsg. Same behaviour.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Marco,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 670394

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.