On Friday, 22 September 2006 03:17, Benjamin A. Okopnik wrote: > On Thu, Sep 21, 2006 at 11:28:29AM +0200, Pavel Machek wrote: > > > > You probably want to debug swsusp, first. Do you have highmem64g? Does > > it work from init=/bin/bash? noapic? > > Well, color me surprised. And lucky. :) While I was testing 'swsusp' > (S2D mode), I managed to figure out that there was some CPU-related > module that was creating a problem. A little experimentation, and > /voila/ - I discovered that the 'acpi_cpufreq' module (which isn't very > useful to me anyway) was the one gumming up the works. At this point, > I've run "echo disk > /sys/power/state" more than 10 times in a row from > a variety of configurations - "init=/bin/bash", booting to console with > a full load of modules, running X, X plus a PCMCIA card - and it's all > working so far. I'll definitely report if it starts acting stupid again.
Good to hear it works. :-) Could you please open a bug report at http://bugzilla.kernel.org for the acpi_cpufreq problem? Greetings, Rafael -- You never change things by fighting the existing reality. R. Buckminster Fuller ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Suspend-devel mailing list Suspend-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/suspend-devel
