All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [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
Date: Wed, 01 Oct 2014 16:22:19 +0000	[thread overview]
Message-ID: <bug-85311-2300-KtV9QCrTzR@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-85311-2300@https.bugzilla.kernel.org/>

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.

  parent reply	other threads:[~2014-10-01 16:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-30 10:25 [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
2014-09-30 13:33 ` [Bug 85311] " bugzilla-daemon
2014-09-30 14:39 ` bugzilla-daemon
2014-10-01 16:11 ` bugzilla-daemon
2014-10-01 16:22 ` bugzilla-daemon [this message]
2014-10-19 15:50 ` bugzilla-daemon
2014-10-23 15:55 ` bugzilla-daemon
     [not found] <bug-85311-41252@https.bugzilla.kernel.org/>
     [not found] ` <bug-85311-41252-8dDry2SwcF@https.bugzilla.kernel.org/>
2014-10-02 15:48   ` Bjorn Helgaas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-85311-2300-KtV9QCrTzR@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.