[Toshiba Satellite U400-112] Ubuntu does not work after hibernation

[Alex]

Doesn't work: usb mouse, usb ports, monitor, ethernet and don't responding to any key combination.
The system is completely inactive.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-23-generic 3.13.0-23.45
ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
Uname: Linux 3.13.0-23-generic x86_64
ApportVersion: 2.14.1-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: alexandr 5294 F.... pulseaudio
 /dev/snd/pcmC0D0p: alexandr 5294 F...m pulseaudio
CurrentDesktop: Unity
Date: Mon Apr 7 18:55:14 2014
HibernationDevice: RESUME=UUID=b24a6988-ef72-4a27-9d47-eaae3b40da79
InstallationDate: Installed on 2014-04-05 (1 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140405)
MachineType: TOSHIBA Satellite U400
ProcEnviron:
 LANGUAGE=ru
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=a2542225-0e12-4374-9e06-517a541a1421 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-23-generic N/A
 linux-backports-modules-3.13.0-23-generic N/A
 linux-firmware 1.127
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: yes
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/25/2010
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V4.70
dmi.board.name: Satellite U400
dmi.board.vendor: TOSHIBA
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnTOSHIBA:bvrV4.70:bd10/25/2010:svnTOSHIBA:pnSatelliteU400:pvrPSU40E-00E00FRU:rvnTOSHIBA:rnSatelliteU400:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.name: Satellite U400
dmi.product.version: PSU40E-00E00FRU
dmi.sys.vendor: TOSHIBA

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.14 kernel[0].

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.14-trusty/

[Alex (salamonovich)]

kernel-bug-exists-upstream

[penalvch (penalvch)]

Alex, could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc1-trusty/ and advise to the results?

[Alex (salamonovich)]

Christopher, kernel 3.15 does not work after hibernation.

[penalvch (penalvch)]

Alex, did this problem not occur in a release prior to Trusty?

[Alex (salamonovich)]

Christopher, yes, this is problem only in Trusty.
Still a problem with the fan speed after 3.2 kernel.

[penalvch (penalvch)]

Alex, just to clarify, this issue is reproducible as far back as the 3.2 kernel (Precise 12.04.0)?

Was this reproducible in a kernel prior to 3.2?

[Alex (salamonovich)]

Christopher, no. Only in trusty.

[penalvch (penalvch)]

Alex, the next step is to fully commit bisect from Saucy to Trusty, in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

[Alex (salamonovich)]

Christopher, today I'm install lubuntu Trusty and there were no problems with hibernation.

[penalvch (penalvch)]

Alex, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1303873/comments/12 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.