From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 61011] New: Radeon Screen Corruption since merged patch of Bug 60639
Date: Sun, 08 Sep 2013 18:49:39 +0000 [thread overview]
Message-ID: <bug-61011-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=61011
Bug ID: 61011
Summary: Radeon Screen Corruption since merged patch of Bug
60639
Product: Drivers
Version: 2.5
Kernel Version: 3.10.5
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: Hamsi2k@freenet.de
Regression: No
Created attachment 107641
--> https://bugzilla.kernel.org/attachment.cgi?id=107641&action=edit
This is the result
I own a board: 880GMH/U3S3 with radeon chipset HD 4250.
Since I upgraded to kernel 3.10.5 I get some screen corruption (shown in
attached picture). Then I used git bisect to track down the commit between the
last working kernel 3.10.2 and 3.10.5. The commit in question is
6f8bbaf568c7f2c497558bfd04654c0b9841ad57 which points to
https://bugzilla.kernel.org/show_bug.cgi?id=60639.
Without this commit I was able to build and run the 3.11.0 kernel release.
This is also the version, which attached log files refers to.
As reference: I created an thread
https://bbs.archlinux.org/viewtopic.php?id=169361 where I first described my
problem.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2013-09-08 18:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-08 18:49 bugzilla-daemon [this message]
2013-09-08 18:57 ` [Bug 61011] Radeon Screen Corruption since merged patch of Bug 60639 bugzilla-daemon
2013-09-08 18:58 ` bugzilla-daemon
2013-09-08 18:58 ` bugzilla-daemon
2013-09-08 18:58 ` bugzilla-daemon
2013-09-08 19:17 ` bugzilla-daemon
2013-09-08 21:39 ` bugzilla-daemon
2013-09-09 4:29 ` 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-61011-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox