From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailout3.hostsharing.net (mailout3.hostsharing.net [144.76.133.104]) (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 3467B282F1B; Tue, 14 Apr 2026 05:45:48 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=144.76.133.104 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776145549; cv=none; b=IXAMaN86RY/wN5QIlfUfx3791br7TfY9mXHdGIT7sVT2yES7NMg9Bx71Y1dRBRy9Nm1QUZf3rSNTrE1pe6cF5Jx1qpLZfuAaDD5YMGWZ/8qsLwqvTb9CldsN6h8jofwdCnJ2qBbQpQXr827VfXr7UXvzCIFTVfAfzBrTSI8Ib1Y= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776145549; c=relaxed/simple; bh=h/0SmEXZ0QK4rok0JqrXdt5TO0dmhnBhwH0/E32rHqk=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=ZbEXBjBXrEWsps9OyM8H6BURqdAxidcDJ3lPaqlM35RlX2MNmVs9FOHGzlw1OANkDbeA3P2H1yD6rNJ+kPnWkfm6eJgTSIs2qXtZM7hMK+IpFFfLKUPBJbxRkotlNr6Dui2IXMzgZTGHU6OoOWbS+yMuszVOYErDGt58qzuP6qg= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=wunner.de; spf=pass smtp.mailfrom=wunner.de; arc=none smtp.client-ip=144.76.133.104 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=wunner.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=wunner.de Received: from h08.hostsharing.net (h08.hostsharing.net [83.223.95.28]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (secp384r1) server-digest SHA384 client-signature ECDSA (secp384r1) client-digest SHA384) (Client CN "*.hostsharing.net", Issuer "GlobalSign GCC R6 AlphaSSL CA 2025" (verified OK)) by mailout3.hostsharing.net (Postfix) with ESMTPS id 81E87C2B; Tue, 14 Apr 2026 07:45:39 +0200 (CEST) Received: by h08.hostsharing.net (Postfix, from userid 100393) id 44B32600B21B; Tue, 14 Apr 2026 07:45:39 +0200 (CEST) Date: Tue, 14 Apr 2026 07:45:39 +0200 From: Lukas Wunner To: "Alexandre N." Cc: Bernd Schumacher , Uwe =?iso-8859-1?Q?Kleine-K=F6nig?= , 1131025@bugs.debian.org, Salvatore Bonaccorso , Bjorn Helgaas , "Rafael J. Wysocki" , Mario Limonciello , regressions@lists.linux.dev, stable@vger.kernel.org, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, Alex Williamson , Ilpo =?iso-8859-1?Q?J=E4rvinen?= Subject: Re: Bug#1131025: [6.12.y regression] Regression with 58130e7ce6cb ("PCI/ERR: Ensure error recoverability at all times"): echo vfio-pci >driver_override does not work for DVB Adapter Message-ID: References: <8275e5b86696dec133889713258c2e158a443496.camel@bschu.de> <7173609c404c5444e634dd3ab26f55f2788d82e4.camel@bschu.de> <79618160f928d7ed4ba0a84f3ab420427c5b8d10.camel@bschu.de> Precedence: bulk X-Mailing-List: linux-pci@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Mon, Apr 13, 2026 at 11:01:17PM +0200, Alexandre N. wrote: > On 4/13/26 05:40, Lukas Wunner wrote: > > Could both of you, Alexandre and Bernd, give that patch a spin > > to see if it fixes the issue? > > I confirm that your last patch alone applied to 6.19.11 > works in my case! (no need for 4d4c10f763d7 nor 907a7a2e5bf4) > > Now my host and guest behave like on 6.18.9, including removing the > pci-stub.ids line from my kernel command line since the automatic > handover between ahci <--> vfio-pci is working again. Thanks a lot, glad to hear that. I'm curious what you did so that 4d4c10f763d7 wasn't sufficient to fix the issue. I'd be grateful if you could provide full dmesg output for analysis of a non-working kernel with this debug patch applied: https://lore.kernel.org/all/acvIfI3naoGsOpFE@wunner.de/ and with the following added to the kernel command line log_buf_len=16M dyndbg="file drivers/pci/* +p" and with this option enabled in .config: CONFIG_DYNAMIC_DEBUG=y That would allow me to amend the commit message of the patch with a better explanation why simply backporting 4d4c10f763d7 is not sufficient as a fix. Thanks! Lukas