From: Philippe Troin <phil@fifi.org>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: APM suspend/resume ceased to work with 2.4.28
Date: 24 Nov 2004 22:10:54 -0800 [thread overview]
Message-ID: <871xeia26p.fsf@ceramic.fifi.org> (raw)
In-Reply-To: 20041123070252.GA2712@logos.cnet
Marcelo Tosatti <marcelo.tosatti@cyclades.com> writes:
> On Mon, Nov 22, 2004 at 04:03:05PM -0800, Philippe Troin wrote:
> > Marcelo Tosatti <marcelo.tosatti@cyclades.com> writes:
> >
> > > On Sun, Nov 21, 2004 at 07:25:20PM -0800, Philippe Troin wrote:
> > > > Seen on a Dell Inspiron 3800 with BIOS revision A17.
> > > >
> > > > APM suspend/resume works perfectly with 2.4.27 (or at least, as well
> > > > as APM can).
> > > >
> > > > Since I did not see any differences in arch/i386/kernel/apm.c between
> > > > .27 and .28, I'm at loss to explain the problem.
> > >
> > > Guess: Are you using ACPI ?
> >
> > ACPI is compiled in, but the kernel is booted with noacpi...
> >
> > Phil.
>
> Phil,
>
> Can you please try 2.4.28-pre3 ?
>
> Lets try to find out where it started to happen. I've got no clue,
> there are no indeed no APM related changes in 2.4.28.
The bug was introduced between rc1 and rc2.
I'm still working on it to narrow it down to which delta introduced
the bug.
I suspect either the ACPI or the APIC/DMI changes.
Phil.
next prev parent reply other threads:[~2004-11-25 6:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 3:25 APM suspend/resume ceased to work with 2.4.28 Philippe Troin
2004-11-22 17:36 ` Marcelo Tosatti
2004-11-23 0:03 ` Philippe Troin
2004-11-23 7:02 ` Marcelo Tosatti
2004-11-25 6:10 ` Philippe Troin [this message]
2004-12-03 1:50 ` Philippe Troin
2004-12-03 3:13 ` Len Brown
[not found] <F7DC2337C7631D4386A2DF6E8FB22B300225E3FC@hdsmsx401.amr.corp.intel.com>
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=871xeia26p.fsf@ceramic.fifi.org \
--to=phil@fifi.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.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