From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 35531] New: Kernel 2.6.36 series, xf86-video-ati 6.14.0 kernel blows up
Date: Mon, 21 Mar 2011 21:26:00 -0700 (PDT) [thread overview]
Message-ID: <bug-35531-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=35531
Summary: Kernel 2.6.36 series, xf86-video-ati 6.14.0 kernel
blows up
Product: DRI
Version: unspecified
Platform: x86 (IA32)
URL: https://bugs.gentoo.org/show_bug.cgi?id=349247
OS/Version: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: chris2k01@hotmail.com
Created an attachment (id=44703)
--> (https://bugs.freedesktop.org/attachment.cgi?id=44703)
dmesg output from a successful attempt
When booting up Xorg server 1.9.2 with xf86-video-ati-6.14.0 and kernel
2.6.36-gentoo-r5 (distro-patched kernel, but the same problem doesn't appear in
2.6.35-g-r12), as soon as X starts, my monitor goes into DPMS powersave and I
get backtraces in dmesg.
A Gentoo developer suggested booting with kernel command-line parameter
"radeon.agpmode=-1". This didn't help.
I've attached dmesg output from a successful startup with 2.6.35, and will
attach dmesg output from failed startups with and without agpmode=-1
momentarily (looks like only one file can be attached at bug creation time).
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-03-22 4:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 4:26 bugzilla-daemon [this message]
2011-03-22 4:26 ` [Bug 35531] Kernel 2.6.36 series, xf86-video-ati 6.14.0 kernel blows up bugzilla-daemon
2011-03-22 4:26 ` bugzilla-daemon
2011-03-22 4:42 ` bugzilla-daemon
2011-03-23 5:42 ` bugzilla-daemon
2011-03-23 5:42 ` 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-35531-502@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 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.