linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Borislav Petkov <bp@alien8.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "x86@kernel.org" <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	it+linux-x86@molgen.mpg.de
Subject: Re: kernel BUG at arch/x86/kernel/apic/apic.c with Dell server with x2APIC enabled and unset X2APIC
Date: Fri, 21 Feb 2020 17:15:00 +0100	[thread overview]
Message-ID: <834f42cc-a517-6a8c-d1ac-b327171779f1@molgen.mpg.de> (raw)
In-Reply-To: <20200221155706.GJ25747@zn.tnic>

[-- Attachment #1: Type: text/plain, Size: 478 bytes --]

Dear Borislav,


On 2020-02-21 16:57, Borislav Petkov wrote:
> On Fri, Feb 21, 2020 at 03:37:23PM +0100, Paul Menzel wrote:

>> On the Dell PowerEdge T640/04WYPY, BIOS 2.4.8 11/27/2019, Linux 5.4.14 (and 4.19.57) with
>> unset `IRQ_REMAP` and `X86_X2APIC` crashes on start-up, when x2APIC is enabled in the
>> firmware.
> 
> Does it happen with latest 5.5-stable too? I see 5.5.5 is the last one...

It also happens with Linux 5.6-rc2.


Kind regards,

Paul


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5174 bytes --]

  reply	other threads:[~2020-02-21 16:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-21 14:37 kernel BUG at arch/x86/kernel/apic/apic.c with Dell server with x2APIC enabled and unset X2APIC Paul Menzel
2020-02-21 15:57 ` Borislav Petkov
2020-02-21 16:15   ` Paul Menzel [this message]
2020-02-21 16:27     ` Paul Menzel
2020-02-21 16:27 ` Thomas Gleixner
2020-02-24 12:59   ` Paul Menzel
2022-12-02 13:35 ` [tip: x86/apic] x86/apic: Handle no CONFIG_X86_X2APIC on systems with x2APIC enabled by BIOS tip-bot2 for Mateusz Jończyk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=834f42cc-a517-6a8c-d1ac-b327171779f1@molgen.mpg.de \
    --to=pmenzel@molgen.mpg.de \
    --cc=bp@alien8.de \
    --cc=it+linux-x86@molgen.mpg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).