I have a dmesg output from boot through suspend and it's subsequent
resume failure.

To answer some questions in earlier comments (although they were
directed at someone else):

    - This lock up + disk I/O errors happens on every suspend/resume I've tried
      which is about 4 times total in a few hours.  All but the one for this
      dmesg output are simply boot to the desktop, then suspend.

    - The trace attached with this comment involves a hibernate and resume
      before the suspend & resume.  The hibernate and resume seemed to go
      ok.  I'd provide a cleaner trace, but getting any trace was tricky with 
all
      disk I/O reporting errors.

The attached dmesg trace comes from:

    - Boot into Linux.  Start Firefox.
    - Hibernate to disk.
    - Resume from disk.  Seemed to go ok.  Not very pretty though, but
      it did resume back to the working Firefox, after presenting a 
locked-screen
      password dialog box.

    - Switch away from the X login screen to a text console, to reduce the 
chance
      that suspend problems are due to video drivers.  The NVidia driver is 
loaded,
      but similar looking suspend/resume problems have been seen after the
      NVidia driver was uninstalled and the system restarted.  So it does not
      look like a likely cause.

    - Login on the text console, and type "pm-suspend".

    - It suspended ok, though a bit slowly.  Windows suspended quite
slowly too.

    - On resume, text console returned showing I/O error messages, eventually
      ext4 remounted itself read-only, and generally doing anything was tough,
      but the keyboard and console output did work.

    - Used a USB flash key plugged in after resume and raw writing with dd to
      capture the dmesg output.

    - All the problems may be due to SATA I/O errors.


** Attachment added: "suspend_trace.txt"
   http://launchpadlibrarian.net/28791911/suspend_trace.txt

-- 
[Compaq Presario CQ60] suspend/resume problem
https://bugs.launchpad.net/bugs/323733
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to