From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B441F14A4EB for ; Mon, 14 Oct 2024 09:36:18 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1728898578; cv=none; b=e/RUNesbFbuanVckxHF/6D1x9XjIp8Ioa32N5CbWJmHmMRmBDb9+vqOp7/wvoZoYHjdXFn//CwJUYpgy66h38W2huTYxvNhiYCrnvJUtTpRaeD1rIfc+vEWni9uo7mPVRUuTRT6gJTntVxLvBP+9fZlz5ARtUOoLB+AQvLutK2Y= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1728898578; c=relaxed/simple; bh=X4c4DYREX/ZJZTtRi5mewGr0H7zDAmpnDr297ANrBts=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=qXfXrgKEjAQcwcWzvYVAhJq1rW3+UEnDxHcNN9ckqXR/RIS2lqVs8yY2jLO6RA9/VKdehO1sPLdo/Vf0+4PuJjdZ6PSI8edQksDphboHp7riC+l40RvG6quiIu6KURoaFjwiPC1h6zrzrLLYIo5RiFsRTcyNzaaudIJP9TyZh4E= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=CO9gB51O; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="CO9gB51O" Received: by smtp.kernel.org (Postfix) with ESMTPSA id BE20DC4CEC3; Mon, 14 Oct 2024 09:36:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1728898578; bh=X4c4DYREX/ZJZTtRi5mewGr0H7zDAmpnDr297ANrBts=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=CO9gB51OYDk/2TQUCW18fFb4tP8mJkHUXC4l34ovr4RDwOxKrDoxEcxopgmbEZYPu +GLx20RbRLwp6XscLc727bXqgV1eoqZ6oWniDvJ9qnWzqAzsgj1H3ld/oMWJnjEM7+ jqVff94Hs+Im5zex+G4P1AXrdHNl+I9XIL0nSdXk= Date: Mon, 14 Oct 2024 11:36:15 +0200 From: Greg KH To: Jinpu Wang Cc: stable , Kan Liang , baolu.lu@linux.intel.com, jroedel@suse.de, Sasha Levin , x86@kernel.org Subject: Re: [regression]Boot Hang on Kernel 6.1.83+ with Dell PowerEdge R770 and Intel Xeon 6710E Message-ID: <2024101401-reawake-posture-01fd@gregkh> References: <2024101006-scanner-unboxed-0190@gregkh> <2024101000-duplex-justify-97e6@gregkh> Precedence: bulk X-Mailing-List: stable@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: On Thu, Oct 10, 2024 at 12:10:49PM +0200, Jinpu Wang wrote: > Hi Greg, > > > On Thu, Oct 10, 2024 at 11:31 AM Greg KH wrote: > > > > 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 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. > > > I think better to revert both: > 8c91a4bfc7f8 ("iommu: Fix compilation without CONFIG_IOMMU_INTEL") > 586e19c88a0c ("iommu/vt-d: Retrieve IOMMU perfmon capability information") Can you send reverts for these, or do you need us to do this for you? thanks, greg k-h