From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 76840] HybridGraphics: Kernel driver in use: radeon but adapter not listed
Date: Mon, 31 Mar 2014 15:32:14 +0000 [thread overview]
Message-ID: <bug-76840-502-aS8Y7CLkWt@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-76840-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2254 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=76840
--- Comment #7 from Michael Eagle <xanto@egaming.ro> ---
Sorry, seems like the comment I entered just vanished,
So, without my xorg conf, X server crashes with the following:
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Mar 31 18:11:05 2014
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension SECURITY
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension SELinux
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
(II) [KMS] Kernel modesetting enabled.
X: ../../../../include/privates.h:123: dixGetPrivateAddr: Assertion
`key->initialized' failed.
If I restart mdm once again or if I execute, startx. Then the system hangs, and
I can't access any VTYs but I can reboot with CTRL + Alt + del.
However, if I rmmod the radeon driver and then modprobe it once again. I get
kernel panic, and I could only reboot from the powerbutton.
Attached images from above represents crash backtrace messages after modprobe
fails.
Hope it helps,
Thank you.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3084 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:[~2014-03-31 15:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 14:40 [Bug 76840] New: HybridGraphics: Kernel driver in use: radeon but adapter not listed bugzilla-daemon
2014-03-31 14:51 ` [Bug 76840] " bugzilla-daemon
2014-03-31 14:58 ` bugzilla-daemon
2014-03-31 15:00 ` bugzilla-daemon
2014-03-31 15:27 ` bugzilla-daemon
2014-03-31 15:28 ` bugzilla-daemon
2014-03-31 15:28 ` bugzilla-daemon
2014-03-31 15:32 ` bugzilla-daemon [this message]
2014-04-04 19:15 ` bugzilla-daemon
2015-11-20 16:09 ` 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-76840-502-aS8Y7CLkWt@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