Bug 456691 - possible iwl4965 regression in 2.6.25.10-86
Summary: possible iwl4965 regression in 2.6.25.10-86
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 9
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: John W. Linville
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-07-25 16:09 UTC by Phil Mayers
Modified: 2008-08-20 11:35 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-08-19 18:49:59 UTC
Type: ---


Attachments (Terms of Use)
extract of /var/log/messages whilst failing with newer kernel (4.75 KB, application/x-gzip)
2008-07-25 16:12 UTC, Phil Mayers
no flags Details

Description Phil Mayers 2008-07-25 16:09:28 UTC
Description of problem:

I have problems connecting to our WPA-Enterprise network (WPA, PEAP/MSCHAP)
under 2.6.25.10-86

If I reboot into the older kernel 2.6.25.9-76 I can connect fine

Driver is iwl4965, firmware version is 4.44.1.20-1

Version-Release number of selected component (if applicable):

2.6.25.10-86

How reproducible:

More or less always

Steps to Reproduce:
1. Try to connect to a WPA-enterprise network
2. System just prompts for password repeatedly
3. Never connects
  
Actual results:

No wireless

Expected results:

Wireless

Additional info:

I seem to get errors in /var/log/messages including:

iwl4965: Error sending TX power (-22)

There are also kernel oopses (info to follow in an attachment)

Our wireless platform (Cisco lightweight, formerly Airespace) syslogs messages
when I'm using the broken kernel version:

APF-3-CHECK_EXT_SUPP_RATES_FAILED: Could not check extended supported rates.
Missing supported rate for station. Length :0. Mobile MAC: 00:13:e8:c1:f8:f9.

APF-1-CONFLICT_IN_ASS_REQ: Conflicting Supported Rates in Association Request
from00:13:e8:c1:f8:f9

Comment 1 Phil Mayers 2008-07-25 16:12:39 UTC
Created attachment 312658 [details]
extract of /var/log/messages whilst failing with newer kernel

Comment 2 John W. Linville 2008-07-31 17:35:37 UTC
Can you try -97?  Someone else reported that it resolved this issue.

Comment 3 John W. Linville 2008-08-19 18:49:59 UTC
Closed due to lack of response...I'm pretty sure this is fixed.

Comment 4 Phil Mayers 2008-08-20 11:35:22 UTC
Yes, sorry for not replying - for reference, the -97 update did indeed correct the problem


Note You need to log in before you can comment on or make changes to this bug.