kernel-packages team mailing list archive

Thread
Date
[Bug 1249765] Re: 8086:4222 [Acer Aspire 5670] iwl3945 resets wireless connection frequently

To: kernel-packages@xxxxxxxxxxxxxxxxxxx
From: "Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>
Date: Sat, 23 Aug 2014 15:38:54 -0000
Reply-to: Bug 1249765 <1249765@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx
Ivan Kay, thank you for your comment. Unfortunately, this bug report is not scoped to you, or your problem. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug
report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1249765

Title:
  8086:4222 [Acer Aspire 5670] iwl3945 resets wireless connection
  frequently

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  The wireless connection keeps getting reset and it has become difficult to Skype or to watch streaming video from certain sites(comdey central or Hulu).
  This bug has existed for years, but I just havent gotten around to reporting it.

  Around the time when the connection drops I see the following
  messages:

  Nov 10 07:22:27 Vish-Aspire-5670 kernel: [28086.352046] iwl3945 0000:03:00.0: Queue 4 stuck for 2500 ms.
  Nov 10 07:22:27 Vish-Aspire-5670 kernel: [28086.352061] iwl3945 0000:03:00.0: On demand firmware reload
  Nov 10 07:22:27 Vish-Aspire-5670 kernel: [28086.388398] ieee80211 phy0: Hardware restart was requested
  Nov 10 07:22:30 Vish-Aspire-5670 kernel: [28090.128748] wlan0: deauthenticated from 00:7f:28:5f:b0:8b (Reason: 6)
  Nov 10 07:22:30 Vish-Aspire-5670 wpa_supplicant[820]: wlan0: CTRL-EVENT-DISCONNECTED bssid=00:7f:28:5f:b0:8b reason=6
  Nov 10 07:22:30 Vish-Aspire-5670 kernel: [28090.156444] cfg80211: Calling CRDA to update world regulatory domain
  Nov 10 07:22:31 Vish-Aspire-5670 NetworkManager[760]: <info> (wlan0): supplicant interface state: completed -> disconnected
  Nov 10 07:22:31 Vish-Aspire-5670 kernel: [28090.208893] cfg80211: World regulatory domain updated:
  Nov 10 07:22:31 Vish-Aspire-5670 kernel: [28090.208902] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Nov 10 07:22:31 Vish-Aspire-5670 kernel: [28090.208908] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
  Nov 10 07:22:31 Vish-Aspire-5670 kernel: [28090.208914] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
  Nov 10 07:22:31 Vish-Aspire-5670 kernel: [28090.208920] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
  Nov 10 07:22:31 Vish-Aspire-5670 kernel: [28090.208925] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
  Nov 10 07:22:31 Vish-Aspire-5670 kernel: [28090.208930] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
  Nov 10 07:22:31 Vish-Aspire-5670 NetworkManager[760]: <info> (wlan0): supplicant interface state: disconnected -> scanning
  Nov 10 07:22:33 Vish-Aspire-5670 wpa_supplicant[820]: wlan0: SME: Trying to authenticate with 00:7f:28:5f:b0:8b (SSID='9R5WB' freq=2437 MHz)
  Nov 10 07:22:33 Vish-Aspire-5670 kernel: [28092.265046] wlan0: authenticate with 00:7f:28:5f:b0:8b
  Nov 10 07:22:33 Vish-Aspire-5670 kernel: [28092.267341] wlan0: send auth to 00:7f:28:5f:b0:8b (try 1/3)
  Nov 10 07:22:33 Vish-Aspire-5670 wpa_supplicant[820]: wlan0: Trying to associate with 00:7f:28:5f:b0:8b (SSID='9R5WB' freq=2437 MHz)
  Nov 10 07:22:33 Vish-Aspire-5670 NetworkManager[760]: <info> (wlan0): supplicant interface state: scanning -> associating
  Nov 10 07:22:33 Vish-Aspire-5670 kernel: [28092.269131] wlan0: authenticated
  Nov 10 07:22:33 Vish-Aspire-5670 kernel: [28092.273552] wlan0: associate with 00:7f:28:5f:b0:8b (try 1/3)
  Nov 10 07:22:33 Vish-Aspire-5670 kernel: [28092.276794] wlan0: RX AssocResp from 00:7f:28:5f:b0:8b (capab=0x431 status=0 aid=1)
  Nov 10 07:22:33 Vish-Aspire-5670 kernel: [28092.278603] wlan0: associated
  Nov 10 07:22:33 Vish-Aspire-5670 kernel: [28092.278711] cfg80211: Calling CRDA for country: US
  Nov 10 07:22:33 Vish-Aspire-5670 wpa_supplicant[820]: wlan0: Associated with 00:7f:28:5f:b0:8b
  Nov 10 07:22:33 Vish-Aspire-5670 NetworkManager[760]: <info> (wlan0): supplicant interface state: associating -> associated
  Nov 10 07:22:33 Vish-Aspire-5670 kernel: [28092.287398] cfg80211: Regulatory domain changed to country: US
  Nov 10 07:22:33 Vish-Aspire-5670 kernel: [28092.287408] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Nov 10 07:22:33 Vish-Aspire-5670 kernel: [28092.287414] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
  Nov 10 07:22:33 Vish-Aspire-5670 kernel: [28092.287420] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
  Nov 10 07:22:33 Vish-Aspire-5670 kernel: [28092.287425] cfg80211:   (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
  Nov 10 07:22:33 Vish-Aspire-5670 kernel: [28092.287431] cfg80211:   (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
  Nov 10 07:22:33 Vish-Aspire-5670 kernel: [28092.287436] cfg80211:   (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
  Nov 10 07:22:33 Vish-Aspire-5670 kernel: [28092.287441] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
  Nov 10 07:22:33 Vish-Aspire-5670 kernel: [28092.287447] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm)
  Nov 10 07:22:35 Vish-Aspire-5670 wpa_supplicant[820]: wlan0: WPA: Key negotiation completed with 00:7f:28:5f:b0:8b [PTK=CCMP GTK=CCMP]
  Nov 10 07:22:35 Vish-Aspire-5670 wpa_supplicant[820]: wlan0: CTRL-EVENT-CONNECTED - Connection to 00:7f:28:5f:b0:8b completed (reauth) [id=0 id_str=]
  Nov 10 07:22:35 Vish-Aspire-5670 NetworkManager[760]: <info> (wlan0): supplicant interface state: associated -> completed
  Nov 10 07:24:06 Vish-Aspire-5670 kernel: [28185.200062] iwl3945 0000:03:00.0: Error sending C_RXON: time out after 500ms.
  Nov 10 07:24:06 Vish-Aspire-5670 kernel: [28185.200072] iwl3945 0000:03:00.0: Error clearing ASSOC_MSK on current configuration (-110).
  Nov 10 07:24:06 Vish-Aspire-5670 kernel: [28185.808061] iwl3945 0000:03:00.0: Error sending C_TX_PWR_TBL: time out after 500ms.
  Nov 10 07:24:07 Vish-Aspire-5670 kernel: [28186.604064] iwl3945 0000:03:00.0: Error sending C_RXON: time out after 500ms.
  Nov 10 07:24:07 Vish-Aspire-5670 kernel: [28186.604075] iwl3945 0000:03:00.0: Error clearing ASSOC_MSK on current configuration (-110).
  Nov 10 07:24:07 Vish-Aspire-5670 kernel: [28186.952035] iwl3945 0000:03:00.0: Queue 4 stuck for 2476 ms.
  Nov 10 07:24:07 Vish-Aspire-5670 kernel: [28186.952045] iwl3945 0000:03:00.0: On demand firmware reload
  Nov 10 07:24:08 Vish-Aspire-5670 kernel: [28187.212044] iwl3945 0000:03:00.0: Error sending C_TX_PWR_TBL: time out after 500ms.
  Nov 10 07:24:08 Vish-Aspire-5670 kernel: [28187.254999] ieee80211 phy0: Hardware restart was requested
  Nov 10 07:24:14 Vish-Aspire-5670 kernel: [28193.320048] iwl3945 0000:03:00.0: Queue 2 stuck for 2064 ms.
  Nov 10 07:24:14 Vish-Aspire-5670 kernel: [28193.320059] iwl3945 0000:03:00.0: On demand firmware reload
  Nov 10 07:24:14 Vish-Aspire-5670 kernel: [28193.358152] ieee80211 phy0: Hardware restart was requested

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-13-generic 3.11.0-13.20
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic i686
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC1:  vishnoo    1890 F.... pulseaudio
   /dev/snd/controlC0:  vishnoo    1890 F.... pulseaudio
   /dev/snd/pcmC0D0p:   vishnoo    1890 F...m pulseaudio
  Date: Sun Nov 10 07:31:38 2013
  HibernationDevice: RESUME=UUID=9197e732-caa4-4ab8-878a-015dff5c048e
  InstallationDate: Installed on 2012-06-15 (513 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
  MachineType: Acer, inc. Aspire 5670
  MarkForUpload: True
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=332eba8f-42fa-40ea-b285-39f38e995722 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-13-generic N/A
   linux-backports-modules-3.11.0-13-generic  N/A
   linux-firmware                             1.116
  SourcePackage: linux
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (23 days ago)
  dmi.bios.date: 01/12/07
  dmi.bios.vendor: Acer
  dmi.bios.version: v1.3239
  dmi.board.name: Bodensee
  dmi.board.vendor: Acer, Inc.
  dmi.board.version: Not Applicable
  dmi.chassis.type: 1
  dmi.chassis.vendor: Acer, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: dmi:bvnAcer:bvrv1.3239:bd01/12/07:svnAcer,inc.:pnAspire5670:pvrNotApplicable:rvnAcer,Inc.:rnBodensee:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A:
  dmi.product.name: Aspire 5670
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer, inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1249765/+subscriptions
References

[Bug 1249765] [NEW] iwl3945 resets wireless connection frequently
From: Vish, 2013-11-10