Re: [coreboot] Why my ACPI device conflicts with "PCI Bus"

[Marshall Dawson]

Hi Zheng,

What version of Windows are you using?  I've seen differences in the
behavior of the arbiters as Windows has matured.  I don't notice anything
incorrect in your ASL.  Does your FUR1 device come up with no conflicts,
and only FUR0 has problems?

Are you able to run WinDbg and get the failure?  Depending on the
generation, you might have Ethernet or USB available for debug as well, if
you need a different option.  I might start with this:
https://msdn.microsoft.com/en-us/library/windows/hardware/ff562124(v=vs.85)....
... using "!arbiter 2" to dump the memory assigned in the system.  That
would hopefully show you the conflict ('C' flag) and ownership, possibly
giving you additional clues and a direction to look.  In theory, this
should be somewhat identical to looking at resources-by-connection in the
Device Manager, but you'll have more options for debugging.

Maybe also dump the device tree with "!devnode 0 1" and make sure items are
scoped where you believe they should be.

The fact that FEDC6000 is used by PCI Bus seems pretty odd, like the bus
consumes the memory without bridging or arbitrating it.  Unless I missed
it, I don't see anything like that in your DSDT.  As an experiment, maybe
try adding a ResourceProducer for FEDC6000 under PCI0 and see if the
problem goes away.  If it does, I'll have to think more about what that
means.

Thanks,
Marshall

On Mon, Aug 22, 2016 at 6:20 AM, Zheng Bao  wrote:
> Hi, All,
>
> I am debugging the UART device on Bettong(AMD Carrizo).
>
> The device
>
> "
> Device(FUR0) {
>     Name(_HID,"AMD0020")
>     Name(_UID,0x0)
>     Name(_CRS, ResourceTemplate() {
>         IRQ(Edge, ActiveHigh, Exclusive) {10}
>         Memory32Fixed(ReadWrite, 0xFEDC6000, 0x2000)
>     })
>     Method (_STA, 0x0, NotSerialized) {
>         Return (0x0F)
>     }
> }
> "
>
> is  added to DSDT. On linux, it doesnt show any error or warning. On
> Windows,
>
> the device manager can show the DEVICE "AMD0020". But it says the
> 0xFEDC6000
>
> is used by other device "PCI Bus".
>
> I checked the whole DSDT and can not find which device conflicts with that?
>
> Any suggestion what else I can check?
>
> Zheng