[PING^3][PATCH v2] PCI: Sanitise firmware BAR assignments behind a PCI-PCI bridge

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 2 Mar 2022, Maciej W. Rozycki wrote:

> > > Fix an issue with the Tyan Tomcat IV S1564D system, the BIOS of which 
> > > does not assign PCI buses beyond #2, where our resource reallocation 
> > > code preserves the reset default of an I/O BAR assignment outside its 
> > > upstream PCI-to-PCI bridge's I/O forwarding range for device 06:08.0 in 
> > > this log:
> > 
> > Would you mind collecting the complete dmesg log before your patch?
> > It's hard to get the entire picture from snippets.
> 
>  Sure, here's the original log from at the time when I made the patch.  I 
> think it's as verbose as you can get; there's no way I could have used it 
> for the change description.
> 
>  Also I doubt it should matter, but if you need a fresh log instead from 
> 5.17, then I can make one too, but that will take a bit.  Let me know if 
> you need me to try anything else too.

 Ping for:
<https://lore.kernel.org/all/alpine.DEB.2.21.2202010150100.58572@xxxxxxxxxxxxxxxxx/>

Do you need any further information?

  Maciej



[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux