https://bugs.freedesktop.org/show_bug.cgi?id=107465
Bug ID: 107465
Summary: Weird resolution
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: germano.massullo(a)gmail.com
Videocard: RX480
OS: Fedora 28 KDE
Kernel 4.17.9-200.fc28.x86_64
…
[View More]Sometimes when I poweroff the screen, then after some time I turn on it again,
the system cannot recognize native screen resolution, and sets it to a weird
one. In Plasma system settings, the monitor name is unknown and the native
resolution is missing (1600x1050), other resolutions are available instead..
After playing with some resolutions, suddendly the screen name (ViewSonic etc.)
returns back.
MrCooper user in #radeon Freenode chat, suggested me to start the system with
amdgpu.dc=0 flag. 24 hours of testing seems to confirm that such flag fixes the
problem.
I attach dmesg and xorg.0.log of system experiencing the problem
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=107456
Bug ID: 107456
Summary: WARNING: CPU: 11 PID: 1137 at
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu
_dm_mst_types.c:88 dm_dp_aux_transfer+0xa5/0xc0
[amdgpu]
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: …
[View More]medium
Component: DRM/AMDgpu
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: marc(a)dragonfly.plus.com
Created attachment 140936
--> https://bugs.freedesktop.org/attachment.cgi?id=140936&action=edit
dmesg output
I see the following warning during boot with Linux kernel 4.18.0-rc6 & 4.17.10:
root@deepthought:~# dmesg | grep WARN
[ 9.346100] WARNING: CPU: 11 PID: 1137 at
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_mst_types.c:88
dm_dp_aux_transfer+0xa5/0xc0 [amdgpu]
[ 9.346162] WARNING: CPU: 14 PID: 1139 at
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_mst_types.c:88
dm_dp_aux_transfer+0xa5/0xc0 [amdgpu]
Hardware is Ryzen 7 2700x, Sapphire Technology Radeon RX 480, IIyama ProLite
XB2380HS connected via DVI.
It looks like "dm_dp_aux_transfer" is used to setup DisplayPort, using "struct
drm_dp_aux_msg — DisplayPort AUX channel transaction". Now, with my hardware I
don't have any monitors connected via DisplayPort. Is that relevant?
I patched in a "printk("msg->size = %d\n", msg->size);" and it displays the
result twice, which is curious.
# dmesg | grep -i "msg->size"
[ 9.469511] msg->size = -5
[ 9.469803] msg->size = -5
Anyway, full "dmesg" attached.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=107376
Bug ID: 107376
Summary: Raven: `flush_delayed_work()` takes 500 ms
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: pmenzel+bugs.freedesktop(a)molgen.mpg.de
Created attachment 140811
--…
[View More]> https://bugs.freedesktop.org/attachment.cgi?id=140811&action=edit
HTML output of `sudo ./sleepgraph.py -config config/suspend-callgraph.cfg`
(devicelist: amdgpu, maxdepth: 12)
Created attachment 140810 [details]
HTML output of `sudo ./sleepgraph.py -config config/suspend-callgraph.cfg`
(devicelist: amdgpu, maxdepth: 12)
Profiling the suspend and resume time [1] on a MSI B350M MORTAR (MS-7A37) with
AMD Ryzen 3 2200G with Radeon Vega Graphics with Linux 4.18-rc6+ and
amd-staging-drm-next [2], `pci_pm_suspend()` takes over one second, which is
too long [3], cf. bug 107278 [3].
This is spent in `amdgpu_device_ip_resume_phase2()`, where 505 ms are spent in
`flush_delayed_work()`.
• flush_delayed_work (505.026 ms @ 98.640854)
[…]
• flush_work (505.017 ms @ 98.640863)
[…]
• wait_for_completion (504.985 ms @ 98.640894)
[…]
• schedule_timeout (504.963 ms @ 98.640914)
[…]
• schedule (504.963 ms @ 98.640914)
[1]: https://01.org/suspendresume
[2]: https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next
[3]: https://bugs.freedesktop.org/show_bug.cgi?id=107278
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=105433
Bug ID: 105433
Summary: Unreliable Modesetting on Tonga with two DVI Screens
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: freedesktop-bugs(a)digital-trauma.de
Two …
[View More]devices connected via DVI, one not coming up (powersave, no signal). On
retry , they may swap their working state, or both go to energy save, or
rarely, both work. This happens regardless of resolutions set on the screens in
question.
Screens: 2 x Benq G2222HDL
Connected via DVI (both straight to card)
Card: ASUS Strix R9285 DC2OC 2GD5
Kernel: amd-staging-drm-next 6e62bc7a123b "drm/amdgpu:Always save uvd vcpu_bo
in VM Mode"
Bug report as discussed in bug 100919.
Possibly related to bug 91202.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=107545
Bug ID: 107545
Summary: radeon - ring 0 stalled - GPU lockup - SI
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: julien.isorce(a)gmail.com
* Steps to reproduce:
for i in {0..300}; do (…
[View More]glxgears &); done (note that 100 might be enough
instead of 300)
* Actual result:
ring 0 stalled, gpu locakup, reset and x11 stops and cannot restart. The only
way is to reboot.
* Expected result:
The fps goes very low the more there are glxgears instances and no gpu lockup,
like with intel gpu.
* Infos:
card W600
mesa 18.2,
kernel 4.15.0-15-generic,
LLVM 7.0.0
xorg 1.20.99.1
xf86-video-ati 18.0.1.
(same result with kernel 4.4.0-130, mesa 12.0.6, llvm 3.8.0, DRM 2.43.0)
I was playing with the apitrace here
https://bugs.freedesktop.org/show_bug.cgi?id=87278#c31 and decided to through
dozens of glxgears instances to see.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=107539
Bug ID: 107539
Summary: Inverted colours after screen blank/unblank
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: barz621(a)gmail.com
Hello. On occasion the colours …
[View More]of my screen get inverted/washed out after a i
unblank the screen. It usually fixes itself after a few blank/unblank cycles.
I am running Arch (latest kernel drivers etc) on a Radeon 6850 GPU connected to
the monitor using display port (in case it matters). Using open drivers and
wayland with Enlightenment as desktop env. Checked with the E guys and it most
likely its not on their side.
Any more info i can provide? I don't see anything weird in the logs when this
happens.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=107324
Bug ID: 107324
Summary: Radeon driver fails to install with modprobe: ERROR:
could not insert 'radeon': Invalid argument
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.…
[View More]org
Reporter: jamesstewartmiller(a)gmail.com
Hi, on the following:
Advanced Micro Devices, Inc. [AMD/ATI] RV770/M98L [Mobility Radeon HD 4850]
on a 2009 imac running kubuntu 18.04 and kde 16.04 and kernel:
4.15.0-29-generic
I'm having no luck obtaining anything but the vesa driver.
The addition of nomodeset to the kernel parameters (booting from refind with no
grub) is necessary to get a graphical desktop. If I leave modesetting on, the
screen blacks out as the mode is changed. If I turn it off I get the vesa but
an error is reported that there is no ums available in the radeon module.
This has occurred on kde neon clean install and kubuntu.
Many thanks.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=107079
Bug ID: 107079
Summary: Black screen after waking from sleep
Product: DRI
Version: unspecified
Hardware: x86 (IA32)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: g.goltsov(a)gmail.com
Created attachment 140397
--> …
[View More]https://bugs.freedesktop.org/attachment.cgi?id=140397&action=edit
uname -a
After waking from sleep I get black screen on my notebook regardless of whether
x-server was starting or no.
I am able to type commands blindly. I can also connect to system via ssh.
But after adding "nomodeset" to kernel params system suspend and resume work
correctly.
I probed linux kernels 4.9 and 4.16. I also compiled modules radeon,drm,ttm
from recent sources.
Situation did not change.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]