[qubes-users] HCL - Thinkpad T14 Gen1 Intel
-- Mustafa -- 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/CAMz_NCo3jfVast0KeuFBOL2L3Wah_43Ys-a%3DH8v_TwGeVVAtEg%40mail.gmail.com. Qubes-HCL-LENOVO-20S00044UK-20210826-140136.yml Description: application/yaml
Re: [qubes-users] Qubes-backup verify only verifies dom0, not appVMs
On Wed, Aug 25, 2021 at 07:31:33AM -0700, Andrew David Wong wrote: And in fact only dom0 gets verified, the others seem to be ignored. I cannot seem to reproduce this. My verify-only attempts also verify domUs. I'm using the same qvm-backup-restore command, just without `--verbose`. That's very strange. Are restore settings stored anywhere on the local machine, like how VMs can have an "exclude from backups" option? -- 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/YSeUe5O1IEUt12if%40danwin1210.me.
Re: [qubes-users] Qubes-backup verify only verifies dom0, not appVMs
On 8/26/21 6:17 AM, tetrahedra via qubes-users wrote: On Wed, Aug 25, 2021 at 07:31:33AM -0700, Andrew David Wong wrote: And in fact only dom0 gets verified, the others seem to be ignored. I cannot seem to reproduce this. My verify-only attempts also verify domUs. I'm using the same qvm-backup-restore command, just without `--verbose`. That's very strange. Are restore settings stored anywhere on the local machine, like how VMs can have an "exclude from backups" option? It's possible to create "backup profiles," but I haven't personally used them, so I'm not familiar with the details of how they work. This option is mentioned in the `--help` text for qvm-backup but not qvm-backup-restore. -- Andrew David Wong Community Manager The Qubes OS Project https://www.qubes-os.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/5cb81b31-43a2-bd70-556e-56329dce446a%40qubes-os.org. OpenPGP_signature Description: OpenPGP digital signature
[qubes-users] Trezor in Qubes
Hello all, I would like to start to use Trezor with my qubes. I would like to follow this guide here https://wiki.trezor.io/Qubes_OS. My intention is to use the Trezor HW wallet in a anon-whonix AppVm with Trezor Suite qube through Tor. I run qubes on X230 Nitropad. I would like to check if the guide to install the Trezor Bridge and Udev rules in the sys-usb (see the official Trezor guide) is advised by qubes community or is it good practice not to install anything in the sys-usb and instead install the packages (bridge, udev rules and suite) in the target anon-whonix AppVM. -- 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/ed217635-97a2-33c8-f786-c9966b331094%40mailbox.org.
[qubes-users] resume from suspend issue after QSB-070
After installing yesterday's patches, my laptop cannot resume from sleep. I have gone through the /sys/power/pm_test procedure to see anything interesting. Only this when doing the 'core' test: [ 2330.899224] [ cut here ] [ 2330.899225] WARNING: CPU: 1 PID: 0 at arch/x86/mm/tlb.c:456 switch_mm_irqs_off+0x375/0x3a0 [ 2330.899230] Modules linked in: snd_seq_dummy snd_hrtimer loop ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter vfat fat rmi_smbus rmi_core snd_soc_skl_hda_dsp snd_soc_hdac_hdmi snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_soc_dmic snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof snd_sof_xtensa_dsp snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi uvcvideo iTCO_wdt intel_pmc_bxt ee1004 iTCO_vendor_support videobuf2_vmalloc snd_soc_core videobuf2_memops videobuf2_v4l2 videobuf2_common intel_wmi_thunderbolt snd_compress wmi_bmof intel_rapl_msr snd_pcm_dmaengine ac97_bus videodev snd_hda_intel intel_powerclamp mc snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec snd_hda_core snd_hwdep snd_seq snd_seq_device joydev pcspkr snd_pcm i2c_i801 i2c_smbus ucsi_acpi typec_ucsi snd_timer typec wmi [ 2330.899259] thinkpad_acpi platform_profile ledtrig_audio snd soundcore iwlwifi processor_thermal_device processor_thermal_rfim processor_thermal_mbox processor_thermal_rapl intel_rapl_common cfg80211 intel_pch_thermal intel_soc_dts_iosf intel_hid int3400_thermal sparse_keymap acpi_thermal_rel int3403_thermal thunderbolt int340x_thermal_zone rfkill fuse xenfs ip_tables dm_thin_pool dm_persistent_data dm_bio_prison dm_crypt trusted crct10dif_pclmul crc32_pclmul crc32c_intel nvme i915 xhci_pci xhci_pci_renesas xhci_hcd ghash_clmulni_intel nvme_core i2c_algo_bit drm_kms_helper cec serio_raw drm video pinctrl_cannonlake xen_acpi_processor xen_privcmd xen_pciback xen_blkback xen_gntalloc xen_gntdev xen_evtchn uinput [ 2330.899280] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.12.14-1.fc32.qubes.x86_64 #1 [ 2330.899281] Hardware name: LENOVO 20S00044UK/20S00044UK, BIOS N2XET31W (1.21 ) 06/17/2021 [ 2330.899282] RIP: e030:switch_mm_irqs_off+0x375/0x3a0 [ 2330.899285] Code: 00 00 65 48 89 05 33 87 fa 7e e9 7e fd ff ff b9 49 00 00 00 b8 01 00 00 00 31 d2 0f 30 e9 5e fd ff ff 41 89 f7 e9 a1 fe ff ff <0f> 0b e8 54 fa ff ff e9 fe fc ff ff 0f 0b e9 49 fe ff ff 0f 0b e9 [ 2330.899286] RSP: e02b:c90040103eb8 EFLAGS: 00010006 [ 2330.899287] RAX: 00010cbae000 RBX: 8881002d2780 RCX: 0040 [ 2330.899288] RDX: 8881002d2780 RSI: RDI: 88818cbae000 [ 2330.899289] RBP: 829d7160 R08: R09: 0004 [ 2330.899289] R10: R11: R12: 888100bfee80 [ 2330.899290] R13: R14: 0001 R15: [ 2330.899294] FS: () GS:88816bc4() knlGS: [ 2330.899295] CS: 1e030 DS: 002b ES: 002b CR0: 80050033 [ 2330.899296] CR2: 7f2c50011766 CR3: 0281 CR4: 00050660 [ 2330.899298] Call Trace: [ 2330.899302] switch_mm+0x1c/0x30 [ 2330.899304] play_dead_common+0xa/0x20 [ 2330.899323] xen_pv_play_dead+0xa/0x60 [ 2330.899325] do_idle+0xc7/0xe0 [ 2330.899327] cpu_startup_entry+0x19/0x20 [ 2330.899329] asm_cpu_bringup_and_idle+0x5/0x1000 [ 2330.899332] ---[ end trace a14329e4cbb028c0 ]--- [ 2331.001403] smpboot: CPU 1 is now offline [ 2331.003746] smpboot: CPU 2 is now offline [ 2331.007186] smpboot: CPU 3 is now offline [ 2331.013292] PM: suspend debug: Waiting for 5 second(s). [ 2336.013713] xen_acpi_processor: Uploading Xen processor PM info [ 2336.013724] xen_acpi_processor: (_PXX): Hypervisor error (-19) for ACPI CPU5 [ 2336.013726] xen_acpi_processor: (_PXX): Hypervisor error (-19) for ACPI CPU6 [ 2336.013727] xen_acpi_processor: (_PXX): Hypervisor error (-19) for ACPI CPU7 [ 2336.013728] xen_acpi_processor: (_PXX): Hypervisor error (-19) for ACPI CPU8 [ 2336.013736] Enabling non-boot CPUs ... [ 2336.013740] installing Xen timer for CPU 1 [ 2336.014046] cpu 1 spinlock event irq 131 [ 2336.014279] ACPI: \_SB_.PR01: Found 3 idle states [ 2336.014526] CPU1 is up [ 2336.014531] installing Xen timer for CPU 2 [ 2336.014758] cpu 2 spinlock event irq 137 [ 2336.014949] ACPI: \_SB_.PR02: Found 3 idle states [ 2336.015018] CPU2 is up [ 2336.015021] installing Xen timer for CPU 3 [ 2336.015279] cpu 3 spinlock event irq 143 [ 2336.015580] ACPI: \_SB_.PR03: Found 3 idle states [ 2336.015657] CPU3 is up [ 2336.015659] ACPI: EC: EC started [ 2336.015784] ACPI: Waking up from system sleep state S3 [ 2336.108923] ACPI: EC: interrupt unblocked [ 2336.152769] ACPI: EC: event unblocked [ 2336.171389] nvme nvme0: Shutdown timeout set to 8 seconds [ 2336.180153] nvme nvme0: 4
Re: [qubes-users] resume from suspend issue after QSB-070
Kind of answering my own question, but disabling hyperthreading happened to be a workaround for the resume from suspend issue. Hint: [ 2336.013724] xen_acpi_processor: (_PXX): Hypervisor error (-19) for ACPI CPU5 [ 2336.013726] xen_acpi_processor: (_PXX): Hypervisor error (-19) for ACPI CPU6 [ 2336.013727] xen_acpi_processor: (_PXX): Hypervisor error (-19) for ACPI CPU7 [ 2336.013728] xen_acpi_processor: (_PXX): Hypervisor error (-19) for ACPI CPU8 Mustafa Kuscu , 26 Ağu 2021 Per, 17:53 tarihinde şunu yazdı: > > After installing yesterday's patches, my laptop cannot resume from sleep. > > I have gone through the /sys/power/pm_test procedure to see anything > interesting. > > Only this when doing the 'core' test: > > [ 2330.899224] [ cut here ] > [ 2330.899225] WARNING: CPU: 1 PID: 0 at arch/x86/mm/tlb.c:456 > switch_mm_irqs_off+0x375/0x3a0 > [ 2330.899230] Modules linked in: snd_seq_dummy snd_hrtimer loop > ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter vfat fat > rmi_smbus rmi_core snd_soc_skl_hda_dsp snd_soc_hdac_hdmi snd_hda_codec_hdmi > snd_hda_codec_realtek snd_hda_codec_generic snd_soc_dmic > snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel > soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda > snd_sof_pci snd_sof snd_sof_xtensa_dsp snd_soc_skl snd_soc_hdac_hda > snd_hda_ext_core snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match > snd_soc_acpi uvcvideo iTCO_wdt intel_pmc_bxt ee1004 iTCO_vendor_support > videobuf2_vmalloc snd_soc_core videobuf2_memops videobuf2_v4l2 > videobuf2_common intel_wmi_thunderbolt snd_compress wmi_bmof intel_rapl_msr > snd_pcm_dmaengine ac97_bus videodev snd_hda_intel intel_powerclamp mc > snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec snd_hda_core snd_hwdep > snd_seq snd_seq_device joydev pcspkr snd_pcm i2c_i801 i2c_smbus ucsi_acpi > typec_ucsi snd_timer typec wmi > [ 2330.899259] thinkpad_acpi platform_profile ledtrig_audio snd soundcore > iwlwifi processor_thermal_device processor_thermal_rfim > processor_thermal_mbox processor_thermal_rapl intel_rapl_common cfg80211 > intel_pch_thermal intel_soc_dts_iosf intel_hid int3400_thermal > sparse_keymap acpi_thermal_rel int3403_thermal thunderbolt > int340x_thermal_zone rfkill fuse xenfs ip_tables dm_thin_pool > dm_persistent_data dm_bio_prison dm_crypt trusted crct10dif_pclmul > crc32_pclmul crc32c_intel nvme i915 xhci_pci xhci_pci_renesas xhci_hcd > ghash_clmulni_intel nvme_core i2c_algo_bit drm_kms_helper cec serio_raw drm > video pinctrl_cannonlake xen_acpi_processor xen_privcmd xen_pciback > xen_blkback xen_gntalloc xen_gntdev xen_evtchn uinput > [ 2330.899280] CPU: 1 PID: 0 Comm: swapper/1 Not tainted > 5.12.14-1.fc32.qubes.x86_64 #1 > [ 2330.899281] Hardware name: LENOVO 20S00044UK/20S00044UK, BIOS N2XET31W > (1.21 ) 06/17/2021 > [ 2330.899282] RIP: e030:switch_mm_irqs_off+0x375/0x3a0 > [ 2330.899285] Code: 00 00 65 48 89 05 33 87 fa 7e e9 7e fd ff ff b9 49 00 > 00 00 b8 01 00 00 00 31 d2 0f 30 e9 5e fd ff ff 41 89 f7 e9 a1 fe ff ff > <0f> 0b e8 54 fa ff ff e9 fe fc ff ff 0f 0b e9 49 fe ff ff 0f 0b e9 > [ 2330.899286] RSP: e02b:c90040103eb8 EFLAGS: 00010006 > [ 2330.899287] RAX: 00010cbae000 RBX: 8881002d2780 RCX: > 0040 > [ 2330.899288] RDX: 8881002d2780 RSI: RDI: > 88818cbae000 > [ 2330.899289] RBP: 829d7160 R08: R09: > 0004 > [ 2330.899289] R10: R11: R12: > 888100bfee80 > [ 2330.899290] R13: R14: 0001 R15: > > [ 2330.899294] FS: () GS:88816bc4() > knlGS: > [ 2330.899295] CS: 1e030 DS: 002b ES: 002b CR0: 80050033 > [ 2330.899296] CR2: 7f2c50011766 CR3: 0281 CR4: > 00050660 > [ 2330.899298] Call Trace: > [ 2330.899302] switch_mm+0x1c/0x30 > [ 2330.899304] play_dead_common+0xa/0x20 > [ 2330.899323] xen_pv_play_dead+0xa/0x60 > [ 2330.899325] do_idle+0xc7/0xe0 > [ 2330.899327] cpu_startup_entry+0x19/0x20 > [ 2330.899329] asm_cpu_bringup_and_idle+0x5/0x1000 > [ 2330.899332] ---[ end trace a14329e4cbb028c0 ]--- > [ 2331.001403] smpboot: CPU 1 is now offline > [ 2331.003746] smpboot: CPU 2 is now offline > [ 2331.007186] smpboot: CPU 3 is now offline > [ 2331.013292] PM: suspend debug: Waiting for 5 second(s). > [ 2336.013713] xen_acpi_processor: Uploading Xen processor PM info > [ 2336.013724] xen_acpi_processor: (_PXX): Hypervisor error (-19) for ACPI > CPU5 > [ 2336.013726] xen_acpi_processor: (_PXX): Hypervisor error (-19) for ACPI > CPU6 > [ 2336.013727] xen_acpi_processor: (_PXX): Hypervisor error (-19) for ACPI > CPU7 > [ 2336.013728] xen_acpi_processor: (_PXX): Hypervisor error (-19) for ACPI > CPU8 > [ 2336.013736] Enabling non-boot CPUs ... > [ 2336.013740] installing Xen timer for CPU 1 > [ 2336.014046] cpu 1 spinlock event irq 131 > [ 2336.014279] ACPI: \_SB_.PR01: Found 3 idl
Re: [qubes-users] resume from suspend issue after QSB-070
On 8/26/21 1:55 PM, Mustafa Kuscu wrote: Kind of answering my own question, but disabling hyperthreading happened to be a workaround for the resume from suspend issue. But shouldn't hyperthreading have already been disabled ever since QSB-043? https://www.qubes-os.org/news/2018/09/02/qsb-43/ -- Andrew David Wong Community Manager The Qubes OS Project https://www.qubes-os.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/6a2ea46d-16fd-e859-173e-88796ccdec02%40qubes-os.org. OpenPGP_signature Description: OpenPGP digital signature
Re: [qubes-users] resume from suspend issue after QSB-070
Thanks for putting effort into publishing the invaluable QSAs. I am now reading them. Andrew David Wong , 26 Ağu 2021 Per, 21:11 tarihinde şunu yazdı: > On 8/26/21 1:55 PM, Mustafa Kuscu wrote: > > Kind of answering my own question, but disabling hyperthreading happened > to > > be a workaround for the resume from suspend issue. > > But shouldn't hyperthreading have already been disabled ever since QSB-043? > > https://www.qubes-os.org/news/2018/09/02/qsb-43/ > > -- > Andrew David Wong > Community Manager > The Qubes OS Project > https://www.qubes-os.org > > -- Mustafa -- 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/CAMz_NCpO_FC4jj-NLyVrnh%3Df84YnMgXGMJ%3DRUau3NE7uq%2B08Dg%40mail.gmail.com.
