From: Peter Zijlstra <peterz@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Harald Arnesen <harald@skogtun.org>,
Ingo Molnar <mingo@kernel.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Giovanni Gherdovich <ggherdovich@suse.cz>
Subject: Re: [BISECTED]: Kernel panic (was: Linux 5.7-rc2)
Date: Tue, 21 Apr 2020 23:41:28 +0200 [thread overview]
Message-ID: <20200421214128.GW2483@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <CAHk-=whhpFhUV51jabGEzHN51aKTL5fbQBvNw9=3cXnO8PXs3A@mail.gmail.com>
On Tue, Apr 21, 2020 at 02:30:06PM -0700, Linus Torvalds wrote:
> Also, see
>
> https://lore.kernel.org/lkml/b90ba443-9b9d-481e-7ecc-d5a25816e02f@oracle.com/
>
> where Dave Kleikamp seems to say that it happens on his Lenovo T410.
>
> So I do think it's real, and _not_ virtualization. Please don't
> dismiss it as some vmware artifact. Looks more like it's triggered by
> some Lenovo Thinkpad BIOS setup issue.
Oh, right (I actually saw that email when I picked up the patches, but
clearly instantly forgot about it again). If the BIOS gets the tables
funny we hit the same paths.
Anyway, it would be good if the reporter can confirm, I've also queued
those patches for /urgent, so they should show up soonish.
next prev parent reply other threads:[~2020-04-21 21:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 21:58 Linux 5.7-rc2 Linus Torvalds
[not found] ` <428bac87-b6dd-0867-c8f8-622cd606de3e@skogtun.org>
2020-04-21 19:03 ` [BISECTED]: Kernel panic (was: Linux 5.7-rc2) Linus Torvalds
2020-04-21 21:23 ` Peter Zijlstra
2020-04-21 21:30 ` Linus Torvalds
2020-04-21 21:41 ` Peter Zijlstra [this message]
2020-04-22 9:02 ` Giovanni Gherdovich
2020-04-22 9:37 ` Harald Arnesen
2020-04-22 10:22 ` Harald Arnesen
2020-04-22 11:01 ` Giovanni Gherdovich
2020-04-22 14:12 ` Dave Kleikamp
2020-04-22 14:49 ` Giovanni Gherdovich
2020-04-22 9:32 ` Harald Arnesen
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=20200421214128.GW2483@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=ggherdovich@suse.cz \
--cc=harald@skogtun.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=torvalds@linux-foundation.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