https://bugzilla.kernel.org/show_bug.cgi?id=117171
Bug ID: 117171
Summary: Radeon GPU lockup in X windows after resuming from
blank screen
Product: Drivers
Version: 2.5
Kernel Version: 4.6 rc5 from
http://kern
https://bugzilla.kernel.org/show_bug.cgi?id=117171
--- Comment #1 from erik.brangs at gmx.de ---
Created attachment 214001
--> https://bugzilla.kernel.org/attachment.cgi?id=214001&action=edit
Xorg log
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=117171
--- Comment #2 from erik.brangs at gmx.de ---
Created attachment 214011
--> https://bugzilla.kernel.org/attachment.cgi?id=214011&action=edit
glxinfo from working system
--
You are receiving this mail because:
You are watching the assignee of t
https://bugzilla.kernel.org/show_bug.cgi?id=117131
Alex Deucher changed:
What|Removed |Added
CC||alexdeucher at gmail.com
--- Comment #6 f
https://bugzilla.kernel.org/show_bug.cgi?id=117111
Alex Deucher changed:
What|Removed |Added
CC||alexdeucher at gmail.com
--- Comment #1 f
https://bugzilla.kernel.org/show_bug.cgi?id=117111
MichaÅ Pecio changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugzilla.kernel.org/show_bug.cgi?id=117181
Bug ID: 117181
Summary: graphic glitches for Kernel > 4.2 Intel HD 5xx and
skylake
Product: Drivers
Version: 2.5
Kernel Version: 4.5.2
Hardware: Intel
O
https://bugzilla.kernel.org/show_bug.cgi?id=117131
--- Comment #7 from Jason Vas Dias ---
(In reply to Alex Deucher from comment #6)
> Your system is muxless so there is no mux to switch. The displays are only
> connected to the IGP. You need to use the xserver PRIME stuff to render
> with the
https://bugzilla.kernel.org/show_bug.cgi?id=117131
--- Comment #8 from Jason Vas Dias ---
As stated on the web-page quoted above ,
( https://wiki.archlinux.org/index.php/PRIME )
an example xorg.conf to use the discrete card
as primary GPU is:
# Discrete Card as Primary GPU
Section "ServerLayo
https://bugzilla.kernel.org/show_bug.cgi?id=117131
--- Comment #9 from Alex Deucher ---
(In reply to Jason Vas Dias from comment #8)
> As stated on the web-page quoted above ,
> ( https://wiki.archlinux.org/index.php/PRIME )
> an example xorg.conf to use the discrete card
> as primary GPU is:
>
https://bugzilla.kernel.org/show_bug.cgi?id=117131
--- Comment #10 from Jason Vas Dias ---
OK, fine, I have to use FGLRX to use the Radeon as the primary display
as I do under OEL7 (Linux 3.10) -
what a terrific new open source radeon driver Linux 4.5 has.
But I cannot even get the Intel card
https://bugzilla.kernel.org/show_bug.cgi?id=117131
--- Comment #11 from Alex Deucher ---
(In reply to Jason Vas Dias from comment #10)
> OK, fine, I have to use FGLRX to use the Radeon as the primary display
> as I do under OEL7 (Linux 3.10) -
> what a terrific new open source radeon driver Lin
https://bugzilla.kernel.org/show_bug.cgi?id=117131
--- Comment #12 from Jason Vas Dias ---
Created attachment 214151
--> https://bugzilla.kernel.org/attachment.cgi?id=214151&action=edit
dmesg boot log
Boot DMESG log as requested
--
You are receiving this mail because:
You are watching the as
https://bugzilla.kernel.org/show_bug.cgi?id=117131
--- Comment #13 from Jason Vas Dias ---
Yes, radeon.runpm=0 has stopped the ACPI problem - but the latest Xorg
xf86-video-intel driver ( 2.99.917 ) apparently does not work with the
latest xorg server (1.18.3) and gets a segmentation violation o
https://bugzilla.kernel.org/show_bug.cgi?id=117181
--- Comment #1 from yves.dufournaud at gmail.com ---
there is another issue: resuming from suspend to ram is failing, I would have
filled a separate bug, but apparently it can be linked to graphics.
following the instruction here:
https://01.org/
https://bugzilla.kernel.org/show_bug.cgi?id=117131
--- Comment #14 from Alex Deucher ---
It sounds like it's a bug in the intel driver. The radeon driver appears to be
loading fine. Can you get any display on the intel card at all? You can
blacklist the radeon driver (append modeprobe.blanklis
https://bugzilla.kernel.org/show_bug.cgi?id=117131
--- Comment #15 from 3pb33h+1ymmkx54pslys at sharklasers.com ---
Seems like alex made an typo i think it should be modprobe.blacklist=radeon
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=117131
--- Comment #16 from Alex Deucher ---
(In reply to 3pb33h+1ymmkx54pslys from comment #15)
> Seems like alex made an typo i think it should be modprobe.blacklist=radeon
Yes you are correct, sorry about that.
--
You are receiving this mail becau
https://bugzilla.kernel.org/show_bug.cgi?id=117181
--- Comment #2 from yves.dufournaud at gmail.com ---
tested with CONFIG_PM_DEBUG with core/processors/device
dmesg > dmesg_before; echo mem > /sys/power/state; dmesg > dmesg_after
machine resume after few second, but mouse pointer is lost (not v
https://bugzilla.kernel.org/show_bug.cgi?id=117181
--- Comment #3 from yves.dufournaud at gmail.com ---
Created attachment 214301
--> https://bugzilla.kernel.org/attachment.cgi?id=214301&action=edit
dmesg_after.txt
output of dmesg > dmesg_before; echo mem > /sys/power/state; dmesg >
dmesg_after
https://bugzilla.kernel.org/show_bug.cgi?id=117131
--- Comment #17 from Jason Vas Dias ---
OK, I tried appending modprobe.blacklist=radeon to the kernel command line -
that had no effect - the radeon module is built-in ; only using
radeon.runpm=0 stops the ACPI error messages .
RE: > I'd sugges
https://bugzilla.kernel.org/show_bug.cgi?id=51381
Peter Uchno changed:
What|Removed |Added
CC||peter.uchno at gmail.com
--- Comment #41 fr
https://bugzilla.kernel.org/show_bug.cgi?id=116251
Kertesz Laszlo changed:
What|Removed |Added
CC||laszlo.kertesz at gmail.com
--- Comment
https://bugzilla.kernel.org/show_bug.cgi?id=116251
--- Comment #7 from Alex Deucher ---
The patch has been reverted:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bfaddd9fc8ac048b99475f000dbef6f08297417f
and will be reverted in stable branches as well.
--
You are rec
https://bugzilla.kernel.org/show_bug.cgi?id=117131
--- Comment #18 from Jason Vas Dias ---
I think FGLRX is evidently able to run my laptop's display in
dual-driver mode whereby the Intel IGP card runs the LCD in some sort of
"slave" mode under the control of the fglrx Radeon 8970M controller mo
https://bugzilla.kernel.org/show_bug.cgi?id=117131
--- Comment #19 from Jason Vas Dias ---
Oops, the link should have been:
https://bugs.freedesktop.org/show_bug.cgi?id=95140
but as it turns out, that other bug could be equally relevant.
--
You are receiving this mail because:
You are watching
https://bugzilla.kernel.org/show_bug.cgi?id=117131
--- Comment #20 from Jason Vas Dias ---
When I look at linux 4.5.0 boot dmesg log messages like :
[3.115380] vga_switcheroo: enabled
[3.115463] ATPX version 1, functions 0x0033
[3.115541] [drm] DMAR active, disabling use of stole
https://bugzilla.kernel.org/show_bug.cgi?id=117131
--- Comment #21 from Jason Vas Dias ---
Aha! It was :
Section "Device"
Identifier "Intel"
Driver "intel"
Option "Monitor-eDP-1" "eDP-1"
Option "Monitor-DisplayPort-0" "eDP-1"
EndSection
and also :
Section "ServerLayout"
Ident
https://bugzilla.kernel.org/show_bug.cgi?id=117131
--- Comment #22 from Jason Vas Dias ---
It looks like the Intel driver is actually internally using the Radeon driver?
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=117131
--- Comment #23 from Jason Vas Dias ---
Xorg server log of successful session
[ 173.214]
X.Org X Server 1.18.3
Release Date: 2016-04-04
[ 173.214] X Protocol Version 11, Revision 0
[ 173.214] Build Operating System: Linux 4.5.0 x86_64
[
https://bugzilla.kernel.org/show_bug.cgi?id=117131
--- Comment #24 from Alex Deucher ---
(In reply to Jason Vas Dias from comment #20)
> When I look at linux 4.5.0 boot dmesg log messages like :
>
> [3.115380] vga_switcheroo: enabled
> [3.115463] ATPX version 1, functions 0x0033
> [
https://bugzilla.kernel.org/show_bug.cgi?id=117131
--- Comment #25 from Alex Deucher ---
Please attach you logs rather than pasting them in the comments, it's much
harder to follow with them inline.
Also, as per comment 11, please try removing your xorg config file completely.
The drivers are a
https://bugzilla.kernel.org/show_bug.cgi?id=117131
--- Comment #26 from Alex Deucher ---
(In reply to Jason Vas Dias from comment #22)
> It looks like the Intel driver is actually internally using the Radeon
> driver?
No. The drivers are independent. vga_switcheroo provides the intermediary for
https://bugzilla.kernel.org/show_bug.cgi?id=86351
haakobja at gmail.com changed:
What|Removed |Added
CC||haakobja at gmail.com
--- Comment
https://bugzilla.kernel.org/show_bug.cgi?id=117181
yves.dufournaud at gmail.com changed:
What|Removed |Added
Regression|No |Yes
--
You are receiving
https://bugzilla.kernel.org/show_bug.cgi?id=117151
--- Comment #1 from Parker Reed ---
Created attachment 214661
--> https://bugzilla.kernel.org/attachment.cgi?id=214661&action=edit
Full verbose lspci
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=117171
--- Comment #3 from Erik Brangs ---
The problem might be related to DPMS: I haven't seen any freezes after
deactivating DPMS in xscreensaver.
When I use DPMS with "Standby" in xscreensaver and set the times for "Suspend"
and "Off" to a high valu
https://bugzilla.kernel.org/show_bug.cgi?id=117411
Bug ID: 117411
Summary: [radeon][HD5650][REDWOOD] radeon.dpm causing one
minute boot delay
Product: Drivers
Version: 2.5
Kernel Version: 4.5.0
Hardware: All
https://bugzilla.kernel.org/show_bug.cgi?id=117411
--- Comment #1 from no.spam.to.me at ish.de ---
Created attachment 214761
--> https://bugzilla.kernel.org/attachment.cgi?id=214761&action=edit
dmesg for 4.4.0
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=117411
--- Comment #2 from no.spam.to.me at ish.de ---
Look here:
[ 24.114256] Bluetooth: BNEP socket layer initialized
[ 35.249644] Console: switching to colour frame buffer device 170x48
That seems to be the "black period"
--
You are receiving t
https://bugzilla.kernel.org/show_bug.cgi?id=141741
--- Comment #13 from Michael Schenaerts ---
I did the bisect with no luck. Evrything was running fine
I built the 4.6 and even the 4.7 with the config files from the 4.5 I set the
other options to default and... it works.
I'll try to build them
https://bugzilla.kernel.org/show_bug.cgi?id=96721
--- Comment #2 from Michel Dänzer ---
It's not clear that those are both one and the same bug.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=151341
Bug ID: 151341
Summary: AMDGPU Hawaii: screen freeze, Xorg blocked in
fence_default_wait
Product: Drivers
Version: 2.5
Kernel Version: 4.7.0
Hardware: x86-64
https://bugzilla.kernel.org/show_bug.cgi?id=151341
Alex Deucher changed:
What|Removed |Added
CC||alexdeucher at gmail.com
--- Comment #1 f
https://bugzilla.kernel.org/show_bug.cgi?id=36522
bastienphilbert at gmail.com changed:
What|Removed |Added
CC||bastienphilbert at gmail.com
https://bugzilla.kernel.org/show_bug.cgi?id=36522
--- Comment #15 from bastienphilbert at gmail.com ---
Created attachment 227551
--> https://bugzilla.kernel.org/attachment.cgi?id=227551&action=edit
Cmap Fix
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=36522
--- Comment #16 from Christian Casteyde ---
No, I still have this:
[ 1215.037018] WARNING: kmemcheck: Caught 16-bit read from uninitialized memory
(8801c307d020)
[ 1215.037029] 2e032b012206070e0307373e033534262327353721171507111e031514062322
[
https://bugzilla.kernel.org/show_bug.cgi?id=151541
Bug ID: 151541
Summary: AMD hybrid graphics: [drm:evergreen_resume [radeon]]
*ERROR* evergreen startup failed on resume
Product: Drivers
Version: 2.5
Kernel Version: 4.7.0
https://bugzilla.kernel.org/show_bug.cgi?id=151541
Dainius Masiliūnas changed:
What|Removed |Added
Attachment #227711|text/x-log |text/plain
mime type|
https://bugzilla.kernel.org/show_bug.cgi?id=151541
--- Comment #1 from Dainius Masiliūnas ---
Using radeon.dpm=0 doesn't change anything, only the "*ERROR* radeon: dpm
resume failed" line is not there in that case.
--
You are receiving this mail because:
You are watching the assignee of the bu
https://bugzilla.kernel.org/show_bug.cgi?id=118611
K. Paden changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugzilla.kernel.org/show_bug.cgi?id=151541
Alex Deucher changed:
What|Removed |Added
CC||alexdeucher at gmail.com
--- Comment #2 f
https://bugzilla.kernel.org/show_bug.cgi?id=151541
--- Comment #3 from Alex Deucher ---
On the kernel command line in grub.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=151541
--- Comment #4 from Dainius Masiliūnas ---
Yes, it does. With that setting, there are no errors either, and lspci runs
quickly.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=151541
--- Comment #5 from Alex Deucher ---
Does it work any better with kernel 4.8?
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=84431
--- Comment #10 from JoaquÃn AramendÃa ---
> JoaquÃn, how does 97d30fa35 break nouveau vga-switcheroo? If you load
> nouveau with runpm=0, then you can write OFF to debugfs' vga_switcheroo.
> However runpm=1 (or -1 for Optimus systems) is reco
https://bugzilla.kernel.org/show_bug.cgi?id=151541
--- Comment #6 from Dainius Masiliūnas ---
Created attachment 227741
--> https://bugzilla.kernel.org/attachment.cgi?id=227741&action=edit
4.7.0-next-20160803 dmesg
No. I tried the linux-next tree and it gave me the same errors even during boo
https://bugzilla.kernel.org/show_bug.cgi?id=36522
--- Comment #17 from bastienphilbert at gmail.com ---
Can you find out what drm driver you are currently using as all of them link to
the core function that is leaking memory and knowing which drive is doing it
would be very helpful.
--
You are r
https://bugzilla.kernel.org/show_bug.cgi?id=36522
--- Comment #18 from Christian Casteyde ---
See comment #3, #4 and #5.
I think i'm using radeon driver with kms since the only graphic chip I have on
my laptop is a Radeon 6650M (no intel graphic in CPU, has been deactivated by
vendor).
--
You
https://bugzilla.kernel.org/show_bug.cgi?id=151341
--- Comment #2 from yshuiv7 at gmail.com ---
Created attachment 227861
--> https://bugzilla.kernel.org/attachment.cgi?id=227861&action=edit
dmesg
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=151341
--- Comment #3 from yshuiv7 at gmail.com ---
Created attachment 227871
--> https://bugzilla.kernel.org/attachment.cgi?id=227871&action=edit
Xorg.log
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=151341
--- Comment #4 from yshuiv7 at gmail.com ---
Previous dmesg is from 4.7.0, the attached one is from git HEAD.
Using the _k_ firmware seems to make this happen much less frequently.
--
You are receiving this mail because:
You are watching the as
https://bugzilla.kernel.org/show_bug.cgi?id=151341
--- Comment #5 from yshuiv7 at gmail.com ---
I tried to reset the gpu by using /sys/kernel/debug/dri/0/amdgpu_gpu_reset, and
the result is a NULL pointer dereference in the kernel.
dmesg attached
--
You are receiving this mail because:
You are
https://bugzilla.kernel.org/show_bug.cgi?id=151341
--- Comment #6 from yshuiv7 at gmail.com ---
Created attachment 227901
--> https://bugzilla.kernel.org/attachment.cgi?id=227901&action=edit
Kernel Oops when resetting the GPU
--
You are receiving this mail because:
You are watching the assigne
https://bugzilla.kernel.org/show_bug.cgi?id=118701
Stuart Foster changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|CODE_FIX
https://bugzilla.kernel.org/show_bug.cgi?id=100871
--- Comment #10 from Charles R. Anderson ---
Problem still exists in Linux 4.6.4 in Fedora 24
(kernel-4.6.4-301.fc24.x86_64).
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=150731
--- Comment #3 from Jimi ---
I've now confirmed this issue on Fiji (R9 Fury) as well.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=119211
--- Comment #4 from Jimi ---
Is this bug still happening? With my R9 Fury on amdgpu, cat
/sys/class/hwmon/hwmon0/pwm1 (well, in my case, it's hwmon2 because I have
another card), returns 35 on idle, not 0, but the fans are not running. Even
when
https://bugzilla.kernel.org/show_bug.cgi?id=119211
--- Comment #5 from Jimi ---
I managed to check the fans while pwm1 was giving values like 68, 61, and 56,
and they were not turned on. I don't know if that means anything, because the
card was still <40 degrees and definitely not too hot to touc
https://bugzilla.kernel.org/show_bug.cgi?id=151831
Bug ID: 151831
Summary: Video freezes mouse moveable, video graphical errors
like black strips an screen goes black sometimes,
system almost unresponsive.
Product: Drivers
https://bugzilla.kernel.org/show_bug.cgi?id=151831
--- Comment #1 from Andre ---
Created attachment 228061
--> https://bugzilla.kernel.org/attachment.cgi?id=228061&action=edit
glxinfo
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=151831
Alex Deucher changed:
What|Removed |Added
CC||alexdeucher at gmail.com
--- Comment #2 f
https://bugzilla.kernel.org/show_bug.cgi?id=119211
--- Comment #6 from Stas Sergeev ---
> Is this bug still happening?
For me it is happening as a hell.
And because fancontrol service also doesn't
work on my PC (I've filled another reports
about it), the problems are very real.
> I managed to c
https://bugzilla.kernel.org/show_bug.cgi?id=119211
--- Comment #7 from Jimi ---
I do not have fancontrol set up or running (it's inactive on my system). I
don't know anything about fancontrol at all. I'm running Arch Linux, so I
pretty much only am running services that I know about.
I tried wri
https://bugzilla.kernel.org/show_bug.cgi?id=119211
Alex Deucher changed:
What|Removed |Added
CC||alexdeucher at gmail.com
--- Comment #8 f
https://bugzilla.kernel.org/show_bug.cgi?id=119211
--- Comment #9 from Stas Sergeev ---
(In reply to Alex Deucher from comment #8)
> By default the hw controls the fan based on temperature, etc.
For me not.
> Not all cards have a fan control. If you do, then the following standard
> HWMON
> pwm
https://bugzilla.kernel.org/show_bug.cgi?id=119211
--- Comment #10 from Alex Deucher ---
Please attach your dmesg output and xorg log (if running X).
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=119211
--- Comment #11 from Stas Sergeev ---
Created attachment 228111
--> https://bugzilla.kernel.org/attachment.cgi?id=228111&action=edit
dmesg
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=119211
--- Comment #12 from Stas Sergeev ---
Created attachment 228121
--> https://bugzilla.kernel.org/attachment.cgi?id=228121&action=edit
Xorg log
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=151831
--- Comment #3 from Andre ---
I'm using mesa 12.0.1
The only thing that works is downgrading kernel to 4.5
had the Problem with kernel 4.6.2 too
I'm on Sabayon
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=151831
--- Comment #4 from Alex Deucher ---
(In reply to Andre from comment #3)
> I'm using mesa 12.0.1
> The only thing that works is downgrading kernel to 4.5
Can you bisect?
--
You are receiving this mail because:
You are watching the assignee of
https://bugzilla.kernel.org/show_bug.cgi?id=151831
--- Comment #5 from Andre ---
eh, do what? ..may if you give complete howto for my sabayon/gentoo system?
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=119211
--- Comment #13 from Jimi ---
That's interesting. My pwm1_enable returns 1, and trying to change it to 0 or 2
does nothing, but my pwm1 value does indeed change on its own, and I've never
seen it be 0. It sounds like I don't have this bug but do
https://bugzilla.kernel.org/show_bug.cgi?id=119211
--- Comment #14 from Jimi ---
I should mention, my pwm1_min is 0 and pwm1_max is 255.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=119211
--- Comment #15 from Stas Sergeev ---
> I should mention, my pwm1_min is 0 and pwm1_max is 255.
Same here.
IMHO pwm1_min should contain the value that
keeps the fan rotating at a minimal safe speed.
Putting 0 there makes it entirely useless.
--
https://bugzilla.kernel.org/show_bug.cgi?id=119211
--- Comment #16 from Jimi ---
Not necessarily. Less fans means less power usage means money saved, and as we
can see with my computer, you can keep the card cool without its own fans. I
have 4 case fans that are plugged directly into power and so
https://bugzilla.kernel.org/show_bug.cgi?id=151831
--- Comment #6 from Alex Deucher ---
Bisecting is a process for determining which specific commit in a project
caused a regression. Google for "linux kernel git bisect howto".
--
You are receiving this mail because:
You are watching the assign
https://bugzilla.kernel.org/show_bug.cgi?id=119211
--- Comment #17 from Stas Sergeev ---
> Not necessarily. Less fans means less power usage means money saved
You can set up fancontrol or put 0 into pwm1 manually
to stop the fan. But putting 0 into pwm1_min is IMHO
quite useless, it can as well
https://bugzilla.kernel.org/show_bug.cgi?id=150731
--- Comment #4 from Jimi ---
Created attachment 228411
--> https://bugzilla.kernel.org/attachment.cgi?id=228411&action=edit
X crash log
Here are my Xorg logs for when I unbind from vfio-pci, remove, and rescan, and
X crashes and comes back wit
https://bugzilla.kernel.org/show_bug.cgi?id=150731
--- Comment #5 from Jimi ---
Created attachment 228421
--> https://bugzilla.kernel.org/attachment.cgi?id=228421&action=edit
X post-crash log
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=150731
--- Comment #6 from Jimi ---
Created attachment 228431
--> https://bugzilla.kernel.org/attachment.cgi?id=228431&action=edit
dmesg log
And now I've tried unbinding it from amdgpu without X running at all, and it of
course didn't work, confirmin
https://bugzilla.kernel.org/show_bug.cgi?id=150731
--- Comment #7 from Jimi ---
I should mention at this point, I think there are 2 different bugs going on.
One bug is making it impossible to unbind any cards from the driver, and
another bug is making X immediately bind itself to an amdgpu card t
https://bugzilla.kernel.org/show_bug.cgi?id=150731
--- Comment #8 from Jimi ---
Created attachment 228441
--> https://bugzilla.kernel.org/attachment.cgi?id=228441&action=edit
dmesg log (amdgpu-pro)
And here's the dmesg log from testing this with amdgpu-pro (without X running),
with the crash s
https://bugzilla.kernel.org/show_bug.cgi?id=117151
Parker Reed changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugzilla.kernel.org/show_bug.cgi?id=85241
--- Comment #5 from Sergei Sinyak ---
(In reply to mirh from comment #4)
> Created attachment 215621 [details]
> TV was attached before booting.
>
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/
> ?id=7403c515c49c033fec33
https://bugzilla.kernel.org/show_bug.cgi?id=153121
Bug ID: 153121
Summary: UVD not responding, trying to reset the VCPU, ATI
Mobility Radeon HD 5650
Product: Drivers
Version: 2.5
Kernel Version: 4.8.0-040800rc2
Hardware
https://bugzilla.kernel.org/show_bug.cgi?id=153121
--- Comment #1 from Kontantin Ivanov ---
Created attachment 228721
--> https://bugzilla.kernel.org/attachment.cgi?id=228721&action=edit
DRI_PRIME=1 glxinfo
glxinfo for Radeon HD card
--
You are receiving this mail because:
You are watching t
https://bugzilla.kernel.org/show_bug.cgi?id=153121
--- Comment #2 from Kontantin Ivanov ---
Created attachment 228731
--> https://bugzilla.kernel.org/attachment.cgi?id=228731&action=edit
glxinfo
glxinfo for integrated Intel graphic card
--
You are receiving this mail because:
You are watchin
https://bugzilla.kernel.org/show_bug.cgi?id=153121
--- Comment #3 from Kontantin Ivanov ---
Created attachment 228741
--> https://bugzilla.kernel.org/attachment.cgi?id=228741&action=edit
md5sum /lib/fimware/radeon/*
--
You are receiving this mail because:
You are watching the assignee of the
https://bugzilla.kernel.org/show_bug.cgi?id=153121
--- Comment #4 from Kontantin Ivanov ---
Created attachment 228751
--> https://bugzilla.kernel.org/attachment.cgi?id=228751&action=edit
sudo lspci -v
--
You are receiving this mail because:
You are watching the assignee of the bug.
1 - 100 of 5870 matches
Mail list logo
