https://bugs.freedesktop.org/show_bug.cgi?id=91192
Bug ID: 91192
Summary: ring test failed/si startup failed on resume
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: benjo316_2003(a)yahoo.com
QA Contact: …
[View More]dri-devel(a)lists.freedesktop.org
Created attachment 116879
--> https://bugs.freedesktop.org/attachment.cgi?id=116879&action=edit
journalctl output and kernel bug
After resume from suspend, upon adjusting the volume (and once without
adjusting the volume), window controls become unresponsive for long periods
(>15s) and audio dies. After the each unresponsive period, some input events
(clicks, etc.) begin catching up and new events are allowed until the next
period. The only way to restore everything to normal (afaik) is to log out and
in again. One time I did this, and it triggered a kernel BUG (see attachment
'journal.txt'). journal2.txt is from when it happened without changing the
volume.
System Info:
ArchLinux (*-testing + lcarlier mesa-git enabled)
Linux version 4.0.7-2
Command-line: root=PARTUUID=7ea06983-7065-4692-aa21-82645fd721ee ro
radeon.dpm=1 drm.rnodes=1
Mesa version: 70936.aa7d4ce-1
Xorg ati driver ver: 3233.afab783-1
DE: Plasma-desktop 5.3.2-1
I will be away from my computer for a couple weeks, but if you have any
questions I'll try to answer as best I can.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=91084
Bug ID: 91084
Summary: RadeonSI crash while playing World Of Tanks
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: edzis(a)inbox.lv
Computer freezes completely …
[View More]however I can access it via the ssh.
Versions are in the files.
This is with Ubuntu 14.04 using liquorix kernel and this is the first time I
can actually ssh into the machine after crash.
Previously tried with Ubuntu 15.04 using kernel 4.1/3.13/3.19/4.0.x all of them
crash completely.
Versions/syslog/etc. are in the attachments.
Please ask if You need more info.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=108907
Bug ID: 108907
Summary: Display corruption on multi-monitor when the largest
panel is not on the left (and amdgpu.dc=1)
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
URL: https://imgur.com/a/DIqAfu1
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: DRM/AMDgpu
…
[View More] Assignee: dri-devel(a)lists.freedesktop.org
Reporter: kdebugs(a)funkster.org
After doing an update (Arch) on 2018-11-27 (including mesa (18.2.4-1 ->
18.2.5-1), linux (4.19.2.arch1-1 -> 4.19.4.arch1-1)) I found I had corruption
on the center monitor of a PLP setup. Further investigation found that the
corruption does not occur if the large panel is configured to be on the left
(both using XFCE display settings, and the equivalent in KDE). This was
replicated on both my installed OS and a Manjaro 18.0 live USB.
Corruption takes the form of every other line being offset by an increasing
amount, although it only starts part-way down the monitor. Side monitors are
not affected.
https://i.imgur.com/0pQMznF.jpg
Probably important details:
- Arch / XFCE / XDE / lightdm
- AMDGPU open source drivers (Sapphire Radeon RX580)
- 3 monitors in PLP: sidecars are 1680x1050 (but turned so they're vertical),
center is 2560x1600. Left-hand sidecar is on HDMI, other two are DP.
- Corruption DOESN'T happen if the large monitor is placed on the left! Nor
does it happen at the login screen (which doesn't have any screen rotation and
probably also has the big panel on the left)
- Corruption DOESN'T happen if I reduce the resolution of the center screen to
2048x1280 (but obviously that's not a solution)
- Corruption DOESN'T happen if I pass amdgpu.dc=0 to the kernel
- Corruption DOES happen on KDE (tested with Manjaro KDE live USB) as long as
you arrange the monitors in the same way
Here's a paste of the pacman.log from the day it all went wrong:
https://pastebin.com/H3i5LuzU
or
https://hastebin.com/dixemisepo.php
Thank you for your attention.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=108892
Bug ID: 108892
Summary: kernel BUG at kernel/time/timer.c:1137 in
drm_sched_job_finish [gpu_sched]
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: …
[View More]vicluo96(a)gmail.com
Created attachment 142656
--> https://bugs.freedesktop.org/attachment.cgi?id=142656&action=edit
kernel dmesg
Sometimes my AMD-2500U with amd.dc=1 crashes with the above messages in dmesg.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=108843
Bug ID: 108843
Summary: Laptop with ATI RX 580 doesn't turn the screen on when
resuming.
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: alex14641(a)…
[View More]yahoo.com
Created attachment 142582
--> https://bugs.freedesktop.org/attachment.cgi?id=142582&action=edit
dmesg
When I close the laptop lid, the screen turns off, and the following appears in
dmesg:
[ 5802.486819] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport
link status failed
[ 5802.486840] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock
recovery failed
[ 5803.077555] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport
link status failed
[ 5803.077576] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock
recovery failed
When I open the lid, the screen stays blank. I'm running Slackware Current with
a kernel built from drm-next-4.21-wip.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=108806
Bug ID: 108806
Summary: AMDGPU Failed to read EDID from display
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: michael.lindman(a)gmail.com
Created attachment 142526
--> https:/…
[View More]/bugs.freedesktop.org/attachment.cgi?id=142526&action=edit
boot log showing EDID failure
When connecting one of my monitors to the system it defaults to 1024x768 and
not the native resolution and grepping through the kernel logs shows that
AMDGPU fails to read the EDID of the display.
[ 5.054779] [drm:dc_link_detect [amdgpu]] *ERROR* No EDID read.
The display was working fine as of kernel 4.18.18 with the issues arising upon
4.19.2.
I am using a POLARIS 10 GPU and both displays are connected to DisplayPort with
the Asus PG2780 having the issues with failing to grab the EDID.
DisplayPort-0 LG 25UM65-P
DisplayPort-1 ASUS PG278Q
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=90340
Bug ID: 90340
Summary: RADEON "PITCAIRN" displayport output breaks when
monitor turned off and on
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: …
[View More]steve(a)einval.com
As initially reporte in Debian at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783705
I'm running Debian Jessie (3.16.x kernel) on a machine with a Pitcairn-based
video adapter and an NEC Multisync EA274WMi 27" monitor, connected via
DisplayPort.
I've also tried upgrading to the 4.0 kernel and I see exactly the same
symptoms.
If I turn the monitor off and then on again (as I was doing overnight), I get
no display at all.
I've wiggled the mouse, hit numlock on the keybard (the numlock
led illuminates fine), etc., but no display. I've seen this kind of
thing happen in the past on some machines, so I switch to VT1 and back
to see if that helps. Still no display at all, either on console or
under X. I log in remotely and I can see that the Xorg.0.log file has
been updated with mode lines for the monitor, suggesting things have
just woken up fine. But still no display.
Here's the really weird thing: at this point, the monitor has
basically locked up. It won't respond to the power/input/menu butttons
at all, and is still showing the blue LED that says "I have signal"
rather than switching to the amber "no signal" warning. Therefore, I
can only assume there's a problem here with some weird invalid DP
signal being produced.
I've carried on playing with this. If I log in from another machine and run
xrandr, I can see the display details of the monitor just fine. If I use xrandr
to turn the display off and then on again:
xrandr --output DisplayPort-0 --off
xrandr --output DisplayPort-0 2560x1440
then things start working again.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=90320
Bug ID: 90320
Summary: Lenovo ThinkPad E455 (Kaveri A10-7300): Blank built-in
screen with radeon kms driver
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: blocker
Priority: highest
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
…
[View More]Reporter: sibradzic(a)gmail.com
Created attachment 115550
--> https://bugs.freedesktop.org/attachment.cgi?id=115550&action=edit
dmesg 4.1 rc1
As soon as the radeon kms switches in from efifb, the screen goes blank for the
moment (no backlight), and then the backlight switches in, but the screen
remains black. External HDMI output works just fine. No X is involved, I can't
even see the kms console @ eDP. I can even control the backlight on the eDP
display, but all i get is the various shades of black. Fglrx works fine,
although it flickers wildly before the picture gets stable.
I've tried numerous things, like forcing EDID that was grabbed from fglrx,
disabling audio, applying all the DP training / backlight disabling patches as
in https://bugs.freedesktop.org/show_bug.cgi?id=73530, all to no avail.
Currently on linux 4.1rc1, tried 3.13, 3.16 & 3.19 as well, same issue.
Please help! I bought this laptop cause I prefer AMD, and was expecting Lenovo
to work great with Linux, but so far its broken. Ready to try some patches...
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]