On Sun, 8 Apr 2012 21:20:35 +0900, Vladimir Lomov wrote: >Hello, >** Jonathan Hudson [2012-04-08 12:53:42 +0100]: > >> On Sun, 08 Apr 2012 13:48:11 +0200, Richard Schütz wrote: > >>>Am 07.04.2012 12:33, schrieb Vladimir Lomov: >>>> Hello, >>>> ** Jonathan Hudson [2012-04-06 20:00:33 +0100]: > >>>>> On Fri, 06 Apr 2012 20:41:46 +0200, Richard Schütz wrote: > >>>>>> Since 3.3.0 suspend isn't working on my desktop computer anymore. Looks >>>>>> like device suspension fails somewhere. Furthermore 3.3.1 seriously >>>>>> breaks ath9k on my netbook [1]. > >>>>>> [1] https://bugzilla.kernel.org/show_bug.cgi?id=43038 > >>>>> I have a similar reservation. On two eeepc 901, suspend works just >>>>> fine. Alas, only only on one of them does resume work with a 3.3 >>>>> kernel. I'm not convinced that 3.3 is ready. > >>>> Same here: >>>> Archlinux x86_64, >>>> testing, kernel 3.1.1-1 >>>> HW: HP Pavilion dv3 (2210er) with nvidia g104m graphics card, atheros >>>> wi-fi. > >>>And with 3.2.x there were no problems like that for both of you? > >> Correct. The "won't resume on 3.3.x" eeepc is suspending / resuming >> happily with 3.2.13-1-ARCH (downgraded a couple of days ago). As it's >> the wife's machine, I dare not touch it now it's working again. > >> I'm somewhat baffled by the whole thing; there is nothing obvious in >> any logs, but X fails to come back from sleep. > >Do you mean "suspend to RAM" or "suspend to DISK"? I tried before >"suspend to DISK": 3.3.1 and 3.3.0 works fine. > >P.S. I use advice found on wiki and systemd. > >--- >WBR, Vladimir Lomov Suspend to RAM. -jh
