On Mon, 30 Mar 2026, Bernd Schumacher wrote: > Am Sonntag, dem 29.03.2026 um 18:22 +0200 schrieb Lukas Wunner: > > Could you repeat this and add log_buf_len=16M to the kernel command > > line > > so that the dmesg output isn't truncated? > > I have now added to /etc/default/grub: > GRUB_CMDLINE_LINUX="\"dyndbg=file log_buf_len=16M drivers/pci/* +p\"" > attached is the dmesg result for 6.12.73
Hi, This doesn't look like a resource assignment issue to me. HOWEVER, despite the assignment being successful, what is worth a note is that BAR 0 changes during resource fitting: pci 0000:07:00.0: BAR 0 [mem 0xfffffffffc500000-0xfffffffffc50ffff 64bit]: can't claim; no compatible bridge window pci 0000:07:00.0: BAR 0 [mem 0xfc500000-0xfc50ffff 64bit]: assigned That is 0xffffffff -> 0x0 for the high order bits happens to match with the change Lukas noted (I've not digged deeply into the logs beyond checking the resource fitting/assignment results from the latest log). Perhaps something on the save/restore side still holds the old value despite the resource & BAR were changed during resource fitting? -- i.
