* [Bug 80901] [radeon] loading corrupts lspci entry + unloading crashes kernel
2014-07-22 14:00 [Bug 80901] New: [radeon] loading corrupts lspci entry + unloading crashes kernel bugzilla-daemon
@ 2014-07-22 14:02 ` bugzilla-daemon
2014-07-22 14:04 ` bugzilla-daemon
` (12 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: bugzilla-daemon @ 2014-07-22 14:02 UTC (permalink / raw)
To: dri-devel
https://bugzilla.kernel.org/show_bug.cgi?id=80901
--- Comment #1 from Andrea Paternò <amerryfellow@gmail.com> ---
Created attachment 143911
--> https://bugzilla.kernel.org/attachment.cgi?id=143911&action=edit
System Journal log
System log on failure
--
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
^ permalink raw reply [flat|nested] 15+ messages in thread* [Bug 80901] [radeon] loading corrupts lspci entry + unloading crashes kernel
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
` (11 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: bugzilla-daemon @ 2014-07-22 14:04 UTC (permalink / raw)
To: dri-devel
https://bugzilla.kernel.org/show_bug.cgi?id=80901
--- Comment #2 from Andrea Paternò <amerryfellow@gmail.com> ---
Created attachment 143921
--> https://bugzilla.kernel.org/attachment.cgi?id=143921&action=edit
Kernel config
--
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
^ permalink raw reply [flat|nested] 15+ messages in thread* [Bug 80901] [radeon] loading corrupts lspci entry + unloading crashes kernel
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
` (10 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: bugzilla-daemon @ 2014-07-22 14:05 UTC (permalink / raw)
To: dri-devel
https://bugzilla.kernel.org/show_bug.cgi?id=80901
Andrea Paternò <amerryfellow@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #143901|application/octet-stream |text/plain
mime type| |
--
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
^ permalink raw reply [flat|nested] 15+ messages in thread* [Bug 80901] [radeon] loading corrupts lspci entry + unloading crashes kernel
2014-07-22 14:00 [Bug 80901] New: [radeon] loading corrupts lspci entry + unloading crashes kernel bugzilla-daemon
` (2 preceding siblings ...)
2014-07-22 14:05 ` bugzilla-daemon
@ 2014-07-22 14:05 ` bugzilla-daemon
2014-07-22 14:05 ` bugzilla-daemon
` (9 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: bugzilla-daemon @ 2014-07-22 14:05 UTC (permalink / raw)
To: dri-devel
https://bugzilla.kernel.org/show_bug.cgi?id=80901
Andrea Paternò <amerryfellow@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #143911|application/octet-stream |text/plain
mime type| |
--
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
^ permalink raw reply [flat|nested] 15+ messages in thread* [Bug 80901] [radeon] loading corrupts lspci entry + unloading crashes kernel
2014-07-22 14:00 [Bug 80901] New: [radeon] loading corrupts lspci entry + unloading crashes kernel bugzilla-daemon
` (3 preceding siblings ...)
2014-07-22 14:05 ` bugzilla-daemon
@ 2014-07-22 14:05 ` bugzilla-daemon
2014-07-22 14:29 ` bugzilla-daemon
` (8 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: bugzilla-daemon @ 2014-07-22 14:05 UTC (permalink / raw)
To: dri-devel
https://bugzilla.kernel.org/show_bug.cgi?id=80901
Andrea Paternò <amerryfellow@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #143921|application/octet-stream |text/plain
mime type| |
--
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
^ permalink raw reply [flat|nested] 15+ messages in thread* [Bug 80901] [radeon] loading corrupts lspci entry + unloading crashes kernel
2014-07-22 14:00 [Bug 80901] New: [radeon] loading corrupts lspci entry + unloading crashes kernel bugzilla-daemon
` (4 preceding siblings ...)
2014-07-22 14:05 ` bugzilla-daemon
@ 2014-07-22 14:29 ` bugzilla-daemon
2014-07-22 14:36 ` bugzilla-daemon
` (7 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: bugzilla-daemon @ 2014-07-22 14:29 UTC (permalink / raw)
To: dri-devel
https://bugzilla.kernel.org/show_bug.cgi?id=80901
Alex Deucher <alexdeucher@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alexdeucher@gmail.com
--- Comment #3 from Alex Deucher <alexdeucher@gmail.com> ---
Does rendering with PRIME work? E.g., DRM_PRIME=1 glxinfo
I'm not sure if radeontop supports all cards or not.
--
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 15+ messages in thread* [Bug 80901] [radeon] loading corrupts lspci entry + unloading crashes kernel
2014-07-22 14:00 [Bug 80901] New: [radeon] loading corrupts lspci entry + unloading crashes kernel bugzilla-daemon
` (5 preceding siblings ...)
2014-07-22 14:29 ` bugzilla-daemon
@ 2014-07-22 14:36 ` bugzilla-daemon
2014-07-22 14:37 ` bugzilla-daemon
` (6 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: bugzilla-daemon @ 2014-07-22 14:36 UTC (permalink / raw)
To: dri-devel
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
^ permalink raw reply [flat|nested] 15+ messages in thread* [Bug 80901] [radeon] loading corrupts lspci entry + unloading crashes kernel
2014-07-22 14:00 [Bug 80901] New: [radeon] loading corrupts lspci entry + unloading crashes kernel bugzilla-daemon
` (6 preceding siblings ...)
2014-07-22 14:36 ` bugzilla-daemon
@ 2014-07-22 14:37 ` bugzilla-daemon
2014-07-22 16:13 ` bugzilla-daemon
` (5 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: bugzilla-daemon @ 2014-07-22 14:37 UTC (permalink / raw)
To: dri-devel
https://bugzilla.kernel.org/show_bug.cgi?id=80901
--- Comment #5 from Andrea Paternò <amerryfellow@gmail.com> ---
Created attachment 143931
--> https://bugzilla.kernel.org/attachment.cgi?id=143931&action=edit
dmesg
--
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
^ permalink raw reply [flat|nested] 15+ messages in thread* [Bug 80901] [radeon] loading corrupts lspci entry + unloading crashes kernel
2014-07-22 14:00 [Bug 80901] New: [radeon] loading corrupts lspci entry + unloading crashes kernel bugzilla-daemon
` (7 preceding siblings ...)
2014-07-22 14:37 ` bugzilla-daemon
@ 2014-07-22 16:13 ` bugzilla-daemon
2014-07-22 18:00 ` bugzilla-daemon
` (4 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: bugzilla-daemon @ 2014-07-22 16:13 UTC (permalink / raw)
To: dri-devel
https://bugzilla.kernel.org/show_bug.cgi?id=80901
--- Comment #6 from Alex Deucher <alexdeucher@gmail.com> ---
(In reply to Andrea Paternò from comment #4)
> 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
Everything appears to be working fine. The delay and messages are due to the
card being powered down by default to save power and then powered back up when
you use it.
--
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
^ permalink raw reply [flat|nested] 15+ messages in thread* [Bug 80901] [radeon] loading corrupts lspci entry + unloading crashes kernel
2014-07-22 14:00 [Bug 80901] New: [radeon] loading corrupts lspci entry + unloading crashes kernel bugzilla-daemon
` (8 preceding siblings ...)
2014-07-22 16:13 ` bugzilla-daemon
@ 2014-07-22 18:00 ` bugzilla-daemon
2014-07-22 18:30 ` bugzilla-daemon
` (3 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: bugzilla-daemon @ 2014-07-22 18:00 UTC (permalink / raw)
To: dri-devel
https://bugzilla.kernel.org/show_bug.cgi?id=80901
--- Comment #7 from Andrea Paternò <amerryfellow@gmail.com> ---
Created attachment 143941
--> https://bugzilla.kernel.org/attachment.cgi?id=143941&action=edit
System Journal log after module unloading
Makes sense! Nonetheless, the "unknown header type 7f" problem remains, as well
as the unloading problem. I managed to capture the journal log of the system
just before the crash, which is attached.
--
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
^ permalink raw reply [flat|nested] 15+ messages in thread* [Bug 80901] [radeon] loading corrupts lspci entry + unloading crashes kernel
2014-07-22 14:00 [Bug 80901] New: [radeon] loading corrupts lspci entry + unloading crashes kernel bugzilla-daemon
` (9 preceding siblings ...)
2014-07-22 18:00 ` bugzilla-daemon
@ 2014-07-22 18:30 ` bugzilla-daemon
2014-07-22 18:41 ` bugzilla-daemon
` (2 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: bugzilla-daemon @ 2014-07-22 18:30 UTC (permalink / raw)
To: dri-devel
https://bugzilla.kernel.org/show_bug.cgi?id=80901
--- Comment #8 from Alex Deucher <alexdeucher@gmail.com> ---
(In reply to Andrea Paternò from comment #7)
> Makes sense! Nonetheless, the "unknown header type 7f" problem remains, as
> well as the unloading problem. I managed to capture the journal log of the
> system just before the crash, which is attached.
The lspci -vvv problem is that lspci doesn't power up the GPU so it just reads
back garbage since the GPU is powered down. It should work if you run lspci
when the GPU is powered up (e.g., when rendering with DRM_PRIME=1 or if you
disable runtime power management (boot with radeon.runpm=0 on the kernel
command line in grub). The crash is a bug in vgaswitcheroo I think rather than
the radeon driver.
--
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
^ permalink raw reply [flat|nested] 15+ messages in thread* [Bug 80901] [radeon] loading corrupts lspci entry + unloading crashes kernel
2014-07-22 14:00 [Bug 80901] New: [radeon] loading corrupts lspci entry + unloading crashes kernel bugzilla-daemon
` (10 preceding siblings ...)
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
13 siblings, 0 replies; 15+ messages in thread
From: bugzilla-daemon @ 2014-07-22 18:41 UTC (permalink / raw)
To: dri-devel
https://bugzilla.kernel.org/show_bug.cgi?id=80901
--- Comment #9 from Andrea Paternò <amerryfellow@gmail.com> ---
That is.. well. I feel quite dumb, because it totally makes sense. It totally
works when the card is powered up: both lspci and radeontop work like a charm!
Now I only have to figure out what may cause the vgaswitcheroo problem
--
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
^ permalink raw reply [flat|nested] 15+ messages in thread* [Bug 80901] [radeon] loading corrupts lspci entry + unloading crashes kernel
2014-07-22 14:00 [Bug 80901] New: [radeon] loading corrupts lspci entry + unloading crashes kernel bugzilla-daemon
` (11 preceding siblings ...)
2014-07-22 18:41 ` bugzilla-daemon
@ 2014-07-22 20:57 ` bugzilla-daemon
2014-07-22 22:22 ` bugzilla-daemon
13 siblings, 0 replies; 15+ messages in thread
From: bugzilla-daemon @ 2014-07-22 20:57 UTC (permalink / raw)
To: dri-devel
https://bugzilla.kernel.org/show_bug.cgi?id=80901
Andrea Paternò <amerryfellow@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #10 from Andrea Paternò <amerryfellow@gmail.com> ---
It turns out that the vgaswitcheroo crash may be avoided by integrating the
radeon module directly into the kernel. Of course, this prevents the user from
unloading it, but, with the power management features on, I see no reason why
should I want to unload it.
I had to compile the radeon extra firmware in the kernel as well, but as of
now, I am not facing any issue, even after suspending/resuming.
--
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
^ permalink raw reply [flat|nested] 15+ messages in thread* [Bug 80901] [radeon] loading corrupts lspci entry + unloading crashes kernel
2014-07-22 14:00 [Bug 80901] New: [radeon] loading corrupts lspci entry + unloading crashes kernel bugzilla-daemon
` (12 preceding siblings ...)
2014-07-22 20:57 ` bugzilla-daemon
@ 2014-07-22 22:22 ` bugzilla-daemon
13 siblings, 0 replies; 15+ messages in thread
From: bugzilla-daemon @ 2014-07-22 22:22 UTC (permalink / raw)
To: dri-devel
https://bugzilla.kernel.org/show_bug.cgi?id=80901
--- Comment #11 from Alex Deucher <alexdeucher@gmail.com> ---
You can leave the radeon driver as a module and just not unload it. There's
generally no reason to.
--
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 15+ messages in thread