8086:4238 [Lenovo ThinkPad T430 2347] Wireless network doesn't resume after suspend/resume (sometimes)

Bug #1089856 reported by Stefan Freyr
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

It seems that sometimes my wireless network interface disappears after suspend/resume.

When this happens, listing hardware with lshw does not show the wireless adapter.

Reloading the wireless kernel module drivers does not work!
The command I'm using to do that is the following:
sudo rmmod iwlwifi mac80211 cfg80211 ; sudo modprobe cfg80211 ; sudo modprobe iwlwifi ; sudo modprobe mac80211

And finally (and this is quite weird to me), a "soft restart" of the computer does not work! That is, selecting the "Restart" option from the logout menu doesn't work. The last time this happened I tried a "soft restart" 4 times and every time the wireless interface did not come up. However, as soon as I did a "hard reboot" (selecting Shutdown from the logout menu, waiting a few seconds and then starting the computer again) fixed the problem right away.

This probably indicates that the wireless controller itself (hardware) is in some undefined state.

I tried adding adding the following line to /etc/pm/config.d/config:
SUSPEND_MODULES="$SUSPEND_MODULES iwlwifi"

That has not solved the problem.

As I stated, I don't think this is happening every time I suspend/resume, but when it happens I consistently need a "hard reboot" to fix the problem and get my wireless interface up again. I will do a few suspend/resume cycles later to try to see how frequently this happens.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-19-generic 3.5.0-19.30
ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
Uname: Linux 3.5.0-19-generic x86_64
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: stefan 2112 F.... pulseaudio
CRDA:
 country IS:
  (2402 - 2482 @ 40), (N/A, 20)
  (5170 - 5250 @ 40), (N/A, 20)
  (5250 - 5330 @ 40), (N/A, 20), DFS
  (5490 - 5710 @ 40), (N/A, 27), DFS
Date: Thu Dec 13 10:35:51 2012
HibernationDevice: RESUME=UUID=339a99de-eef3-452e-b55c-a229bee214e5
InstallationDate: Installed on 2012-09-20 (83 days ago)
InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905)
MachineType: LENOVO 2347W2U
MarkForUpload: True
ProcEnviron:
 LANGUAGE=
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-19-generic root=UUID=c8916e6c-a99f-43f1-9d8c-c1daf21fedac ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-19-generic N/A
 linux-backports-modules-3.5.0-19-generic N/A
 linux-firmware 1.95
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/25/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: G1ET41WW (1.16 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2347W2U
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrG1ET41WW(1.16):bd05/25/2012:svnLENOVO:pn2347W2U:pvrThinkPadT430:rvnLENOVO:rn2347W2U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2347W2U
dmi.product.version: ThinkPad T430
dmi.sys.vendor: LENOVO

Revision history for this message
Stefan Freyr (stefan-freyr) wrote :
Revision history for this message
Stefan Freyr (stefan-freyr) wrote :

I should mention that this bug was reported when the wireless interface was working. If it helps I can try to get the problem to appear and run some commands and send in the result, I will just need some instructions on what exactly I should do.

Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Stefan Freyr (stefan-freyr) wrote : Re: Wireless network doesn't resume after suspend/resume (sometimes)

I did two suspend/resume cycles. After the first one everything was OK, so I can confirm now for sure that this does not happen always. After the second one I got this problem again and now I do not have wireless but I have a wired connection.

I'm attaching the output of lspci and dmesg now since the problem is "active".

Revision history for this message
Stefan Freyr (stefan-freyr) wrote :

Here's the output of lspci -vv when the problem is active.

The following line seems _just a little_ suspicious:
03:00.0 Network controller: Intel Corporation Centrino Ultimate-N 6300 (rev ff) (prog-if ff)
        !!! Unknown header type 7f

Revision history for this message
Stefan Freyr (stefan-freyr) wrote :

updated the lspci attachment (using options -vvnn).

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.7 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-raring/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Stefan Freyr (stefan-freyr) wrote :

I've installed the 3.7.0 kernel and will do as much testing as I can to try to produce the bug. Unfortunately, since it isn't predictable and not always reproducible we'll just have to wait and see.

Revision history for this message
Stefan Freyr (stefan-freyr) wrote :

I've been using 3.7.0-030700-generic for a while now and was starting to think that the bug was fixed but unfortunately it isn't. This happened now with the same symptoms ("lspci -vvnn" gives me the "!!! Unknown header type 7f" error message).

Don't know if it helps but it feels like this is likelier to happen if the computer has been sleeping for some amount of time (overnight or more). This may be a coincidence though.

I'm trying to add the tag 'kernel-bug-exists-upstream' but I can't figure out how to do it. Hopefully it will be possible if I change the state to 'Confirmed'.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-bug-exists-upstream
Revision history for this message
penalvch (penalvch) wrote :

Stefan Freyr, as per http://support.lenovo.com/en_US/downloads/default.page? an update is available for your BIOS (2.56). If you update to this, does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Thank you for your understanding.

tags: added: bios-outdated-2.56 kernel-bug-exists-upstream-v3.7 needs-upstream-testing regression-potential
removed: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
summary: - Wireless network doesn't resume after suspend/resume (sometimes)
+ [Lenovo ThinkPad T430 2347]Wireless network doesn't resume after
+ suspend/resume (sometimes)
summary: - [Lenovo ThinkPad T430 2347]Wireless network doesn't resume after
- suspend/resume (sometimes)
+ 8086:4238 [Lenovo ThinkPad T430 2347] Wireless network doesn't resume
+ after suspend/resume (sometimes)
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.