mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Schierl <schierlm-usenet@gmx.de>
To: Antony Dovgal <tony2001@phpclub.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: APM & device_power_up/down
Date: Sat, 06 Mar 2004 23:44:08 +0100	[thread overview]
Message-ID: <S261722AbUCFWoa/20040306224430Z+905@vger.kernel.org> (raw)
In-Reply-To: <1uQOH-4Z1-9@gated-at.bofh.it>

On Mon, 01 Mar 2004 09:20:07 +0100, in linux.kernel you wrote:

>Hi all!
>
>I've tried to contact Pavel Machek directly, but got no response from him, so I'm forwarding the letter to the list.
>
>The problem is: 
>the patch, that was provided here: 
>http://marc.theaimsgroup.com/?l=linux-kernel&m=107540713415651&w=2, 
>prevents my laptop from suspending.

Hmm. Can you try unapplying it and applying the one in 

http://marc.theaimsgroup.com/?l=linux-kernel&m=107506063605497&w=2

instead? Does it work for you as well as with no patch?

>This behaviuor was firstly noticed after upgrade from 2.6.1 to 2.6.2 (and 2.6.3 doesn't fix it).

>So I decided to do a small investigation and discovered that when I 
>remove calls to device_power_*() from apm.c, it works well.

My situation is the other way round. I was always unable to suspend my
laptop under Linux until I tried the 2.5.x series first. That one
worked; however, in 2.6.0-test4 someone did some major changes and
removed these two calls as well. So I could not suspend in 2.6.0-test4
till 2.6.1, now U can again :-)

>Of course, the problem can be in my laptop's BIOS or wherever, but, I 
>repeat, it works well with 2.4.x & 2.6.1 and it doesn't with 2.6.2 & 
>2.6.3.

Same for me. Dunno if my or your BIOS is borked, but one is surely
broken.

>At this moment I can hardly understand why there is need to power down 
>devices after suspend (shouldn't they be powered down in the suspend 
>process?), but I'm not a kernel hacker.

Where do you read something about powering down devices after suspend?

The process is:

1- suspend devices

2- (power down devices w/ my patch)

3- asm call to put cpu in suspend mode - it will not return 
   until you wake it up again

4- (power up devices w/ my patch)

5- resume devices

>So, any help is appreciated.

HTH,

Michael
-- 
My PGP Key: User ID: Michael Schierl <schierlm@gmx.de>
Key ID: 0x58B48CDD    Size: 2048    Created: 26.03.2002
Fingerprint:  68CE B807 E315 D14B  7461 5539 C90F 7CC8
http://home.arcor.de/mschierlm/mschierlm.asc

       reply	other threads:[~2004-03-06 22:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1uQOH-4Z1-9@gated-at.bofh.it>
2004-03-06 22:44 ` Michael Schierl [this message]
2004-03-09  7:11   ` Antony Dovgal
2004-03-09 19:52     ` Michael Schierl
2004-03-12  7:30       ` Antony Dovgal
2004-03-01  8:11 Antony Dovgal

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=S261722AbUCFWoa/20040306224430Z+905@vger.kernel.org \
    --to=schierlm-usenet@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schierlm@gmx.de \
    --cc=tony2001@phpclub.net \
    /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®