MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16113.30843.610388.253090@solen.ce.chalmers.se>
Date: Thu, 19 Jun 2003 10:46:51 +0200
From: Florian-Daniel Otel <otel@ce.chalmers.se>
To: EricAltendorf@orst.edu,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
       swsusp-devel@lists.sourceforge.net
Subject: Re: [Swsusp-devel] Re: RTC causes hard lockups in 2.5.70-mm8
In-Reply-To: <16113.30505.519963.233275@solen.ce.chalmers.se>
References: <Pine.LNX.4.55L-032.0306122205210.4915@unix48.andrew.cmu.edu>
	<1055492730.5162.0.camel@dhcp22.swansea.linux.org.uk>
	<200306171232.27887.EricAltendorf@orst.edu>
	<200306190031.54686.EricAltendorf@orst.edu>
	<16113.30505.519963.233275@solen.ce.chalmers.se>
Reply-To: Florian-Daniel Otel <otel@ce.chalmers.se>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2343
Lines: 59


Ermm.....Me bad :). I was talking 2.4.21 here...

Anyway, take it for what it's worth.

Florian


Florian-Daniel Otel writes:
> 
> 
> 
> I can confirm the RTC problems on a Fujitsu LifeBook P2120 (Crusoe
> TM5800, ALi, ACPI). In my case I was even more fortunate (??) since
> using RTC (either compiled-in in the kernel and/or as a module), any
> call to "hwclock" locks the machine rock solid (not even SysRQ
> works). So for me the RTC issue is not at all swsusp related.
> 
> Back to swsusp: I'm more than happy to annonce that I just discovered
> that -pre11 works !! Actually, after reading a bit more closely this
> list (*gasp*) and trying the suspend the machine AFTER modules were
> unloaded (WLAN, USBs), networking stopped and all non-critical daemons
> terminated (basically switching to run-level 1, terminating daemons
> and unloading modules), the suspend worked !! And resuming too :)) !!
> 
> As such, after a horrible hack of the old  suspend.sh script (from
> swsusp-beta17) and using "echo -n 4 > /proc/acpi/sleep" the
> suspension+resuming process worked (at least once...).
> 
> On less extatic but more useful note: It seems that if I start the
> suspending process by hand (i.e. swsusp utility) while PCMCIA and USBs
> are stopped but __not__ networking, the resume process freezes. I can
> use SysRq+T at this point, but since this is a "legacy free" laptop, I
> have no idea how to hook on a serial console there and come w/ a
> useful bug report. If anyone has an idea how to do that, I'll be more
> than happy to help w/ more testing.
> 
> 
> HTH,
> 
> Florian
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: INetU
> Attention Web Developers & Consultants: Become An INetU Hosting Partner.
> Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
> INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
> _______________________________________________
> swsusp-devel mailing list
> swsusp-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/swsusp-devel
-
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/