linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Paul Menzel <pmenzel@molgen.mpg.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>
Cc: "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:27:24 +0100	[thread overview]
Message-ID: <87imjzoqhf.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <d573ba1c-0dc4-3016-712a-cc23a8a33d42@molgen.mpg.de>

Paul,

Paul Menzel <pmenzel@molgen.mpg.de> writes:
>
> 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.

>     [    3.883893] Switched APIC routing to physical flat.
>     [    3.888904] ------------[ cut here ]------------
>     [    3.893641] kernel BUG at arch/x86/kernel/apic/apic.c:1616!

So the APIC is not registered.
>
> `noapic` and `acpi=off` separately did not work, but `noapic acpi=off` hit the other
> panic.

I have no idea what you are talking about.

Which command line options are set to reproduce the above?

Also please test the latest stable kernels not some random ones.

Thanks,

        tglx

  parent reply	other threads:[~2020-02-21 16:27 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
2020-02-21 16:27     ` Paul Menzel
2020-02-21 16:27 ` Thomas Gleixner [this message]
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=87imjzoqhf.fsf@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=bp@alien8.de \
    --cc=it+linux-x86@molgen.mpg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pmenzel@molgen.mpg.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).