Bug 37832 - pm-suspend causes kernel panic on Thinkpad X200 Tablet
Summary: pm-suspend causes kernel panic on Thinkpad X200 Tablet
Status: CLOSED UNREPRODUCIBLE
Alias: None
Product: Power Management
Classification: Unclassified
Component: Hibernation/Suspend (show other bugs)
Hardware: All Linux
: P1 high
Assignee: power-management_other
URL:
Keywords:
Depends on:
Blocks: 7216
  Show dependency tree
 
Reported: 2011-06-18 21:30 UTC by Dinesh Joshi
Modified: 2012-02-21 03:07 UTC (History)
2 users (show)

See Also:
Kernel Version: 2.6.39
Subsystem:
Regression: No
Bisected commit-id:


Attachments
hardware info (282.02 KB, text/plain)
2011-06-18 21:30 UTC, Dinesh Joshi
Details

Description Dinesh Joshi 2011-06-18 21:30:07 UTC
Created attachment 62742 [details]
hardware info

Please note although I am using Ubuntu, I am running the stock mainline kernel from Ubuntu's kernel ppa.

Description:

On this hardware, when I attempt to suspend to ram, once in a while it leads to a kernel panic.

Steps to Reproduce:

Followed the debugging steps here:
https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume

First:

1. setfont /usr/share/consolefonts/Uni1-VGA8.psf.gz
2. sudo pm-suspend

Then repeated pm-suspend, wakeup cycle at the command line until I got the kernel panic.

Additional info:

I am attaching hwinfo output and screenshots of the actual panic.

Note: I have a sucky iPhone cam and the font on my screen was tiny so I need to attach several pictures.
Comment 2 Dinesh Joshi 2011-06-18 21:43:47 UTC
The last one should've been: http://ustor.me/get.php?fsn=0ecc1964b765e1951df9217e2433eafd
Comment 3 Zhang Rui 2012-01-18 05:20:52 UTC
It's great that the kernel bugzilla is back.

Can you please verify if the problem still exists in the latest upstream
kernel?
Comment 4 Dinesh Joshi 2012-02-20 09:44:25 UTC
This bug doesn't seem to exist on the latest upstream. I am using the Ubuntu precompiled mainline kernel.

Thanks.
Comment 5 Zhang Rui 2012-02-21 03:07:15 UTC
Okay.
Bug closed.
please feel free to re-open it if you can reproduce the problem again.

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