Re: [EXT] Re: [qubes-users] resume from suspend issue after QSB-070

2021-09-04 Thread haaber
On 9/3/21 11:41 PM, Marek Marczykowski-Górecki wrote: [...]I'm confused. I was under the impression that Qubes OS (after the QSB-043 patches) automatically disables hyper-threading for you such that you don't have to know anything, do anything, or read any past QSBs. [] There are (at

Re: [EXT] Re: [qubes-users] resume from suspend issue after QSB-070

2021-09-03 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 > >>> Marek Marczykowski-Górecki 31.08.2021, 02:52 >>> > On Mon, Aug 30, 2021 at 05:39:40PM -0700, Andrew David Wong wrote: > > On 8/30/21 2:12 PM, haaber wrote: > > > > > > > > Kind of answering my own question, but disabling hyperthreading > > > >

Re: [qubes-users] resume from suspend issue after QSB-070

2021-08-31 Thread haaber
[Andrew] But shouldn't hyperthreading have already been disabled ever since QSB-043? https://www.qubes-os.org/news/2018/09/02/qsb-43/ >>> I admit that I missed that one as well. Shame on me. Is there some way >>> to detect active hyperthreading on boot && print out

Re: [qubes-users] resume from suspend issue after QSB-070

2021-08-30 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, Aug 30, 2021 at 05:39:40PM -0700, Andrew David Wong wrote: > On 8/30/21 2:12 PM, haaber wrote: > > > > > > Kind of answering my own question, but disabling hyperthreading > > > > happened to > > > > be a workaround for the resume from

Re: [qubes-users] resume from suspend issue after QSB-070

2021-08-30 Thread Andrew David Wong
On 8/30/21 5:39 PM, Andrew David Wong wrote: On 8/30/21 2:12 PM, haaber 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?

Re: [qubes-users] resume from suspend issue after QSB-070

2021-08-30 Thread Andrew David Wong
On 8/30/21 2:12 PM, haaber 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/ I

Re: [qubes-users] resume from suspend issue after QSB-070

2021-08-30 Thread haaber
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/ I admit that I missed that one as

Re: [qubes-users] resume from suspend issue after QSB-070

2021-08-26 Thread Mustafa Kuscu
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

Re: [qubes-users] resume from suspend issue after QSB-070

2021-08-26 Thread Andrew David Wong
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/

Re: [qubes-users] resume from suspend issue after QSB-070

2021-08-26 Thread Mustafa Kuscu
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 [