Dell Latitude 131L - crash when resuming after suspend

Asked by Tom Louwrier on 2009-10-15

hi
I'm running Karmic amd64 on a Dell Latitude 131L, updated at least twice a day.
Unfortunately the suspend/resume is (still) broken. Last time I tried it I closed all apps before choosing 'suspend' in the logout / shutdown menu. I didn't even try just to close the lid.
The suspending appears to work fine, but after opening the lid the screen stays black and the system seems to hang. I get no response from either mouse, keys or power button.
This leaves no other option than to lean on the power button until the system does a hard reboot.

I've uploaded several crash reports on this one, but can't find them now, so I'm making a new bug report.
After the last crash Apport started a report, but quit with the message that 'linux kernel 2.6.31-14-generic is not a generic ubuntu package'
This is strange. Either the latest kernel version is not branded right, or Apport itself has a new bug.

Any more information you might need, just ask, but my command line skills are quite rusty now and never were very good in unix anyway.

cheers
Tom

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu gnome-power-manager Edit question
Assignee:
No assignee Edit question
Solved by:
Tom Louwrier
Solved:
2010-01-27
Last query:
2010-01-27
Last reply:
2010-01-27
Tom Louwrier (tom-louwrier) said : #1

hi

Just found my other bug report and linked this question to it.
It's still not working btw.

enjoy
Tom

Tom Louwrier (tom-louwrier) said : #2

hi

Just found my other bug report and linked this question to it.
It's still not working btw.

enjoy
Tom

Torsten Spindler (tspindler) said : #3

Can you test the latest Lucid build from cdimages.ubuntu.com and see if suspend/resume works with it?

Tom Louwrier (tom-louwrier) said : #4

I'm already on Lucid amd64, have been for a month now.
Suspend/resume started working last week (see bug 466868)
Hibernate/resume is still broken (see bug 447192)

Question is answered as far as I'm concerned, should have been a bug report from the start.

thanx
Tom