While comparing Qubes 4 to Fedora 25 might be tempting, it is not similar as it might seem. Qubes 4 is based on Fedora 25, but some parts including kernel are independent. So, seeing different kernel-related behavior in Fedora 25 and Qubes 4 is definitely not a surprise.
Regards, Vít Šesták 'v6ak' On January 3, 2020 6:53:24 PM GMT+01:00, Claudia <claud...@disroot.org> wrote: >January 1, 2020 5:09 PM, "Claudia" <claud...@disroot.org> wrote: > >> However, I still have a long road ahead of me. I did several >suspend/resume cycles, and each time I >> had a different combination of problems, including the mouse >sticking, the keyboard not working, >> and finally input/output errors and segmentation faults in the >terminal. But the Xen problem has >> been identified nonetheless. I'll try kernel-latest and see if that >changes anything. > >Installed kernel-latest from stable, 5.3.11-1.qubes.x86, and no >difference as far as I can tell. It resumes fine the first time >usually, but after the second or third cycle, I get a bunch of io >errors, as though someone unplugged the SATA connector. I think this is >actually the underlying cause of the other symptoms. This is with no >VMs running. No swap. > >ata1.00: qc timeout (cmd 0xec) >ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) >ata1.00: limiting SATA link speed to 3.0 Gbps >ata1.00: SATA link up 3.0 Gbps (SStatus 123 SControl 320) >ata1.00: revalidation failed (errno=-5) >ata1.00: disabled >sd 0:0:0:0: [sda] Start/Stop Unit failed: Result: >hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK >sd 0:0:0:0: [sda] tag#21 FAILED Result: hostbyte=DID_BAD_TARGET >driverbyte=DRIVER_OK >sd 0:0:0:0: [sda] tag#21 CDB: Write(10) 2a 00 3c 9f [...] >blk_update_request: I/O error, dev sda, sector [...] op 0x1: (WRITE) >flags 0x100000 phys_seg 1 prio class 0 >BTRFS error (device dm-0): bdev /dev/mapper/luks-[...] errs: wr 1, rd >0, flush 0, corrupt 0, gen0 > >Note this different than the Fedora 25 resume behavior. In F25 with >4.8.6, the screen doesn't power on, but the system seems responsive >otherwise. For example ctrl-alt-delete reboots after 60 seconds as >expected. (In Qubes, after resuming a second or third time and getting >disk errors, when you try to shutdown it will just hang indefinitely.) >But F25 was running from a USB drive so I wouldn't necessarily know if >there were SATA errors in that case. > >I'll see if I can figure out how to apply the patch to the latest 4.1 >(F31-based) and try it from there. In the mean time, if anyone has any >ideas please share. > >-- >You received this message because you are subscribed to a topic in the >Google Groups "qubes-users" group. >To unsubscribe from this topic, visit >https://groups.google.com/d/topic/qubes-users/67LmZ8LsR9A/unsubscribe. >To unsubscribe from this group and all its topics, send an email to >qubes-users+unsubscr...@googlegroups.com. >To view this discussion on the web visit >https://groups.google.com/d/msgid/qubes-users/8b5cad4abcdce9da863ab033c86752d7%40disroot.org. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/86C1ED2B-2651-459F-BF1C-D927C2A2EFA1%40v6ak.com.
