Re: pci=no_e820 report for vmware fusion

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

 



On 16 Jun 2022, at 16:40, Bjorn Helgaas wrote:

> The badness would definitely be interesting (the entire dmesg log), as

Here it is:
https://bcodding.com/d/dmesg_pci_badness.txt

> well as a dmesg log collected with "pci=no_e820".  I'll attach them to
> this bugzilla [1].

https://bcodding.com/d/dmesg_pci_no_e820_param.txt

> Generally I expect PCI devices to work even if we reassign their BARs
> before a driver claims them.  But apparently some do not, and I'm
> always curious about which ones they are.
>
> If you could confirm that Hans' revert [2] avoids the problem without
> needing "pci=no_e820", that would be awesome, too.

I can confirm that the Hans' revert avoids the problem without having the
kernel param set.  I've only booted it, not done any other PCI testing.

Ben




[Index of Archives]     [DMA Engine]     [Linux Coverity]     [Linux USB]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Greybus]

  Powered by Linux