Message-ID: <404E206A.266ABD1C@gmx.de>
Date: Tue, 09 Mar 2004 20:52:10 +0100
From: Michael Schierl <schierlm@gmx.de>
MIME-Version: 1.0
To: Antony Dovgal <tony2001@phpclub.net>
CC: linux-kernel@vger.kernel.org
Subject: Re: APM & device_power_up/down
References: <1uQOH-4Z1-9@gated-at.bofh.it>
		<S261722AbUCFWoa/20040306224430Z+905@vger.kernel.org> <20040309101110.50b55786.tony2001@phpclub.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1274
Lines: 35

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/