Re: [qubes-users] Suspend Problems

2016-10-10 Thread Torsten Grote
On 10/08/2016 02:46 PM, jo...@mailbox.org wrote:
> 1. the network-connection symbol says the network is broken. I have to
> reboot the sys-net (kill and restart), then the network comes online
> again and I have network connection from within the sys-net.

This problem I have as well after waking up from each suspend, but I
found out that it is sufficient to disable the networking via the
network manager icon and then re-enable it.

Kind Regards,
Torsten

-- 
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+unsubscr...@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/9c3b9098-d557-7a84-e472-dfa08e9ab920%40grobox.de.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Suspend Problems

2016-10-08 Thread jondo

Dear Qubes Users,

first of all I would thank the developers for this great peace of
software! It (3.2) works on two Laptops and now I made the step to
install it on the "main"-PC. Very unfortunate suspend-to-ram does not
work ... really. Maybe someone has a cure for this unfortunate
behaviour.

I can suspend, and the machine wakes up from sleep, but is more or less
unusable afterwards. The symptoms are:
1. the network-connection symbol says the network is broken. I have to
reboot the sys-net (kill and restart), then the network comes online
again and I have network connection from within the sys-net.
2. Most of the other VMs are offline and stopped. Restarting these VMs
does not work or takes ages. You cannot start any other VMs (well
somethimes after several minutes something works, i.e. a shell is
startet, but no net.)
3. in Dom0 you can see that some process like (awk, cut, sed and such
are taking 100% of one CPU core for hours.) 
4. the VM-Manager marks some/most VMs with "VM didn't give back memory".
I can restart (kill) them, but they are unresposive/unusable. Sometimes
I can get a shell, sometimes not (or I haven't waited long enough.)
5. I cannot shut down properly. (_maybe_ I could wait some hours, and
it would work.) Have to do a cold reset.

So I have to cold reset to have a working system again. 
Could someone maybe shed some light on this?

Best,
Jon







-- 
layout:
  'hcl'
type:
  'desktop'
hvm:
  'yes'
iommu:
  'no'
slat:
  'yes'
tpm:
  'unknown'
brand: |
  System manufacturer
model: |
  System Product Name
bios: |
  0508
cpu: |
  Intel(R) Core(TM) i5-3450S CPU @ 2.80GHz
cpu-short: |
  FIXME
chipset: |
  Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM
Controller [8086:0150] (rev 09) chipset-short: |
  FIXME
gpu: |
  Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD
6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller])
gpu-short: | FIXME
network: |
  Intel Corporation 82579V Gigabit Network Connection (rev 04)
memory: |
  16337
scsi: |
  DVD RW AD-7760H  Rev: 1.00
  SAMSUNG SSD 830  Rev: 3B1Q

versions:

- works:
'FIXME:yes|no|partial'
  qubes: |
R3.2
  xen: |
4.6.1
  kernel: |
4.4.14-11
  remark: |
FIXME
  credit: |
FIXAUTHOR
  link: |
FIXLINK

---


-- 
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+unsubscr...@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/20161008194607.7de9f146%40mailbox.org.
For more options, visit https://groups.google.com/d/optout.