mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Patrick Mochel <mochel@osdl.org>
Cc: Andrew Morton <akpm@digeo.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.69-mm5: reverting i8259-shutdown.patch
Date: Fri, 16 May 2003 21:41:28 +0200	[thread overview]
Message-ID: <20030516194128.GB372@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.44.0305141935440.9816-100000@cherise>

Hi!

> > > Hi again, Andrew,
> > > 
> > > Besides the "make_KOBJ_NAME-match_BUS_ID_SIZE.patch" causing "pccard"
> > > oopses, I've also found that, with 2.5.69-mm5 compiled with ACPI
> > > support, my laptop is unable to power off. The kernel invokes
> > > "acpi_power_off" and stays there forever.
> > > 
> > > I've found that reverting the "i8259-shutdown.patch" fixes the problem
> > > and my laptop is able to shutdown properly (init 0) when using ACPI.
> > > 
> > > A hardware bug? A kernel bug?
> > 
> > And thanks again, again.
> > 
> > That's the below patch.  It looks pretty innocuous.  I'd be assuming that
> > there's something in the shutdown sequence which needs 8259 functionality
> > after the thing has been turned off.
> > 
> > This could well depend upon .config contents and linkage order.
> > 
> > Eric, maybe we need to turn it off by hand at the right time rather than
> > relying on driver model shutdown ordering?
> 
> 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? 

I guess shutdown needs to be treated like suspend, and needs to have
"level". There should be no shutdown, you should do suspend(5, ) and
go through all levels properly.
								Pavel

-- 
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]

      parent reply	other threads:[~2003-05-16 19:52 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
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 [this message]

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=20030516194128.GB372@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@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®