Date: Sat, 21 Jun 2014 07:37:34 -0700 From: Adrian Chadd <adrian@freebsd.org> To: =?UTF-8?Q?Jan_Kokem=C3=BCller?= <jan.kokemueller@gmail.com> Cc: "freebsd-mobile@freebsd.org" <freebsd-mobile@freebsd.org> Subject: Re: Suspend/Resume on Lenovo IdeaPad S400 with FreeBSD 10? Message-ID: <CAJ-VmomRKCBx9dcUew-1%2BYFKU_mXOhyFJ_UohgY_S_-7D0HX4Q@mail.gmail.com> In-Reply-To: <53A54C05.7060403@gmail.com> References: <CAOTTJKFPTTbg9GZv1Vvwc%2BRYRQXXYA2pk5Lr%2BZid64gp3b4-9w@mail.gmail.com> <53A54C05.7060403@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ah, that patch. I wonder whether it's something that we need in X or whether the dri code needs prodding. -a On 21 June 2014 02:10, Jan Kokem=C3=BCller <jan.kokemueller@gmail.com> wrot= e: >> After some experimenting, I found this patch, which solved the problem >> completely: >> http://lists.freebsd.org/pipermail/freebsd-x11/2013-October/013727.html >> >> Now, I have this in X log after resume: >> [ 4561.749] (WW) intel(0): retrying batchbuffer submit >> [ 4561.803] (WW) intel(0): retrying batchbuffer submit >> [ 4561.857] (WW) intel(0): retrying batchbuffer submit >> [ 4561.908] (WW) intel(0): retrying batchbuffer submit >> [ 4561.959] (WW) intel(0): retrying batchbuffer submit >> [ 4562.012] (WW) intel(0): retrying batchbuffer submit >> [ 4562.063] (WW) intel(0): retrying batchbuffer submit >> [ 4562.117] (WW) intel(0): retrying batchbuffer submit >> [ 4562.171] (WW) intel(0): retrying batchbuffer submit >> [ 4562.225] (WW) intel(0): retrying batchbuffer submit >> [ 4562.279] (WW) intel(0): retrying batchbuffer submit >> [ 4562.333] (WW) intel(0): retrying batchbuffer submit >> [ 4562.386] (WW) intel(0): retrying batchbuffer submit >> [ 4562.439] (WW) intel(0): retrying batchbuffer submit >> [ 4562.493] (WW) intel(0): retrying batchbuffer submit >> [ 4562.547] (WW) intel(0): retrying batchbuffer submit >> [ 4564.779] (II) AIGLX: Suspending AIGLX clients for VT switch >> [ 4564.779] (WW) intel(0): drmDropMaster failed: Unknown error: -22 >> [ 4565.994] (II) AIGLX: Resuming AIGLX clients after VT switch >> [ 4566.096] (II) intel(0): EDID vendor "CMN", prod id 5239 >> [ 4566.096] (II) intel(0): Printing DDC gathered Modelines: >> [ 4566.096] (II) intel(0): Modeline "1366x768"x0.0 71.59 1366 1410 >> 1439 1512 768 771 775 789 -hsync -vsync (47.3 kHz eP) >> >> but everything is alive: compiz restarts correctly, GL applications >> work as they did before resume. Job done! >> >> A question: is this patch ok? Nothing wrong with it? Do you or anybody >> else experienced a similar problem and found a different solution? > > > I think I found a less hackish workaround for this problem. I've put "pki= ll > -STOP X" into /etc/rc.suspend and "pkill -CONT X" into /etc/rc.resume. Th= is > seems to work fine so far with an unmodified xf86-video-intel driver on m= y > SL510. > > _______________________________________________ > freebsd-mobile@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmomRKCBx9dcUew-1%2BYFKU_mXOhyFJ_UohgY_S_-7D0HX4Q>