public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jinpu Wang <jinpu.wang@ionos.com>
Cc: stable <stable@vger.kernel.org>,
	Kan Liang <kan.liang@linux.intel.com>,
	baolu.lu@linux.intel.com, jroedel@suse.de,
	Sasha Levin <sashal@kernel.org>,
	x86@kernel.org
Subject: Re: [regression]Boot Hang on Kernel 6.1.83+ with Dell PowerEdge R770 and Intel Xeon 6710E
Date: Thu, 10 Oct 2024 11:31:26 +0200	[thread overview]
Message-ID: <2024101000-duplex-justify-97e6@gregkh> (raw)
In-Reply-To: <CAMGffE=HvMU4Syy7ATEevKQ+izAvndmpQ8-F9HN_WM+3PKwWyw@mail.gmail.com>

On Thu, Oct 10, 2024 at 11:13:42AM +0200, Jinpu Wang wrote:
> Hi Greg,
> 
> On Thu, Oct 10, 2024 at 11:07 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Thu, Oct 10, 2024 at 09:31:37AM +0200, Jinpu Wang wrote:
> > > Hello all,
> > >
> > > We are experiencing a boot hang issue when booting kernel version
> > > 6.1.83+ on a Dell Inc. PowerEdge R770 equipped with an Intel Xeon
> > > 6710E processor. After extensive testing and use of `git bisect`, we
> > > have traced the issue to commit:
> > >
> > > `586e19c88a0c ("iommu/vt-d: Retrieve IOMMU perfmon capability information")`
> > >
> > > This commit appears to be part of a larger patchset, which can be found here:
> > > [Patchset on lore.kernel.org](https://lore.kernel.org/lkml/7c4b3e4e-1c5d-04f1-1891-84f686c94736@linux.intel.com/T/)
> > >
> > > We attempted to boot with the `intel_iommu=off` option, but the system
> > > hangs in the same manner. However, the system boots successfully after
> > > disabling `CONFIG_INTEL_IOMMU_PERF_EVENTS`.
> >
> > Is there any error messages?  Does the latest 6.6.y tree work properly?
> > If so, why not just use that, no new hardware should be using older
> > kernel trees anyway :)
> No error, just hang, I've removed "quiet" and added "debug".
> Yes, the latest 6.6.y tree works for this, but there are other
> problems/dependency we have to solve.

Ok, that implies that we need to add some other patch to 6.1.y, OR we
can revert it from 6.1.y.  Let me know what you think is the better
thing to do.

thanks,

greg k-h

  reply	other threads:[~2024-10-10  9:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-10  7:31 [regression]Boot Hang on Kernel 6.1.83+ with Dell PowerEdge R770 and Intel Xeon 6710E Jinpu Wang
2024-10-10  9:07 ` Greg KH
2024-10-10  9:13   ` Jinpu Wang
2024-10-10  9:31     ` Greg KH [this message]
2024-10-10 10:10       ` Jinpu Wang
2024-10-10 13:25         ` Liang, Kan
2024-10-10 14:00           ` Baolu Lu
2024-10-11  5:22             ` Jinpu Wang
2024-10-14  9:39               ` Jinpu Wang
2024-10-14 13:46                 ` Greg KH
2024-10-14  9:35             ` Greg KH
2024-10-14  9:36         ` Greg KH

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=2024101000-duplex-justify-97e6@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=baolu.lu@linux.intel.com \
    --cc=jinpu.wang@ionos.com \
    --cc=jroedel@suse.de \
    --cc=kan.liang@linux.intel.com \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --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