Bug 744524 - Toshiba R850 will not wake from suspend
Summary: Toshiba R850 will not wake from suspend
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-09 08:06 UTC by Daniel Rowe
Modified: 2011-11-10 04:23 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-10 04:23:52 UTC
Type: ---


Attachments (Terms of Use)
pm-suspend.log (5.02 KB, text/x-log)
2011-10-09 08:06 UTC, Daniel Rowe
no flags Details
dmesg (77.87 KB, text/plain)
2011-10-09 08:09 UTC, Daniel Rowe
no flags Details
lspci -vv (34.74 KB, text/plain)
2011-10-09 08:10 UTC, Daniel Rowe
no flags Details

Description Daniel Rowe 2011-10-09 08:06:18 UTC
Created attachment 527079 [details]
pm-suspend.log

Description of problem:

Toshiba R850 will not wake from suspend. Seems to go into suspend OK but when waking up after a couple of seconds the fan just run at what seems maximum and it stays in this state until hard reboot (hold power button down).

Version-Release number of selected component (if applicable):

2.6.40.6-0.fc15.x86_64

How reproducible:

Every time.

Steps to Reproduce:
1. Suspend the machine.
2. Wake up.
  
Actual results:

Will not wake.

Expected results:

Wakes up correctly.

Comment 1 Daniel Rowe 2011-10-09 08:09:03 UTC
Created attachment 527081 [details]
dmesg

Comment 2 Daniel Rowe 2011-10-09 08:10:45 UTC
Created attachment 527082 [details]
lspci -vv

Comment 3 Daniel Rowe 2011-11-07 13:04:05 UTC
I have managed to fix this issue:

http://thecodecentral.com/2011/01/18/fix-ubuntu-10-10-suspendhibernate-not-working-bug

Comment 4 Daniel Rowe 2011-11-10 04:23:52 UTC
Tested this in Fedora 16 and there is no issues out of the box. So closing the bug.


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