public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: acpi-devel@lists.sourceforge.net, romano@dea.icai.upco.es
Cc: Pavel Machek <pavel@ucw.cz>,
	Stefan Schweizer <sschweizer@gmail.com>,
	Norbert Preining <preining@logic.at>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [ACPI] Re: 2.6.12-rc1-mm4 and suspend2ram (and synaptics)
Date: Tue, 5 Apr 2005 17:31:52 +0200	[thread overview]
Message-ID: <200504051731.52845.rjw@sisk.pl> (raw)
In-Reply-To: <20050405150105.GA26149@pern.dea.icai.upco.es>

Hi,

On Tuesday, 5 of April 2005 17:01, Romano Giannetti wrote:
> > 
> > Same way to debug it, then.... try minimal drivers.
> 
> Yes, the lifer of a kernel debugger is hard... 
> 
> Pavel, one question (maybe stupid, I am not at all an expert). Wouldn't be
> possible to add a printk when invoking and returning from suspend/resume
> methods of drivers, telling if they are specific or generic on? Maybe with
> the help of the serial console could be an aid to detect wich drivers are
> failing in that case.

The serial sonsole itself is disabled during suspend/resume, so you have to
hack the serial driver's suspend/resume routines to get any output on it
at that time. :-)

Anyway, if you want to put some debug printks somewhere, IMO a good place
to start is in resume_device() in drivers/base/power/resume.c or
in suspend_device() in drivers/base/power/suspend.c (actually, there already
is one, you only need to enable it).

Greets,
Rafael


-- 
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
		-- Lewis Carroll "Alice's Adventures in Wonderland"

  reply	other threads:[~2005-04-05 15:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-31 22:08 2.6.12-rc1-mm4 and suspend2ram (and synaptics) Norbert Preining
2005-04-01 11:33 ` Pavel Machek
2005-04-01 17:38   ` [ACPI] " Stefan Schweizer
2005-04-02  8:59     ` Pavel Machek
2005-04-05 15:01       ` Romano Giannetti
2005-04-05 15:31         ` Rafael J. Wysocki [this message]
2005-04-03 22:45   ` Norbert Preining
2005-04-03 22:59     ` Pavel Machek
2005-04-04  8:16       ` Norbert Preining
2005-04-05 10:06         ` Pavel Machek
2005-04-05 12:46           ` Norbert Preining
2005-04-05 13:24           ` Norbert Preining

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=200504051731.52845.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=preining@logic.at \
    --cc=romano@dea.icai.upco.es \
    --cc=sschweizer@gmail.com \
    /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