Bug 675535 - Suspend 'randomly' causes hard freeze - HP Probook 4510s
Summary: Suspend 'randomly' causes hard freeze - HP Probook 4510s
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: i686
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-02-06 11:58 UTC by Christopher Svanefalk
Modified: 2013-01-10 06:26 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-21 16:28:54 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
My Smolt profile (6.84 KB, text/plain)
2011-02-06 11:58 UTC, Christopher Svanefalk
no flags Details
My lspci output (2.00 KB, text/plain)
2011-02-06 11:58 UTC, Christopher Svanefalk
no flags Details
The 'lspci' output for the effected machine. (2.31 KB, text/plain)
2011-04-20 19:20 UTC, Madison Kelly
no flags Details

Description Christopher Svanefalk 2011-02-06 11:58:09 UTC
Created attachment 477291 [details]
My Smolt profile

Description of problem:

This bug is similar in effect to #649103 (https://bugzilla.redhat.com/show_bug.cgi?id=649103), however, it differs in the following ways:

1. The system can still shutdown properly 100% of the time. Hibernate has not been extensively tested.  
2. Different hardware is being used.
3. Suspend still works sometimes, but it seems go into hard freeze at random.

Version-Release number of selected component (if applicable):
Fedora 14, latest updates as of February 6.

How reproducible:
Should be reproducible on a mint system.

Steps to Reproduce:
1. Start system, login 
2. attempt to suspend in any way
3. --
  
Actual results:
Sometimes (about 50/50 chance of occurence), the system will go into hard freeze when trying to suspend. It manifests in one of two ways:
1. The standard shutdown/suspend screen (fedora logo on a blue backround) stays indefinetly.
2. Screen goes black indefinetly.

In both cases, the only know resolution is a hard reset. No input devices respond.

Expected results:
The system should go into suspend, and wake up again when powerbutton is pressed.

Additional info:
I remember having the exact same problem with Fedora 12 back in the day. The problem persists after a fresh reinstallation, with or without updates.

Comment 1 Christopher Svanefalk 2011-02-06 11:58:50 UTC
Created attachment 477292 [details]
My lspci output

Comment 2 Christopher Svanefalk 2011-02-06 13:05:32 UTC
ADDITIONS:

I realized I mentioned "other hardware without mentioning what it was specifically, apart from the attachments. Thus:

HP ProBook 4510s

Intel Core 2 Duo T6570 2.1 Ghz
Intel HDMA 4500

Other hardware specs can be rooted out on request.

Comment 3 Madison Kelly 2011-04-20 19:20:25 UTC
Created attachment 493589 [details]
The 'lspci' output for the effected machine.

I'm experiencing the same thing on my Lenovo Thinkpad T400s (lspci attached). It's possibly worth noting that this behaviour began just after upgrading (by fresh reinstall) of Ubuntu 10.10. I figured at the time that the problem was with that release, so I switched to Fedora, however the problem has persisted. x86_64 installs with 4 and then 8GB. Perhaps this is something more fundamental?

Comment 4 Madison Kelly 2011-04-20 19:20:58 UTC
Neglected to include the kernel version.

Linux lework.alteeve.com 2.6.35.12-88.fc14.x86_64 #1 SMP Thu Mar 31 21:21:57 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

Comment 5 Thomas White 2011-10-05 09:05:35 UTC
I've been having a very similar problem on my Thinkpad T500 - the "sleep" LED blinks forever while the blue Fedora screen shows, and the only thing possible is to cut the power or press and hold the power button to force the power off.  I thought it was random for a long time, but I've recently noticed a correlation between the problem occurring and my trackball (Logitech Marble Mouse) being plugged in via USB.  I've made sure to unplug the trackball every time before suspending, and I haven't seen the problem for many days now with two suspend cycles per day.

So, if this is affecting you, please report here if it still happens if you're careful to remove all USB devices first.  Watch out for internal USB devices (e.g. my last laptop's wifi and bluetooth adaptor was connected via USB internally) - check with "lsusb".

Comment 6 Christopher Svanefalk 2011-10-11 11:00:49 UTC
Yes, it appears that the problem is a driver-issue. I will see if I can take some time later on to load-unload drivers and see if I can pin it down. Before that, I will upgrade to F16 (stable) and see if it persists though.

Comment 7 Christopher Svanefalk 2011-10-21 11:59:05 UTC
As of F16 Beta, using the same hardware as when I reported the bug, this seems to no longer be an issue. I can suspend and awaken the system without any regular problems.

Comment 8 Dave Jones 2011-10-21 16:28:54 UTC
thanks for testing. If it happens again, feel free to reopen this bug.

Comment 9 Christopher Svanefalk 2011-10-21 16:32:47 UTC
No problem, happy to help.


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