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
-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
> > > >
[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
-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
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?
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
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
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
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/
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
[
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
11 matches
Mail list logo
