Hi. 32 bit on a laptop with intel graphics hardware.
Just had a kernel panic when resuming from a suspend to RAM using the new 2.6.38. First problem with suspend on this computer in nearly three years.

Right now I have some work to do so back to the last 2.6.37 kernel. I'll give some more info later.

_________________There are some who call me Tim

Last edited by timrichardson on 14.04.2011, 11:30; edited 3 times in total

with 2.6.38-0.slh.2-aptosid-686 I get a different problem with resuming. After resume, I see the screen saver and the unlock dialog for around three seconds, and then the machine locks up (three times successively so it's reproducible). I can't get any reaction so I force the machine to power down.
I have Intel GM965. The power supply is connected while I do this.
I don't know where to find log messages that may help. dmesg seems to have nothing useful, same with pm-suspend.log

_________________There are some who call me Tim

timrichardson

Post subject:Posted: 17.03.2011, 01:05

Joined: 2010-09-12
Posts: 66
Location: Melbourne
Status: Offline

Resuming from a suspend to disk (hibernate) works, unlike resuming from RAM.

_________________There are some who call me Tim

slh

Post subject:Posted: 17.03.2011, 01:15

Joined: 2010-08-25
Posts: 954

Status: Offline

That is actually a quite rare combination, as suspend to disk is usually more likely to be affected... However at this moment, nothing really strikes out (an ICH6/ i945GME systems suspends and wakes up fine for me, although I rarely use suspend). The big problem with suspend related issues is how tightly these issues are coupled to the hardware and the running BIOS implementation, which are mostly hard to reproduce and debug.

DeepDayze

Post subject:Posted: 17.03.2011, 01:21

Joined: 2010-09-11
Posts: 616
Location: USA
Status: Offline

Do you have the latest BIOS?

timrichardson

Post subject:Posted: 17.03.2011, 10:56

Joined: 2010-09-12
Posts: 66
Location: Melbourne
Status: Offline

BIOS update made no difference. What logfiles may be helpful?

_________________There are some who call me Tim

timrichardson

Post subject:Posted: 17.03.2011, 11:19

Joined: 2010-09-12
Posts: 66
Location: Melbourne
Status: Offline

I dropped down to init 3 and did a pm-suspend.
On resume, the console had errors and a kernel panic.
They look like dmesg errors, time stamps like 90.773041 bad_area_nosemaphore messages.
But upon reboot, I couldn't see where these message may be.

_________________There are some who call me Tim

DeepDayze

Post subject:Posted: 17.03.2011, 14:06

Joined: 2010-09-11
Posts: 616
Location: USA
Status: Offline

those semaphore messages could have something to do with the removal of the BKL

timrichardson

Post subject:Posted: 18.03.2011, 08:16

Joined: 2010-09-12
Posts: 66
Location: Melbourne
Status: Offline

well, 2.6.38-0.slh.3-aptosid-686
still kernel panics, although now I get a flashing LED to accompany the crash.