https://bugs.freedesktop.org/show_bug.cgi?id=99881
Martin Peres changed:
What|Removed |Added
Resolution|--- |MOVED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=99881
--- Comment #33 from Matthew Fox ---
Hi,
With runpm enabled & radeon.audio=0, the computer locks up requiring a hard
shutdown.
With runpm enabled & radeon.audio=0 & xorg.conf workaround, ditto. Except
sometimes instead the computer will lock up
https://bugs.freedesktop.org/show_bug.cgi?id=99881
--- Comment #32 from Alex Deucher ---
Does your kernel have this patch?
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/drivers/gpu/drm/radeon/radeon_device.c?id=066f1f0b4719eb4573ef09bfc63c2bbb6f7676ca
--
You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=99881
--- Comment #31 from Michel Dänzer ---
(In reply to Matthew Fox from comment #30)
> Just to confirm, the freezes and hard lockups still occur and the
> corresponding messages in dmesg which I also attached.
Weird; the xrandr output and Xorg log
https://bugs.freedesktop.org/show_bug.cgi?id=99881
--- Comment #30 from Matthew Fox ---
Just to confirm, the freezes and hard lockups still occur and the corresponding
messages in dmesg which I also attached.
This may be more sound related but I previously found in the kernel source
(file http:/
https://bugs.freedesktop.org/show_bug.cgi?id=99881
--- Comment #29 from Matthew Fox ---
Created attachment 129857
--> https://bugs.freedesktop.org/attachment.cgi?id=129857&action=edit
dmesg
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=99881
--- Comment #28 from Matthew Fox ---
Created attachment 129856
--> https://bugs.freedesktop.org/attachment.cgi?id=129856&action=edit
Xorg.1.log
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=99881
--- Comment #27 from Matthew Fox ---
Created attachment 129855
--> https://bugs.freedesktop.org/attachment.cgi?id=129855&action=edit
Xorg.0.log
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=99881
--- Comment #26 from Matthew Fox ---
Created attachment 129854
--> https://bugs.freedesktop.org/attachment.cgi?id=129854&action=edit
xrandr.log 2
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=99881
--- Comment #25 from Matthew Fox ---
Hi,
/etc/X11/xorg.conf didn't exist so I created it with the contents you
specified.
So I'm now running with runpm enabled and the xorg.conf in place.
--
You are receiving this mail because:
You are the as
https://bugs.freedesktop.org/show_bug.cgi?id=99881
--- Comment #24 from Michel Dänzer ---
(In reply to Matthew Fox from comment #23)
> That workaround doesn't seem to have any effect [...]
At the very least, it should have visible effects in the Xorg log file and
xrandr output. Please attach tho
https://bugs.freedesktop.org/show_bug.cgi?id=99881
--- Comment #23 from Matthew Fox ---
That workaround doesn't seem to have any effect so I'll run with radeon.runpm=0
Thanks for your help any way.
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=99881
--- Comment #22 from Michel Dänzer ---
I suspect what happens is that some client occasionally asks the X server to
probe the connected displays, similar to xrandr. This powers up the dGPU, in
order to probe its display connectors. That takes so
https://bugs.freedesktop.org/show_bug.cgi?id=99881
--- Comment #21 from Matthew Fox ---
Created attachment 129814
--> https://bugs.freedesktop.org/attachment.cgi?id=129814&action=edit
dmesg after xrandr
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=99881
--- Comment #20 from Matthew Fox ---
Created attachment 129813
--> https://bugs.freedesktop.org/attachment.cgi?id=129813&action=edit
dmesg before xrandr
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=99881
--- Comment #19 from Matthew Fox ---
Created attachment 129812
--> https://bugs.freedesktop.org/attachment.cgi?id=129812&action=edit
vgaswitcheroo switch after xrandr
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=99881
--- Comment #18 from Matthew Fox ---
Created attachment 129811
--> https://bugs.freedesktop.org/attachment.cgi?id=129811&action=edit
vgaswitcheroo switch before xrandr
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=99881
--- Comment #17 from Matthew Fox ---
Created attachment 129810
--> https://bugs.freedesktop.org/attachment.cgi?id=129810&action=edit
Xorg log after xrandr
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=99881
--- Comment #16 from Matthew Fox ---
Created attachment 129809
--> https://bugs.freedesktop.org/attachment.cgi?id=129809&action=edit
Xorg log before xrandr
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=99881
--- Comment #15 from Matthew Fox ---
Created attachment 129808
--> https://bugs.freedesktop.org/attachment.cgi?id=129808&action=edit
xrandr.log
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=99881
--- Comment #14 from Matthew Fox ---
Hi,
It's rare that the PC doesn't lock up with runpm enabled so I've only been able
to test this a couple of times.
In the first try, the PC had stabilized (stopped freezing) after a while. I
then ran xrandr
https://bugs.freedesktop.org/show_bug.cgi?id=99881
--- Comment #13 from Michel Dänzer ---
Please attach the output of xrandr.
With runpm enabled, if you run xrandr, does the dedicated GPU turn on and the
corresponding messages appear in dmesg?
--
You are receiving this mail because:
You are th
https://bugs.freedesktop.org/show_bug.cgi?id=99881
Matthew Fox changed:
What|Removed |Added
Attachment #129782|text/x-log |text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=99881
--- Comment #12 from Matthew Fox ---
Created attachment 129785
--> https://bugs.freedesktop.org/attachment.cgi?id=129785&action=edit
Xorg.0.log
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=99881
--- Comment #11 from Matthew Fox ---
Created attachment 129784
--> https://bugs.freedesktop.org/attachment.cgi?id=129784&action=edit
Xorg.1.log
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=99881
--- Comment #10 from Matthew Fox ---
Created attachment 129783
--> https://bugs.freedesktop.org/attachment.cgi?id=129783&action=edit
dmesg.log 2
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=99881
--- Comment #9 from Matthew Fox ---
(In reply to Michel Dänzer from comment #8)
> Please attach the corresponding Xorg log file.
Hi,
The only Xorg logs I have are for my new session. They weren't in /var/log/ but
/home/matthew/.local/share/xor
https://bugs.freedesktop.org/show_bug.cgi?id=99881
--- Comment #8 from Michel Dänzer ---
Please attach the corresponding Xorg log file.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists
https://bugs.freedesktop.org/show_bug.cgi?id=99881
--- Comment #7 from Matthew Fox ---
(In reply to Michel Dänzer from comment #6)
> Note that you should run
>
> env | grep DRI_
>
> in an X terminal, not in a console TTY.
Same result in both :/
--
You are receiving this mail because:
You ar
https://bugs.freedesktop.org/show_bug.cgi?id=99881
--- Comment #6 from Michel Dänzer ---
Note that you should run
env | grep DRI_
in an X terminal, not in a console TTY.
--
You are receiving this mail because:
You are the assignee for the bug.___
d
https://bugs.freedesktop.org/show_bug.cgi?id=99881
--- Comment #5 from Matthew Fox ---
> What does
>
> env | grep DRI_
>
> say?
That printed nothing.
My session with runtime pm enabled (no radeon.runpm=0 in cmdline) had been
running for a couple of hours without problem (apart from a bit of
https://bugs.freedesktop.org/show_bug.cgi?id=99881
--- Comment #4 from Michel Dänzer ---
(In reply to Matthew Fox from comment #3)
> This is a fresh install and I have not set that env var anywhere. Where
> could I check for that?
What does
env | grep DRI_
say?
> Does that mean with radeon.
https://bugs.freedesktop.org/show_bug.cgi?id=99881
--- Comment #3 from Matthew Fox ---
Hi Michel,
Just a slight correction to my description - I am running Ubuntu Gnome 16.04.2.
This is a fresh install and I have not set that env var anywhere. Where could I
check for that?
Does that mean with
https://bugs.freedesktop.org/show_bug.cgi?id=99881
--- Comment #2 from Michel Dänzer ---
It sounds like you have the environment variable DRI_PRIME=1 set for all
applications?
Those dmesg messages are normal when the dedicated GPU is powered up, which
takes some time. With runpm enabled, it's po
https://bugs.freedesktop.org/show_bug.cgi?id=99881
Michel Dänzer changed:
What|Removed |Added
Attachment #129781|text/x-log |text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=99881
--- Comment #1 from Matthew Fox ---
Created attachment 129782
--> https://bugs.freedesktop.org/attachment.cgi?id=129782&action=edit
lspci.log
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=99881
Bug ID: 99881
Summary: Lockup/Freezes on Laptop with switchable graphics
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
37 matches
Mail list logo
