Date: Tue, 15 Feb 2005 20:47:10 +0100
From: Pavel Machek <pavel@suse.cz>
To: Norbert Preining <preining@logic.at>
Cc: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2005@gmx.net>,
       ACPI mailing list <acpi-devel@lists.sourceforge.net>,
       kernel list <linux-kernel@vger.kernel.org>, seife@suse.de, rjw@sisk.pl
Subject: Re: [ACPI] Call for help: list of machines with working S3
Message-ID: <20050215194710.GE7338@elf.ucw.cz>
References: <20050214211105.GA12808@elf.ucw.cz> <20050215125555.GD16394@gamma.logic.tuwien.ac.at> <42121EC5.8000004@gmx.net> <20050215170837.GA6336@gamma.logic.tuwien.ac.at>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20050215170837.GA6336@gamma.logic.tuwien.ac.at>
User-Agent: Mutt/1.5.6+20040907i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1034
Lines: 23

Hi!

> - Sometimes I have to make a Sysrq-s (sync) to get some stuff running
>   (eg logging in from the console hangs after input of passwd, calling
>   sysrq-s makes it continue). I had a similar effect when logging in
>   AFTER resuming (for the resume I had only gdm running but wasn't
>   logged in) the GNOME starting screen stayed there indefinitely, no
>   change. Even after restarting the X server and retrying.
>   Logging in with twm session DID work without any problem.
>   Do you have any idea what this could be?

Does it happen with swsusp? Is it in any way reproducible? Maybe
commenting out refrigerator would help....

								Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
-
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/