public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ross Burton <ross@burtonini.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: APM and ACPI sleep issues with 2.6 (2.6.2pre1-mm1 vs mm2)
Date: Sat, 24 Jan 2004 12:46:20 +0000	[thread overview]
Message-ID: <1074948379.1368.11.camel@localhost.localnet> (raw)
In-Reply-To: <20040121015903.0b4198b0.sfr@canb.auug.org.au>

On Tue, 2004-01-20 at 14:59, Stephen Rothwell wrote:
> > I've been told that building 2.6.1-mm4, making i8042 and atkdb modules
> > and unloading them before sleeping should fix this problem.  Is that the
> > blessed solution?  Unloading the modules for the keyboard controller
> > does seem a little too much like brute-force for me, especially since
> > 2.4.x managed fine. :)
> 
> I am not sure if you need to build i8042 and atkb as modules amy more, I
> thought there was a fix applied (in 2.6.1?).  However it would be
> interesting to the results of removing the modules before suspending.

After some frantic kernel building I've more interesting data (with
i8042 and atkbd built into the kernel).

2.6.2-rc1-mm1 will APM suspend and resume fine at first with the
following log:

atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
hda: start_power_step(step: 0)
hda: start_power_step(step: 1)
hda: complete_power_step(step: 1, stat: 50, err: 0)
hda: completing PM request, suspend
PCI: Setting latency timer of device 0000:00:1d.0 to 64
PCI: Setting latency timer of device 0000:00:1d.1 to 64
PCI: Setting latency timer of device 0000:00:1d.2 to 64
PCI: Found IRQ 5 for device 0000:00:1f.5
PCI: Sharing IRQ 5 with 0000:00:1f.3
PCI: Sharing IRQ 5 with 0000:02:03.1
PCI: Setting latency timer of device 0000:00:1f.5 to 64
hda: Wakeup request inited, waiting for !BSY...
hda: start_power_step(step: 1000)
hda: completing PM request, resume
MCE: The hardware reports a non fatal, correctable incident occurred on CPU 0.
Bank 1: f200000000000095

The atkbd lines are interesting as I was not running X at the time.  The
MCE line slightly worries me, is this normal?

However, I cannot sleep once I've used PCMCIA (with yenta_socket). 
Instead of sleeping it locks up.  I didn't notice this the first time
and came back to a very warm laptop, it felt like it had been
busy-looping.


I was very excited by the changelog for 2.6.2-rc1-mm2 with its "updated
ACPI" so I tried that.  ACPI still hard-crashes (grey screen, power
button dead, I had to remove the battery) and APM also crashes: it looks
like it is suspending (screen turns off and there is some disk activity)
but it never sleeps and I can't resume without holding the power button
(so at least *something* is still running).

Summary: something regressed over mm1 to mm2 with APM suspending, and
yenta_socket or cs isn't handling the suspend correctly.  Does anyone
have any ideas where I can look for these?

However, I did manage to use 2.6.2-pre1-mm1 for a day before I used my
wifi card, and did like what I saw -- the new scheduler makes GNOME more
responsive when I've a compile going.

Ross
-- 
Ross Burton                                 mail: ross@burtonini.com
                                          jabber: ross@burtonini.com
                                     www: http://www.burtonini.com./
 PGP Fingerprint: 1A21 F5B0 D8D0 CFE3 81D4 E25A 2D09 E447 D0B4 33DF



      parent reply	other threads:[~2004-01-24 12:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-04 16:05 APM and ACPI sleep issues with 2.6 Ross Burton
2004-01-05  3:00 ` Stephen Rothwell
2004-01-19 13:47   ` Ross Burton
2004-01-20 14:59     ` Stephen Rothwell
2004-01-20 15:25       ` Ross Burton
2004-01-24 12:46       ` Ross Burton [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=1074948379.1368.11.camel@localhost.localnet \
    --to=ross@burtonini.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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