[Bug 85311] New: radeon 0000:01:00.0: Max Payload Size 16384, but upstream 0000:00:01.0 set to 128; if necessary, use "pci=pcie_bus_safe" and report a bug

[Bug 85311] New: radeon 0000:01:00.0: Max Payload Size 16384, but upstream 0000:00:01.0 set to 128; if necessary, use "pci=pcie_bus_safe" and report a bug

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=85311

            Bug ID: 85311
           Summary: radeon 0000:01:00.0: Max Payload Size 16384, but
                    upstream 0000:00:01.0 set to 128; if necessary, use
                    "pci=pcie_bus_safe" and report a bug
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.17-rc6
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: pali.rohar@gmail.com
        Regression: No

Created attachment 152131
  --> https://bugzilla.kernel.org/attachment.cgi?id=152131&action=edit
dmesg log

Every time when I open LID on my notebook I see tons of new error lines in
dmesg with kernel 3.17-rc6. And more lines come from radeon card (dmesg log is
attached). I do not see these log lines with 3.13 kernel, so this is
regression.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 85311] radeon 0000:01:00.0: Max Payload Size 16384, but upstream 0000:00:01.0 set to 128; if necessary, use "pci=pcie_bus_safe" and report a bug

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=85311

Alex Deucher <alexdeucher@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |alexdeucher@gmail.com

--- Comment #1 from Alex Deucher <alexdeucher@gmail.com> ---
Does radeon.runpm=0 "fix" this?  I think the kernel is trying to access the
device while it is powered off.  Seems like a possible bug in the kernel
runtime pm code.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 85311] radeon 0000:01:00.0: Max Payload Size 16384, but upstream 0000:00:01.0 set to 128; if necessary, use "pci=pcie_bus_safe" and report a bug

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=85311

Bjorn Helgaas <bhelgaas@google.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bhelgaas@google.com
         Regression|No                          |Yes

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 85311] radeon 0000:01:00.0: Max Payload Size 16384, but upstream 0000:00:01.0 set to 128; if necessary, use "pci=pcie_bus_safe" and report a bug

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=85311

--- Comment #2 from Pali Rohár <pali.rohar@gmail.com> ---
Yes, with radeon.runpm=0 radeon lines are not written anymore. But acpi and
i915 are still present.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 85311] radeon 0000:01:00.0: Max Payload Size 16384, but upstream 0000:00:01.0 set to 128; if necessary, use "pci=pcie_bus_safe" and report a bug

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=85311

--- Comment #3 from Alex Deucher <alexdeucher@gmail.com> ---
When the radeon device is powered down, all the PCI registers and BARs read
back as ones. which is why you are seeing the radeon errors.  Apparently the
pci runtime pm code does not properly ask the driver to power the card up
before accessing those registers.  Unfortunately, I'm not that familiar with
the Linux runtime pm code.  I have no idea about the i915 and apci messages.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 85311] radeon 0000:01:00.0: Max Payload Size 16384, but upstream 0000:00:01.0 set to 128; if necessary, use "pci=pcie_bus_safe" and report a bug

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=85311

--- Comment #4 from Pali Rohár <pali.rohar@gmail.com> ---
Ok, so to who or where to report this problem?

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 85311] radeon 0000:01:00.0: Max Payload Size 16384, but upstream 0000:00:01.0 set to 128; if necessary, use "pci=pcie_bus_safe" and report a bug

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=85311

Alan <alan@lxorguk.ukuu.org.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |alan@lxorguk.ukuu.org.uk
          Component|Video(DRI - non Intel)      |PCI
           Assignee|drivers_video-dri@kernel-bu |drivers_pci@kernel-bugs.osd
                   |gs.osdl.org                 |l.org

--- Comment #5 from Alan <alan@lxorguk.ukuu.org.uk> ---
Moving to PCI

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

Re: [Bug 85311] radeon 0000:01:00.0: Max Payload Size 16384, but upstream 0000:00:01.0 set to 128; if necessary, use "pci=pcie_bus_safe" and report a bug

[Bjorn Helgaas]

[+cc linux-pci, linux-pm, Rafael, Alex]

> https://bugzilla.kernel.org/show_bug.cgi?id=85311

Pali reported:

> Every time when I open LID on my notebook I see tons of new error lines in dmesg
> with kernel 3.17-rc6. And more lines come from radeon card (dmesg log is attached).
> I do not see these log lines with 3.13 kernel, so this is regression.

The new error lines are (from the bugzilla attachment):

  i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
  radeon 0000:01:00.0: Max Payload Size 16384, but upstream
0000:00:01.0 set to 128; if necessary, use "pci=pcie_bus_safe" and
report a bug
  pci_bus 0000:02: Allocating resources
  pci_bus 0000:03: Allocating resources
  pci_bus 0000:04: Allocating resources
  pci_bus 0000:05: Allocating resources
  pci_bus 0000:06: Allocating resources
  pci_bus 0000:0e: Allocating resources
  i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
  radeon 0000:01:00.0: Max Payload Size 16384, but upstream
0000:00:01.0 set to 128; if necessary, use "pci=pcie_bus_safe" and
report a bug
  i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
  radeon 0000:01:00.0: Max Payload Size 16384, but upstream
0000:00:01.0 set to 128; if necessary, use "pci=pcie_bus_safe" and
report a bug
  i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
  radeon 0000:01:00.0: Max Payload Size 16384, but upstream
0000:00:01.0 set to 128; if necessary, use "pci=pcie_bus_safe" and
report a bug
  i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
  ...

Using "radeon.runpm=0" gets rid of the radeon MPS complaints, but not
the others.

Alex said (in the bugzilla):

> When the radeon device is powered down, all the PCI registers and BARs read
> back as ones. which is why you are seeing the radeon errors.  Apparently the
> pci runtime pm code does not properly ask the driver to power the card up
> before accessing those registers.  Unfortunately, I'm not that familiar with
> the Linux runtime pm code.  I have no idea about the i915 and apci messages.

I haven't looked into this at all, so I don't know where this bug
report belongs.

Bjorn