Skip to contentSkip to conversation

Suspend/Resume/Hibernation - bisecting or bug-logs?

DISCUSSION Kristoffer Ericson 4 participants 5 messages Nov 16, 2007 – Nov 25, 2007

lore
Share & tools
lore
#0 lore raw

Greetings,

Ive been following your discussion and documentation efforts concerning pm in the kernel. This has in the past been a gray area which was hard to find information about so kudos.

I maintain 2 handheld platforms that would benefit greatly from implementing proper pm (mainly suspend) but Im having problems bugtracking it. Currently the system tries to suspend but fails somewhere and then tries to resume (which fails). The end result however is that Im unable to see anything (bugmessages...) since the video driver gets deactivated by pm.

My question is this: Is bisecting (turning off device support in kernel until it works) the best approach when bugtracking pm suspend? Or is there any other logging system that I can use?

Signature · 1 line
Kristoffer Ericson <[email protected]>
#1 lore raw
Quoted 13 lines · Kristoffer Ericson

Greetings,

Ive been following your discussion and documentation efforts concerning pm in the kernel. This has in the past been a gray area which was hard to find information about so kudos.

I maintain 2 handheld platforms that would benefit greatly from implementing proper pm (mainly suspend) but Im having problems bugtracking it. Currently the system tries to suspend but fails somewhere and then tries to resume (which fails). The end result however is that Im unable to see anything (bugmessages...) since the video driver gets deactivated by pm.

Quoted 4 lines

My question is this: Is bisecting (turning off device support in kernel until it works) the best approach when bugtracking pm suspend? Or is there any other logging system that I can use?

Good question. I could use advice too :)

Bisecting is good only if you have known good and known bad versions. From your description it sounds like it has never worked - so bisecting won't help. Also sometimes bisecting hits way too large commit (this happened to me when ACPI replaced mutex with spinlock).

#2 lore raw
Quoted 20 lines · Andrey Borzenkov
Quoted 13 lines · Kristoffer Ericson

Greetings,

Ive been following your discussion and documentation efforts concerning pm in the kernel. This has in the past been a gray area which was hard to find information about so kudos.

I maintain 2 handheld platforms that would benefit greatly from implementing proper pm (mainly suspend) but Im having problems bugtracking it. Currently the system tries to suspend but fails somewhere and then tries to resume (which fails). The end result however is that Im unable to see anything (bugmessages...) since the video driver gets deactivated by pm.

Quoted 4 lines

My question is this: Is bisecting (turning off device support in kernel until it works) the best approach when bugtracking pm suspend? Or is there any other logging system that I can use?

Quoted 6 lines

Good question. I could use advice too :)

Bisecting is good only if you have known good and known bad versions. From your description it sounds like it has never worked - so bisecting won't help. Also sometimes bisecting hits way too large commit (this happened to me when ACPI replaced mutex with spinlock).

If I understand the original post correctly, Kristoffer didn't mean searching for a bad patch using bisection. :-)

#3 lore raw
In reply to Kristoffer Ericson
Quoted 5 lines · Kristoffer Ericson

Greetings,

Ive been following your discussion and documentation efforts concerning pm in the kernel. This has in the past been a gray area which was hard to find information about so kudos.

Thanks!

Quoted 5 lines

I maintain 2 handheld platforms that would benefit greatly from implementing proper pm (mainly suspend) but Im having problems bugtracking it. Currently the system tries to suspend but fails somewhere and then tries to resume (which fails). The end result however is that Im unable to see anything (bugmessages...) since the video driver gets deactivated by pm.

That's bad.

Quoted 3 lines

My question is this: Is bisecting (turning off device support in kernel until it works) the best approach when bugtracking pm suspend? Or is there any other logging system that I can use?

Well, various approaches are possible.

First, you can build as many drivers as possible as modules and boot with init=/bin/bash . Then, try to suspend and resume and if that fails, the problem is somewhere deeper. If that goes well, one of the drivers is failing and you'll need to find it (eg. by bisection).

Second, on x86 we have PM_TRACE which uses the RTC to store some debugging information that can be used later to identify the point of failure. This might be portable to your platforms.

Next, you can use my recent patches (available at
http://www.sisk.pl/kernel/hibernation_and_suspend/2.6.24-rc2/patches/) to check how deep the problem is located.

Greetings,
Rafael

#4 lore raw
In reply to Kristoffer Ericson
Quoted 7 lines · Kristoffer Ericson

Greetings,

Ive been following your discussion and documentation efforts concerning pm in the kernel. This has in the past been a gray area which was hard to find information about so kudos.

I maintain 2 handheld platforms that would benefit greatly from implementing proper pm (mainly suspend) but Im having problems bugtracking it. Currently the system tries to suspend but fails somewhere and then tries to resume (which fails). The end result however is that Im unable to see anything (bugmessages...) since the video driver gets deactivated by pm.

My question is this: Is bisecting (turning off device support in kernel until it works) the best approach when bugtracking pm suspend? Or is there any other logging system that I can use?

Bisecting is not bad. Or you can port store-progress-into-rtc hacks from pc...

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html