[prev in list] [next in list] [prev in thread] [next in thread] 

List:       qubes-users
Subject:    [qubes-users] Re: Suspend/Shutdown Issue report
From:       sudodcfldd () gmail ! com
Date:       2015-12-31 10:12:58
Message-ID: a92b5beb-2ca7-414c-be25-8ea2d1c4e063 () googlegroups ! com
[Download RAW message or body]


Am Dienstag, 29. Dezember 2015 09:46:53 UTC+1 schrieb Kevin Moraga:
> Hi,
> Just to do a report.
> I did a fresh installation of RC3.1 and now I have some problems with Suspend and \
> Shutdown actions. I can suspend my laptop just 1 time and after that, I get this \
> error message everytime that I try to shutdown/suspend dom0: 
> ```
> Failed to issue method call: Transaction is destructive. 
> ```
> 
> After checking qubes-suspend.service, once I did suspend my laptop, I see this: 
> 
> ```
> qubes-suspend.service - Qubes suspend hooks
> Loaded: loaded (/usr/lib/systemd/system/qubes-suspend.service; enabled)
> Active: deactivating (stop-post) since Mon 2015-12-28 21:27:44 CST; 5h 1min ago
> Process: 10646 ExecStop=/usr/lib64/pm-utils/sleep.d/52qubes-pause-vms resume \
>                 suspend (code=exited, status=0/SUCCESS)
> Process: 10608 ExecStart=/usr/lib64/pm-utils/sleep.d/52qubes-pause-vms suspend \
>                 suspend (code=exited, status=0/SUCCESS)
> Process: 10545 ExecStartPre=/usr/lib64/pm-utils/sleep.d/51qubes-suspend-netvm \
>                 suspend suspend (code=exited, status=0/SUCCESS)
> Process: 10541 ExecStartPre=/usr/lib64/pm-utils/sleep.d/01qubes-sync-vms-clock \
> suspend suspend (code=exited, status=0/SUCCESS) Main PID: 10608 (code=exited, \
>                 status=0/SUCCESS);                 : 10652 (51qubes-suspend)
> CGroup: /system.slice/qubes-suspend.service
> └─control
> ├─10652 /bin/sh /usr/lib64/pm-utils/sleep.d/51qubes-suspend-netvm resume \
> suspend ├─10695 /usr/bin/python2 /usr/bin/qvm-run -u root --pass-io sys-usb \
> QUBESRPC qubes.SuspendPost dom0 └─10700 /usr/lib/qubes/qrexec-client -d sys-usb \
> root:QUBESRPC qubes.SuspendPost dom0 
> Dec 28 21:26:55 dom0 51qubes-suspend-netvm[10545]: method return \
> time=1451359615.855689 sender=:1.4 -> destination=:1.765 serial=14993 \
>                 reply_serial=2
> Dec 28 21:27:22 dom0 systemd[1]: Started Qubes suspend hooks.
> Dec 28 21:27:44 dom0 systemd[1]: Unit qubes-suspend.service is not needed anymore. \
>                 Stopping.
> Dec 28 21:27:44 dom0 systemd[1]: Stopping Qubes suspend hooks...
> Dec 28 21:27:45 dom0 51qubes-suspend-netvm[10652]: method return \
> time=1451359665.748227 sender=:1.4 -> destination=:1.769 serial=15031 \
>                 reply_serial=2
> Dec 29 02:21:50 dom0 systemd[1]: Starting Qubes suspend hooks...
> Dec 29 02:27:37 dom0 systemd[1]: Stopping Qubes suspend hooks...
> ```

I've got a similar problem. Suspend and resume actually work, but suspending takes a \
very long time. When pressing the suspend button the screen gets locked immediately, \
then nothing happens for a minute or two. After that Qubes finally goes to sleep. \
There are no error messages and I added ehci_pci, xhci-pci to \
suspend-modules-blacklist.

Any ideas?

-- 
You received this message because you are subscribed to the Google Groups \
"qubes-users" group. To unsubscribe from this group and stop receiving emails from \
it, send an email to qubes-users+unsubscribe@googlegroups.com. To post to this group, \
send email to qubes-users@googlegroups.com. To view this discussion on the web visit \
https://groups.google.com/d/msgid/qubes-users/a92b5beb-2ca7-414c-be25-8ea2d1c4e063%40googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.



[prev in list] [next in list] [prev in thread] [next in thread]