From: Dan Williams <dan.j.williams@intel.com>
To: Dave Hansen <dave.hansen@intel.com>,
Mark Brown <broonie@kernel.org>, Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"Pawan Gupta" <pawan.kumar.gupta@linux.intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"Dan Williams" <dan.j.williams@intel.com>
Cc: <x86@kernel.org>, <linux-kernel@vger.kernel.org>,
<gregkh@linuxfoundation.org>
Subject: Re: x86 boot issues in -next
Date: Fri, 1 Mar 2024 14:17:40 -0800 [thread overview]
Message-ID: <65e254047fbce_2bce9294cf@dwillia2-mobl3.amr.corp.intel.com.notmuch> (raw)
In-Reply-To: <71f9b0b7-190f-453c-b55b-c842db4a825d@intel.com>
[ add Greg ]
Dave Hansen wrote:
> On 3/1/24 13:29, Mark Brown wrote:
> > For the past few days -next has been failing to boot an x86_64 defconfig
> > on the x86 machine Linaro has available in their lab. DMI says it's a
> > "Dell Inc. PowerEdge R200/0TY019, BIOS 1.4.3 05/15/2009" and the CPU is
> > described as "Intel(R) Xeon(R) CPU X3220 @ 2.40GHz (family: 0x6, model:
> > 0xf, stepping: 0xb)", it's running happily with mainline and
> > pending-fixes.
>
> This wouldn't explain the bisect results, but there's been a crash fixed
> in here:
>
> > https://lore.kernel.org/all/170863445442.1479840.1818801787239831650.stgit@dwillia2-xfh.jf.intel.com/
>
> that looks pretty similar to your signature.
>
> Could you give Dan's patch a shot?
>
Hey Greg, this indeed looks like something that will be fixed when you
update driver-core-next.
http://lore.kernel.org/r/2024022342-unbroken-september-e58d@gregkh
next prev parent reply other threads:[~2024-03-01 22:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 21:29 Mark Brown
2024-03-01 21:48 ` Dave Hansen
2024-03-01 22:17 ` Dan Williams [this message]
2024-03-02 15:22 ` Greg KH
2024-03-04 18:04 ` Mark Brown
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=65e254047fbce_2bce9294cf@dwillia2-mobl3.amr.corp.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=broonie@kernel.org \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=pbonzini@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
all inboxes | Powered by JetHome®