F11 iwlagn errors on Thinkpad W700

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I apologize in advance for what promises to be a lengthy post. Suggest heavy editing in any replies.

Since installing F11 on my Thinkpad W700 I've had a chronic problem with the wireless disconnecting after a random time interval. It was rock solid with F10. I've noticed a number of kernel errors in my e-mail logs. The most prolific example was yesterday:
---------------------- Kernel Begin -----------------------

WARNING:  Kernel Errors Present
   iwlagn: Error sending REPLY_SC ...:  1 Time(s)
   iwlagn: Error sending REPLY_TX ...:  5 Time(s)
   iwlagn: Error sending Sensitiv ...:  1 Time(s)
   iwlagn: Microcode SW error detected.  Resta ...:  19 Time(s)

---------------------- Kernel End -------------------------
I just now updated to the 2.6.29.6-217.2.7 kernel. --changelog says John Linville patched iwlwifi in the 217.2.5 kernel on Wednesday to fix a TX queue race. I pulled my eth0 cable, reset the NetworkManager wireless connection, and started a ping to my default gateway. The wifi connection lasted 11 pings, so John's patch didn't fix this problem.

When the ping stopped I saw the following in /var/log/messages:
Aug 16 15:57:10 tiger kernel: iwlagn: Microcode SW error detected.  Restarting 0x82000000.
Aug 16 15:57:10 tiger kernel: iwlagn: No space for Tx
Aug 16 15:57:10 tiger kernel: iwlagn: Error sending SENSITIVITY_CMD failed
Aug 16 15:57:10 tiger kernel: iwlagn: SENSITIVITY_CMD failed: -28
Aug 16 15:57:10 tiger kernel: Registered led device: iwl-phy0:radio
Aug 16 15:57:10 tiger kernel: Registered led device; iwl-phy0:assoc
Aug 16 15:57:10 tiger kernel: Registered led device: iwl-phy0:RX
Aug 16 15:57:10 tiger kernel: Registered led device: iwl-phy0:TX
When I click on the NetworkManager button to reset the wireless connection /var/log/messages reports a very chatty but normal looking restart:
Aug 16 16:03:46 tiger NetworkManager: <info> (wlan0): device state change: 8 -> 3 (reason 0)
Aug 16 16:03:46 tiger NetworkManager: <info> (wlan0): deactivating device (reason: 0)
Aug 16 16:03:46 tiger NetworkManager: <WARN> check_one_route(): (wlan0) error - 34 returned from rtnl_route_del(): Success#012
Aug 16 16:03:46 tiger avahi-daemon[1901]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.7.
Aug 16 16:03:46 tiger avahi-daemon[1901]: Interface wlan0.IPv4 no longer relevan for mDNS.
Aug 16 16:03:46 tiger NetworkManager: <info> Activation (wlan0) starting connection 'Auto <SSID>'
Aug 16 16:03:46 tiger NetworkManager: <info> (wlan0): device state change: 3 -> 4 (reason 0)
Aug 16 16:03:46 tiger NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Aug 16 16:03:46 tiger NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Aug 16 16:03:46 tiger NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Aug 16 16:03:46 tiger NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Aug 16 16:03:46 tiger NetworkManager: <info> (wlan0): supplicant connection state:  completed -> disconnected
Aug 16 16:03:46 tiger NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Aug 16 16:03:46 tiger NetworkManager: <info> (wlan0): device state change: 4 -> 5 (reason 0)
Aug 16 16:03:46 tiger NetworkManager: <info> Activation (wlan0/wireless): connection 'Auto <SSID>' requires no security.  No secrets needed.
Aug 16 16:03:46 tiger NetworkManager: <info> Config: added 'ssid' value '<SSID>'
Aug 16 16:03:46 tiger NetworkManager: <info> Config: added 'scan_ssid' value '1'
Aug 16 16:03:46 tiger NetworkManager: <info> Config: added 'key_mgmt' valuen 'NONE'
Aug 16 16:03:46 tiger NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Aug 16 16:03:46 tiger NetworkManager: <info> Config: set interface ap_scan to 1
Aug 16 16:03:46 tiger NetworkManager: <info> (wlan0: supplicant connection state:  disconnected -> scanning
Aug 16 16:03:48 tiger ntpd[2263]: Deleting interface #10 wlan0, 192.168.1.7#123, interface stats: received=2, sent=18, dropped-0, active_time=664 secs
Aug 16 16:03:49 tiger NetworkManager: <info> (wlan0): supplicant connection state:  scanning -> associating
Aug 16 16:03:49 tiger NetworkManager: <info> (wlan0): supplicant connection state:  associating -> associated
Aug 16 16:03:49 tiger NetworkManager: <info> (wlan0): supplicant connection state:  associated -> completed
Aug 16 16:03:49 tiger NetworkManager: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network '<SSID>'.
Aug 16 16:03:49 tiger NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Aug 16 16:03:49 tiger NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Aug 16 16:03:49 tiger NetworkManager: <info> (wlan0): device state change: 5 -> 7 (reason 0)
Aug 16 16:03:49 tiger NetworkManager: <info> Activation (wlan0) Beginning DHCP transaction.
Aug 16 16:03:49 tiger NetworkManager: <info> dhclient started with pid 4089
Aug 16 16:03:49 tiger NetworkManager: <info>Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Aug 16 16:03:49 tiger dhclient: Internet Systems Consortium DHCP Client 4.1.0
Aug 16 16:03:49 tiger dhclient: Copyright 2004-2008 Internet Systems Consortium.
Aug 16 16:03:49 tiger dhclient: All rights reserved.
Aug 16 16:03:49 tiger dhclient: For info, please visit http://www.isc.org/sw.dhcp/
Aug 16 16:03:49 tiger dhclient: 
Aug 16 16:03:49 tiger NetworkManager: <info>  DHCP: device wlan state changed normal exit -> preinit
Aug 16 16:03:49 tiger dhclient: Listening on LPF/wlan0/<MAC>
Aug 16 16:03:49 tiger dhclient: Sending on   LPF/wlan0/<MAC>
Aug 16 16:03:49 tiger dhclient: Sending on   Socket/fallback
Aug 16 16:03:50 tiger dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Aug 16 16:03:53 tiger dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Aug 16 16:03:53 tiger dhclient: DHCPACK from 192.168.1.2
Aug 16 16:03:53 tiger NetworkManager: <info>  DHCP: device wlan0 state changed preinit -> reboot
Aug 16 16:03:53 tiger NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP configure Get) scheduled...
Aug 16 16:03:53 tiger NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP Configure Get) started...
Aug 16 16:03:53 tiger NetworkManager: <info>    address 192.168.1.7
Aug 16 16:03:53 tiger NetworkManager: <info>    prefix 24 (255.255.255.0)
Aug 16 16:03:53 tiger NetworkManager: <info>    gateway 192.168.1.1
Aug 16 16:03:53 tiger NetworkManager: <info>    nameserver 'xxx.xxx.xxx.xxx'
Aug 16 16:03:53 tiger NetworkManager: <info>    nameserver 'yyy.yyy.yyy.yyy'
Aug 16 16:03:53 tiger NetworkManager: <info>    nameserver 'zzz.zzz.zzz.zzz'
Aug 16 16:03:53 tiger NetworkManager: <info>    domain name '<privatedomainname>'
Aug 16 16:03:53 tiger NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Aug 16 16:03:53 tiger NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP Configure Get)  complete.
Aug 16 16:03:53 tiger NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
Aug 16 16:03:53 tiger avahi-daemon[1901]: Joining mDNS multicast group on interface wlan0.IPv4 with 192.168.1.7.
Aug 16 16:03:53 tiger avahi-daemon[1901]: Registering new address record for 192.168.1.7 on wlan0.IPv4.
Aug 16 16:03:53 tiger dhclient: bound to 192.168.1.7 -- renewal in 2727 seconds.
Aug 16 16:03:54 tiger NetworkManager: <info>  (wlan0): device state change: 7 -> 8 (reason 0)
Aug 16 16:03:54 tiger NetworkManager: <info>  Policy set 'Auto <SSID>' (wlan0) as default for routing and DNS.
Aug 16 16:03:54 tiger NetworkManager: <info>  Activation (wlan0) successful, device activated.
Aug 16 16:03:54 tiger NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
Aug 16 16:03:54 tiger ntpd02263]: Listening on interface #11 wlan0, 192.168.1.7#123 Enabled
About a half hour later the connection failed with the same log entries:
Aug 16 16:45:25 tiger kernel: iwlagn: Microcode SW error detected.  Restarting 0x82000000.
Aug 16 16:45:25 tiger kernel: iwlagn: No space for Tx
Aug 16 16:45:25 tiger kernel: iwlagn: Error sending Sensitivity_CMD: enqueue_hcmd failed: -28
Aug 16 16:45:25 tiger kernel: iwlagn: SENSITIVITY_CMD failed
Aug 16 16:45:25 tiger kernel: Registered led device: iwl-phy0:radio
Aug 16 16:45:25 tiger kernel: Registered led device: iwl-phy0:assoc
Aug 16 16:45:25 tiger kernel: Registered led device: iwl-phy0:RX
Aug 16 16:45:25 tiger kernel: Registered led device: iwl-phy0:TX
Has anyone else running seen this misbehavior on a W700 running F11?

--Doc Savage
  Fairview Heights, IL

-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora Magazine]     [Fedora News]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux