On Mon, Dec 11, 2023 at 02:52:42PM +0100, Fiona Ebner wrote: > Am 11.12.23 um 08:46 schrieb Igor Mammedov: > > On Fri, 8 Dec 2023 16:47:23 +0100 > > Igor Mammedov <imammedo@xxxxxxxxxx> wrote: > >> On Thu, 7 Dec 2023 17:28:15 -0600 > >> Bjorn Helgaas <helgaas@xxxxxxxxxx> wrote: > >> > >>> What's the actual symptom that this is broken? All these log > >>> fragments show the exact same assignments for BARs 0, 1, 4 and for the > >>> bridge windows. > > The disk never shows up in /dev > > >>> I assume 0000:01:02.0 is the hot-added SCSI HBA, and 00:05.0 is a > >>> bridge leading to it? > >>> > >>> Can you put the complete dmesg logs somewhere? There's a lot of > >>> context missing here. > > Is this still necessary with Igor being able to reproduce the issue? Only if you want help resolving the problem. I don't have time to guess what interesting things might be missing and go back and forth to get them. > >>> Do you have to revert both cc22522fd55e2 and 40613da52b13f to make it > >>> work reliably? If we have to revert something, reverting one would be > >>> better than reverting both. > > Just reverting cc22522fd55e2 is not enough (and cc22522fd55e2 fixes > 40613da52b13f so I can't revert just 40613da52b13f). OK, thanks. So it sounds like our options are to fix it or to revert both. I'm going to be on vacation Dec 16-25, so we have about 3-4 days to figure something out. Bjorn
