From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 80901] [radeon] loading corrupts lspci entry + unloading crashes kernel
Date: Tue, 22 Jul 2014 14:36:45 +0000 [thread overview]
Message-ID: <bug-80901-2300-zaisEOeLtJ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-80901-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=80901
--- Comment #4 from Andrea Paternò <amerryfellow@gmail.com> ---
It does.
gandalf@the_shire ~ » LIBGL_DEBUG=1 DRI_PRIME=1 glxinfo | grep "renderer
string"
libGL: Can't open configuration file /home/gandalf/.drirc: No such file or
directory.
libGL: Can't open configuration file /home/gandalf/.drirc: No such file or
directory.
OpenGL renderer string: Gallium 0.4 on AMD CAPE VERDE
Also, I just noticed that everytime I lauch anithing with PRIME, it takes a few
seconds before returning the output. If you check the dmesg output I just
attached, you'll see that it shows several driver-related outputs. Basically It
prints them out everytime I lauch the program with PRIME
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-07-22 14:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 14:00 [Bug 80901] New: [radeon] loading corrupts lspci entry + unloading crashes kernel bugzilla-daemon
2014-07-22 14:02 ` [Bug 80901] " bugzilla-daemon
2014-07-22 14:04 ` bugzilla-daemon
2014-07-22 14:05 ` bugzilla-daemon
2014-07-22 14:05 ` bugzilla-daemon
2014-07-22 14:05 ` bugzilla-daemon
2014-07-22 14:29 ` bugzilla-daemon
2014-07-22 14:36 ` bugzilla-daemon [this message]
2014-07-22 14:37 ` bugzilla-daemon
2014-07-22 16:13 ` bugzilla-daemon
2014-07-22 18:00 ` bugzilla-daemon
2014-07-22 18:30 ` bugzilla-daemon
2014-07-22 18:41 ` bugzilla-daemon
2014-07-22 20:57 ` bugzilla-daemon
2014-07-22 22:22 ` 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-80901-2300-zaisEOeLtJ@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.