Bug 268641 - Suspend fails to resume, results in unbootable machine
Suspend fails to resume, results in unbootable machine
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
i686 Linux
medium Severity high
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-08-30 15:38 EDT by Boris Goldowsky
Modified: 2007-12-30 12:06 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-12-30 12:06:27 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Boris Goldowsky 2007-08-30 15:38:07 EDT
Description of problem:

On Dell Inspiron 9300
Suspended, then opened lid to resume - got power/disk hardware lamp indications
but black screen and non-responsive to keyboard.

Cycled power off then on.  Now boot process repeatably fails with messages:
Unable to access resume device (/dev/sda5)
mount: could not find filesystem '/dev/root'
switchroot: mount failed: No such file or directory

Then nothing.  Machine is apparently unbootable short of using a rescue disk.
Comment 1 Jon Stanley 2007-12-30 00:36:45 EST

I'm reviewing this bug as part of the kernel bug triage project, an attempt to
isolate current bugs in the Fedora kernel.


I am CC'ing myself to this bug and will try and assist you in resolving it if I can.

There hasn't been much activity on this bug for a while. Could you tell me if
you are still having problems with the latest kernel?

If the problem no longer exists then please close this bug or I'll do so in a
few days if there is no additional information lodged.
Comment 2 Boris Goldowsky 2007-12-30 08:29:57 EST
Sorry, I no longer have access to that laptop to test on, so I can't say whether
this is still an issue.
Comment 3 Jon Stanley 2007-12-30 12:06:27 EST
In that case, I'm going to close this as INSUFFICIENT_DATA.  Feel free to reopen
if the problem recurs.

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