On 2/12/25 10:25 AM, Roger Pau Monné wrote:
On Wed, Feb 12, 2025 at 09:51:16AM +0100, Jan Beulich wrote:
On 12.02.2025 09:33, Oleksii Kurochko wrote:
On 2/11/25 7:39 PM, Roger Pau Monné wrote:
On Tue, Feb 11, 2025 at 12:02:04PM +0100, Roger Pau Monne wrote:
Hello,
The following series aims
On Wed, Feb 12, 2025 at 09:51:16AM +0100, Jan Beulich wrote:
> On 12.02.2025 09:33, Oleksii Kurochko wrote:
> >
> > On 2/11/25 7:39 PM, Roger Pau Monné wrote:
> >> On Tue, Feb 11, 2025 at 12:02:04PM +0100, Roger Pau Monne wrote:
> >>> Hello,
> >>>
> >>> The following series aims to prevent local A
On 12.02.2025 09:33, Oleksii Kurochko wrote:
>
> On 2/11/25 7:39 PM, Roger Pau Monné wrote:
>> On Tue, Feb 11, 2025 at 12:02:04PM +0100, Roger Pau Monne wrote:
>>> Hello,
>>>
>>> The following series aims to prevent local APIC errors from stalling the
>>> shtudown process. On XenServer testing we
On 2/11/25 7:39 PM, Roger Pau Monné wrote:
On Tue, Feb 11, 2025 at 12:02:04PM +0100, Roger Pau Monne wrote:
Hello,
The following series aims to prevent local APIC errors from stalling the
shtudown process. On XenServer testing we have seen reports of AMD
boxes sporadically getting stuck in a
On Tue, Feb 11, 2025 at 12:02:04PM +0100, Roger Pau Monne wrote:
> Hello,
>
> The following series aims to prevent local APIC errors from stalling the
> shtudown process. On XenServer testing we have seen reports of AMD
> boxes sporadically getting stuck in a spam of:
>
> APIC error on CPU0: 00(
Hello,
The following series aims to prevent local APIC errors from stalling the
shtudown process. On XenServer testing we have seen reports of AMD
boxes sporadically getting stuck in a spam of:
APIC error on CPU0: 00(08), Receive accept error
Messages during shutdown, as a result of device inte
