From: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
To: Patrick Mochel <mochel@osdl.org>
Cc: Zwane Mwaikambo <zwane@linuxpower.ca>,
Andrew Morton <akpm@digeo.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.69-mm5: reverting i8259-shutdown.patch
Date: 15 May 2003 14:02:35 +0200 [thread overview]
Message-ID: <1053000155.605.1.camel@teapot.felipe-alfaro.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0305141956530.9816-100000@cherise>
On Thu, 2003-05-15 at 05:00, Patrick Mochel wrote:
> On Wed, 14 May 2003, Zwane Mwaikambo wrote:
>
> > On Wed, 14 May 2003, Patrick Mochel wrote:
> >
> > > Interesting. This is yet more proof that system-level devices cannot be
> > > treated as common, everyday devices. Sure, it's nice to see them show up
> > > in sysfs with little overhead, and very nice not to have to work about
> > > them during shutdown or power transitions. But there are just too many
> > > special cases (like getting the ordering right ;) that you have to worry
> > > about.
> > >
> > > So, what do we do with them?
> >
> > Does the PIC shutdown callback get called _just_ before acpi_power_off?
>
> It may or may not be. It depends on which order it gets registered in,
> which is arbitrary (*). One can enable DEBUG in drivers/base/power.c and
> crank up the console log level to see the order that devices get shutdown
> in on their system.
OK, I've changed "#undef DEBUG" to "#define DEBUG" in
drivers/base/power.c, but during shutdown, I can see no extra debug
messages. What am I doing wrong?
next prev parent reply other threads:[~2003-05-15 11:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-15 2:23 Felipe Alfaro Solana
2003-05-15 2:33 ` Andrew Morton
2003-05-15 2:39 ` Patrick Mochel
2003-05-15 2:45 ` Zwane Mwaikambo
2003-05-15 3:00 ` Patrick Mochel
2003-05-15 12:02 ` Felipe Alfaro Solana [this message]
2003-05-15 17:35 ` Patrick Mochel
2003-05-15 6:14 ` Andrew Morton
2003-05-15 6:13 ` Zwane Mwaikambo
2003-05-15 7:56 ` Zwane Mwaikambo
2003-05-15 17:34 ` Patrick Mochel
2003-05-15 12:07 ` Felipe Alfaro Solana
2003-05-17 19:25 ` Zwane Mwaikambo
2003-05-17 19:47 ` Felipe Alfaro Solana
2003-05-17 20:35 ` Zwane Mwaikambo
2003-05-18 19:42 ` Felipe Alfaro Solana
2003-05-16 19:41 ` Pavel Machek
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=1053000155.605.1.camel@teapot.felipe-alfaro.com \
--to=felipe_alfaro@linuxmail.org \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=zwane@linuxpower.ca \
/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®