public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Schierl <schierlm@gmx.de>
To: Antony Dovgal <tony2001@phpclub.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: APM & device_power_up/down
Date: Tue, 09 Mar 2004 20:52:10 +0100	[thread overview]
Message-ID: <404E206A.266ABD1C@gmx.de> (raw)
In-Reply-To: 20040309101110.50b55786.tony2001@phpclub.net

Antony Dovgal schrieb:
> 
> On Sat, 06 Mar 2004 23:44:08 +0100
> Michael Schierl <schierlm-usenet@gmx.de> wrote:
> 
> > 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?
> 
> Yes, it works ok for me with this patch.

Are you using any modules or patches that are not in the main line
kernel?
Does your problem also occur when you build a "minimal" kernel (i.e.
remove all things from it you don't really need for booting up, e.g.
local apic, pcmcia, network support, framebuffer, mouse)?

can you boot with init=/bin/bash (or another shell) and then do 

mount /proc
apm -s

does suspending work there? (this all against a "vanilla" kernel).

The thing above was just a guess, the only difference between the 2
patches i know is that the patch which is in kernel also informs all
device drivers. So i guess there must be a "broken" device driver that
makes your supend come to a halt.

Michael

  reply	other threads:[~2004-03-09 19:52 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 ` APM & device_power_up/down Michael Schierl
2004-03-09  7:11   ` Antony Dovgal
2004-03-09 19:52     ` Michael Schierl [this message]
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=404E206A.266ABD1C@gmx.de \
    --to=schierlm@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --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