From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 56561] kernel > 3.4.7 breaks KMS on rv515 (r300)
Date: Wed, 31 Oct 2012 05:44:53 +0000 [thread overview]
Message-ID: <bug-56561-502-7jMXN85Kdr@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-56561-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 723 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=56561
--- Comment #8 from dmotd <inaudible@simplesuperlativ.es> ---
(In reply to comment #6)
> Do newer kernels work without radeon driver options on the kernel command
> line, in particular without radeon.msi=0?
>
> If not, can you bisect which kernel change introduced the problem?
The kernel command line options do not effect the later kernels.
I will need some spare time to bisect, although this bug report looks to be
relevant,
--
https://bugzilla.redhat.com/show_bug.cgi?id=845745
--
user 'Richard Gration' is running the exact same laptop setup as here and
experiencing identical issues.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1633 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2012-10-31 5:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 1:50 [Bug 56561] New: kernel > 3.4.7 breaks KMS on rv515 (r300) bugzilla-daemon
2012-10-30 2:56 ` [Bug 56561] " bugzilla-daemon
2012-10-30 2:57 ` bugzilla-daemon
2012-10-30 2:58 ` bugzilla-daemon
2012-10-30 2:59 ` bugzilla-daemon
2012-10-30 2:59 ` bugzilla-daemon
2012-10-30 10:33 ` bugzilla-daemon
2012-10-30 14:59 ` bugzilla-daemon
2012-10-31 5:44 ` bugzilla-daemon [this message]
2012-10-31 6:06 ` bugzilla-daemon
2012-10-31 13:32 ` bugzilla-daemon
2019-11-19 8:30 ` 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-56561-502-7jMXN85Kdr@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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