Bug 453920 - kernel-2.6.25.9-76.fc9.i686 breaks wireless with iwl4965 somehow
kernel-2.6.25.9-76.fc9.i686 breaks wireless with iwl4965 somehow
Status: CLOSED DUPLICATE of bug 453390
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
9
i686 Linux
high Severity high
: ---
: ---
Assigned To: John W. Linville
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-03 04:54 EDT by Christoph Höger
Modified: 2008-07-03 13:21 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-07-03 13:21:43 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Log of the Networkmanager session (20.54 KB, text/plain)
2008-07-03 06:05 EDT, Andrea Dell'Amico
no flags Details

  None (edit)
Description Christoph Höger 2008-07-03 04:54:15 EDT
Description of problem:
I have a fine working wireless connection with 
kernel-2.6.25.6-55.fc9.i686 here (sending this report over it right now).
After upgrading the kernel I cannot get a valid ip via dhcp and after a while my
wireless connection disassociates (reason=7 or =3).

Steps to Reproduce:
1. Use NetworkManager to connect to Network
2. wait for association
3. wait for ip
  
Actual results:
timeout

Expected results:
waiting for ip should finish successfull after a while.
Comment 1 Andrea Dell'Amico 2008-07-03 06:02:09 EDT
It happens for me with intel 3945.
I have two access points, one at home and one at work, and the behaviour is the
same.
Authentication is WPA-PSK.
Comment 2 Andrea Dell'Amico 2008-07-03 06:05:54 EDT
Created attachment 310905 [details]
Log of the Networkmanager session

This is the log of the connection failures. I tried 3/4 times. There are
thousands of the following messages:

wlan0: RX deauthentication from 00:16:e0:04:fa:c0 (reason=7)
iwl3945: No space for Tx
iwl3945: Error sending REPLY_LEDS_CMD: iwl3945_enqueue_hcmd failed: -28
wlan0: RX deauthentication from 00:16:e0:04:fa:c0 (reason=7)
iwl3945: No space for Tx
iwl3945: Error sending REPLY_LEDS_CMD: iwl3945_enqueue_hcmd failed: -28
wlan0: RX deauthentication from 00:16:e0:04:fa:c0 (reason=7)
iwl3945: No space for Tx
iwl3945: Error sending REPLY_LEDS_CMD: iwl3945_enqueue_hcmd failed: -28
wlan0: RX deauthentication from 00:16:e0:04:fa:c0 (reason=7)
wlan0: RX deauthentication from 00:16:e0:04:fa:c0 (reason=7)
wlan0: RX deauthentication from 00:16:e0:04:fa:c0 (reason=7)
wlan0: RX deauthentication from 00:16:e0:04:fa:c0 (reason=7)
wlan0: RX deauthentication from 00:16:e0:04:fa:c0 (reason=7)
wlan0: RX deauthentication from 00:16:e0:04:fa:c0 (reason=7)
wlan0: RX deauthentication from 00:16:e0:04:fa:c0 (reason=7)
Comment 3 Chris Schanzle 2008-07-03 13:07:39 EDT
Me too on a Dell Vostro 1700 with iwl3945.

Interestingly, connecting to access point with no encryption worked with no
Rx/Tx errors, and transferred a 15MB file no problem.
Comment 4 John W. Linville 2008-07-03 13:21:43 EDT

*** This bug has been marked as a duplicate of 453390 ***

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