https://bugs.freedesktop.org/show_bug.cgi?id=108361
Bug ID: 108361
Summary: Radeon/Xorg crash during boot with Radeon R5 M230
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: jian-hong(a)endlessm.com
Created …
[View More]attachment 142025
--> https://bugs.freedesktop.org/attachment.cgi?id=142025&action=edit
journal log when radeon/Xorg crash
This is found on Acer Veriton Z4660G desktop equipped with Intel(R) Core(TM)
i7-8700 CPU and an AMD/ATI Jet PRO Radeon R5 M230 graphic card.
01:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Jet
PRO [Radeon R5 M230] [1002:6665] (rev 83)
Subsystem: PC Partner Limited / Sapphire Technology Jet PRO [Radeon R5
M230] [174b:e332]
Flags: bus master, fast devsel, latency 0, IRQ 127
Memory at 90000000 (64-bit, prefetchable) [size=256M]
Memory at 7c300000 (64-bit, non-prefetchable) [size=256K]
I/O ports at 4000 [size=256]
Expansion ROM at 7c340000 [disabled] [size=128K]
Capabilities: [48] Vendor Specific Information: Len=08 <?>
Capabilities: [50] Power Management version 3
Capabilities: [58] Express Legacy Endpoint, MSI 00
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010
<?>
Capabilities: [150] Advanced Error Reporting
Capabilities: [200] #15
Capabilities: [270] #19
Kernel driver in use: radeon
Kernel modules: radeon, amdgpu
I have tested it with Linux kernel 4.19-rc7. System (radeon module) sometimes
hits the error during boot, then Xorg crashes.
Oct 12 17:28:52 endless kernel: [drm:atom_op_jump [radeon]] *ERROR* atombios
stuck in loop for more than 5secs aborting
Oct 12 17:28:52 endless kernel: [drm:atom_execute_table_locked [radeon]]
*ERROR* atombios stuck executing 67C0 (len 254, WS 0, PS 4) @ 0x67CE
Oct 12 17:28:52 endless kernel: [drm:atom_execute_table_locked [radeon]]
*ERROR* atombios stuck executing 612C (len 78, WS 12, PS 8) @ 0x6165
Oct 12 17:28:52 endless kernel: iwlwifi 0000:00:14.3: HCMD_ACTIVE already clear
for command SCAN_REQ_UMAC
Oct 12 17:28:52 endless kernel: [drm] PCIE gen 3 link speeds already enabled
Oct 12 17:28:54 endless kernel: radeon 0000:01:00.0: Wait for MC idle timedout
!
Oct 12 17:28:54 endless kernel: radeon 0000:01:00.0: Wait for MC idle timedout
!
Oct 12 17:28:54 endless eos-metrics-ins[606]: Failed to start GeoClue2 client:
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected
from message bus without replying.
Oct 12 17:28:54 endless kernel: [drm] PCIE GART of 2048M enabled (table at
0x0000000000040000).
Oct 12 17:28:54 endless kernel: radeon 0000:01:00.0: WB enabled
Oct 12 17:28:54 endless kernel: radeon 0000:01:00.0: fence driver on ring 0 use
gpu addr 0x0000000080000c00 and cpu addr 0x000000007d0c53c5
Oct 12 17:28:54 endless kernel: radeon 0000:01:00.0: fence driver on ring 1 use
gpu addr 0x0000000080000c04 and cpu addr 0x000000006e1c12be
Oct 12 17:28:54 endless kernel: radeon 0000:01:00.0: fence driver on ring 2 use
gpu addr 0x0000000080000c08 and cpu addr 0x00000000a603d5e9
Oct 12 17:28:54 endless kernel: radeon 0000:01:00.0: fence driver on ring 3 use
gpu addr 0x0000000080000c0c and cpu addr 0x0000000039a9e421
Oct 12 17:28:54 endless kernel: radeon 0000:01:00.0: fence driver on ring 4 use
gpu addr 0x0000000080000c10 and cpu addr 0x00000000ba920de2
Oct 12 17:28:55 endless kernel: [drm:r600_ring_test [radeon]] *ERROR* radeon:
ring 0 test failed (scratch(0x850C)=0xCAFEDEAD)
Oct 12 17:28:55 endless kernel: [drm:si_resume [radeon]] *ERROR* si startup
failed on resume
I also tried to disable radeon's runtime power management by passing
"radeon.runpm=0" to boot command. It makes system working stable on this
model.
--
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]
https://bugs.freedesktop.org/show_bug.cgi?id=106474
Bug ID: 106474
Summary: "CPU1 stuck for XXs: Xorg" since update to
linux-4.16.x
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: linuxhippy(a)gmail.com
Created …
[View More]attachment 139489
--> https://bugs.freedesktop.org/attachment.cgi?id=139489&action=edit
screenshot
After updating the Laptop of a friend running Fedora 27 to linux-4.16.4/5/6 it
frequently gets stuck when starting Xorg - please see the attached screenshot.
The machine is a AMD Beema based Hewlett-Packard HP 355 G2/22C1, BIOS F.10
02/12/2015 running the latest Fedora 27 packages.
Graphics stack is default (glamor, radeon kernel module).
Linux-4.15.17 works absolutly flawless.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=106471
Bug ID: 106471
Summary: Radeon HD 3450 acceleration not working
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: jjcogliati-r1(a)yahoo.com
Created attachment 139483
…
[View More] --> https://bugs.freedesktop.org/attachment.cgi?id=139483&action=edit
full dmesg
The Radeon HD 3450 acceleration support does not work on my computer.
uname -a:
Linux mouse 4.17.0-041700rc4-generic #201805070430 SMP Mon May 7 04:31:46 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
In the dmesg I get:
[ 4.007419] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed
(scratch(0x8504)=0xCAFEDEAD)
[ 4.007433] radeon 0000:02:00.0: disabling GPU acceleration
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=106191
Bug ID: 106191
Summary: Failure to recognize DisplayPort signal
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: francois.jacques(a)gmail.com
Created attachment 139004
-…
[View More]-> https://bugs.freedesktop.org/attachment.cgi?id=139004&action=edit
callstack from DRM/radeon
DRM/radeon fails with in drm_dp_link_rate_to_bw_code
Driver fails to negotiate video resolution with DP-connected monitor, on any of
4 DP ports.
Controller can drive monitor at 2048x1080 through HDMI adapter. Straight DP
cable only works in console (low-res)
Disconnecting power cable from monitor for 5 minutes trick doesn't help ;)
Video controller: FirePro v8800 ChipID 0x6888 (see hardware.txt for details, 4
DPs)
DP monitor: Dell U2717DA
Workstation: HP xw8600
Kernel messages with backtrace: see var_log_messages_excerpt.txt
Max res supported by monitor: 1440p (see Xorg.0.log)
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=105728
Bug ID: 105728
Summary: radeon_init takes longer than a few seconds
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: pmenzel+bugs.freedesktop(a)molgen.mpg.de
On a Asus F2A85-M PRO with …
[View More]an AMD A6-6400K APU with Radeon HD Graphics and
Linux 4.14.13 `radeon_init`, according to `initcall_debug`, takes over two
seconds to execute. Init functions should not take longer than a few
milliseconds to load.
```
$ sudo dmesg | grep -i radeon
[ 18.767379] calling radeon_init+0x0/0xab [radeon] @ 292
[ 18.767382] [drm] radeon kernel modesetting enabled.
[ 18.809797] radeon 0000:00:01.0: VRAM: 768M 0x0000000000000000 -
0x000000002FFFFFFF (768M used)
[ 18.809798] radeon 0000:00:01.0: GTT: 1024M 0x0000000030000000 -
0x000000006FFFFFFF
[ 18.811498] [drm] radeon: 768M of VRAM memory ready
[ 18.811499] [drm] radeon: 1024M of GTT memory ready.
[ 18.812019] radeon 0000:00:01.0: firmware: direct-loading firmware
radeon/ARUBA_pfp.bin
[ 18.812512] radeon 0000:00:01.0: firmware: direct-loading firmware
radeon/ARUBA_me.bin
[ 18.812674] radeon 0000:00:01.0: firmware: direct-loading firmware
radeon/ARUBA_rlc.bin
[ 18.812813] [drm] radeon: dpm initialized
[ 18.813730] radeon 0000:00:01.0: firmware: direct-loading firmware
radeon/TAHITI_uvd.bin
[ 18.814178] radeon 0000:00:01.0: firmware: direct-loading firmware
radeon/TAHITI_vce.bin
[ 18.867545] radeon 0000:00:01.0: WB enabled
[ 18.867549] radeon 0000:00:01.0: fence driver on ring 0 use gpu addr
0x0000000030000c00 and cpu addr 0xffff8a5af9339c00
[ 18.867928] radeon 0000:00:01.0: fence driver on ring 5 use gpu addr
0x0000000000075a18 and cpu addr 0xffffab8a01435a18
[ 18.888018] radeon 0000:00:01.0: fence driver on ring 6 use gpu addr
0x0000000030000c18 and cpu addr 0xffff8a5af9339c18
[ 18.888021] radeon 0000:00:01.0: fence driver on ring 7 use gpu addr
0x0000000030000c1c and cpu addr 0xffff8a5af9339c1c
[ 18.888022] radeon 0000:00:01.0: fence driver on ring 1 use gpu addr
0x0000000030000c04 and cpu addr 0xffff8a5af9339c04
[ 18.888024] radeon 0000:00:01.0: fence driver on ring 2 use gpu addr
0x0000000030000c08 and cpu addr 0xffff8a5af9339c08
[ 18.888025] radeon 0000:00:01.0: fence driver on ring 3 use gpu addr
0x0000000030000c0c and cpu addr 0xffff8a5af9339c0c
[ 18.888026] radeon 0000:00:01.0: fence driver on ring 4 use gpu addr
0x0000000030000c10 and cpu addr 0xffff8a5af9339c10
[ 18.916268] radeon 0000:00:01.0: radeon: MSI limited to 32-bit
[ 18.917088] radeon 0000:00:01.0: radeon: using MSI.
[ 18.917113] [drm] radeon: irq initialized.
[ 20.736792] [drm] Radeon Display Connectors
[ 21.035055] fbcon: radeondrmfb (fb0) is primary device
[ 21.152576] radeon 0000:00:01.0: fb0: radeondrmfb frame buffer device
[ 21.172202] [drm] Initialized radeon 2.50.0 20080528 for 0000:00:01.0 on
minor 0
[ 21.172314] initcall radeon_init+0x0/0xab [radeon] returned 0 after 2348527
usecs
[ 126.973651] radeon_dp_aux_transfer_native: 74 callbacks suppressed
```
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]