From: "Albert D. Cahalan" <acahalan@cs.uml.edu>
To: pavel@suse.cz (Pavel Machek)
Cc: maillist@chello.nl (Igmar Palsenberg),
pavel@ucw.cz (Pavel Machek),
linux-kernel@vger.kernel.org (kernel list)
Subject: Re: kapm-idled : is this a bug?
Date: Thu, 21 Dec 2000 14:27:24 -0500 (EST) [thread overview]
Message-ID: <200012211927.eBLJROd347633@saturn.cs.uml.edu> (raw)
In-Reply-To: <20001221132800.A1398@bug.ucw.cz> from "Pavel Machek" at Dec 21, 2000 01:28:00 PM
>> Agree that it is different. But it confuses people to have two
>> idle-tasks. I suggest that we throw it one big pile, unless having a
>> separate apm idle task has a purpose.
>
> You can't do that.
Sure you can, and it makes perfect sense.
> Doing it this way is _way_ better for system
> stability, because kidle-apmd sometimes dies due to APM
> bug. kidle-apmd dying is recoverable error; swapper dieing is as fatal
> as it can be.
Good. Maybe the bugs will get fixed then. If the bugs are in
the BIOS or motherboard hardware, we can have a blacklist.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-21 19:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-11 17:00 stewart
2000-12-11 5:11 ` Robert M. Love
2000-12-11 15:16 ` Rik van Riel
2000-12-11 15:45 ` Nick Holloway
2000-12-11 18:56 ` stewart
2000-12-11 19:26 ` Richard B. Johnson
2000-12-11 19:28 ` Mark Hahn
2000-12-11 23:49 ` Kurt Garloff
2000-12-15 22:40 ` Pavel Machek
2000-12-17 2:18 ` Jamie Lokier
2000-12-17 15:26 ` Igmar Palsenberg
2000-12-20 9:11 ` Pavel Machek
2000-12-21 11:00 ` Igmar Palsenberg
2000-12-21 12:28 ` Pavel Machek
2000-12-21 19:27 ` Albert D. Cahalan [this message]
2000-12-22 10:02 ` Pavel Machek
2000-12-22 18:50 ` Igmar Palsenberg
2000-12-22 18:45 ` Igmar Palsenberg
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=200012211927.eBLJROd347633@saturn.cs.uml.edu \
--to=acahalan@cs.uml.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=maillist@chello.nl \
--cc=pavel@suse.cz \
--cc=pavel@ucw.cz \
/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®