From: Pavel Machek <pavel@ucw.cz>
To: Linus Torvalds <torvalds@osdl.org>
Cc: "Frédéric Riss" <frederic.riss@gmail.com>,
"Arjan van de Ven" <arjan@infradead.org>,
"Linux Kernel list" <linux-kernel@vger.kernel.org>,
len.brown@intel.com
Subject: suspend debugging Re: 2.6.18 suspend regression on Intel Macs
Date: Wed, 11 Oct 2006 13:16:13 +0000 [thread overview]
Message-ID: <20061011131613.GB4725@ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.64.0610101649440.3952@g5.osdl.org>
Hi!
> I'm wondering what Pavel does for debugging these things, since the claim
> was that keeping printk() active would make debugging easier. As it is, it
> just seems to break suspend exactly because it wants to access devices
> that are turned off.
>
> Pavel?
I have framebuffer console here, and just leave printk enabled during
system. Last messages usually tell me where to look for problem...
Plus I test suspend quite often so that regressions show up quickly.
In the early days, plain vga console on machine where bios kicks video
card to work after resume did wonders, and I had to use hardware
debugger on one machine, too.
Another common trick is to test s2disk, first. It tends to catch many
driver problems.
Pavel
--
Thanks for all the (sleeping) penguins.
next prev parent reply other threads:[~2006-10-11 13:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-09 18:19 Frédéric Riss
2006-10-10 10:39 ` Pavel Machek
2006-10-10 10:41 ` Arjan van de Ven
2006-10-10 10:49 ` Pavel Machek
2006-10-10 15:33 ` Linus Torvalds
2006-10-10 19:08 ` Frédéric Riss
2006-10-10 19:38 ` Arjan van de Ven
2006-10-10 19:46 ` Frédéric Riss
2006-10-10 19:50 ` Pavel Machek
2006-10-10 21:49 ` Linus Torvalds
2006-10-10 22:09 ` Frédéric Riss
2006-10-10 23:53 ` Linus Torvalds
2006-10-11 6:09 ` Frédéric Riss
2006-10-11 13:16 ` Pavel Machek [this message]
2006-10-11 6:35 ` Len Brown
2006-10-11 14:35 ` Linus Torvalds
2006-10-10 21:28 ` Matthew Garrett
2006-10-11 6:37 ` Len Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061011131613.GB4725@ucw.cz \
--to=pavel@ucw.cz \
--cc=arjan@infradead.org \
--cc=frederic.riss@gmail.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®