From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [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
Date: Tue, 30 Sep 2014 10:25:06 +0000 [thread overview]
Message-ID: <bug-85311-2300@https.bugzilla.kernel.org/> (raw)
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.
next reply other threads:[~2014-09-30 10:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 10:25 bugzilla-daemon [this message]
2014-09-30 13:33 ` [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
2014-09-30 14:39 ` bugzilla-daemon
2014-10-01 16:11 ` bugzilla-daemon
2014-10-01 16:22 ` bugzilla-daemon
2014-10-19 15:50 ` bugzilla-daemon
2014-10-23 15:55 ` bugzilla-daemon
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@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.