[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2668869.mvXUDI8C0e@natalenko.name>
Date: Mon, 20 Feb 2023 17:40:05 +0100
From: Oleksandr Natalenko <oleksandr@...alenko.name>
To: tglx@...utronix.de, kim.phillips@....com,
Usama Arif <usama.arif@...edance.com>,
David Woodhouse <dwmw2@...radead.org>
Cc: arjan@...ux.intel.com, mingo@...hat.com, bp@...en8.de,
dave.hansen@...ux.intel.com, hpa@...or.com, x86@...nel.org,
pbonzini@...hat.com, paulmck@...nel.org,
linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
rcu@...r.kernel.org, mimoja@...oja.de, hewenliang4@...wei.com,
thomas.lendacky@....com, seanjc@...gle.com, pmenzel@...gen.mpg.de,
fam.zheng@...edance.com, punit.agrawal@...edance.com,
simon.evans@...edance.com, liangma@...ngbit.com
Subject: Re: [PATCH v9 0/8] Parallel CPU bringup for x86_64
Hello.
Thank you for your reply.
On pondělí 20. února 2023 17:20:13 CET David Woodhouse wrote:
> On Mon, 2023-02-20 at 17:08 +0100, Oleksandr Natalenko wrote:
> >
> > I've applied this to the v6.2 kernel, and suspend/resume broke on my
> > Ryzen 5950X desktop. The machine suspends just fine, but on resume
> > the screen stays blank, and there's no visible disk I/O.
> >
> > Reverting the series brings suspend/resume back to working state.
>
> Hm, thanks. What if you add 'no_parallel_bringup' on the command line?
If the `no_parallel_bringup` param is added, the suspend/resume works.
> Is that using X2APIC?
Probably?
```
$ dmesg | grep -i x2apic
[ 0.632740] x2apic: IRQ remapping doesn't support X2APIC mode
```
> If so, what about 'nox2apic' on the command line?
If `no_parallel_bringup` is removed and `nox2apic` is added, then the `x2apic: …` stuff disappears from dmesg, but suspend/resume remains broken.
--
Oleksandr Natalenko (post-factum)
Powered by blists - more mailing lists