| What | Removed | Added |
|---|---|---|
| Component | Driver/Radeon | Drivers/Gallium/radeonsi |
| Assignee | xorg-driver-ati@lists.x.org | dri-devel@lists.freedesktop.org |
| QA Contact | xorg-team@lists.x.org | dri-devel@lists.freedesktop.org |
| Product | xorg | Mesa |
Please attach the Xorg log file and the output of dmesg and gl= xinfo. This is more likely a Mesa or kernel issue than a Xorg driver one.
Created attachment 133590 [details]
glxinfo output after installing Mesa-demo-x
(In reply to laurie from comment #3) > Created attachment 133590 [details] > glxinfo output after installing Mesa-demo-x This is truncated, missing the beginning of the glxinfo output.
| What | Removed | Added |
|---|---|---|
| Attachment #133590 is obsolete | 1 |
Created attachment 133591 =
[details]
glxinfo - 2nd try
glxinfo using gnome terminal instead of Konsole
I might have the same bug I does not append with Mesa git from mid august but a version from beginnin= g of September do it. System boot, splash screen turn on, I login in KDE, sometime it fail and re= turn to login (X crash). With it work, doing stuff that require 3D card will sometime work or do graphics corruption and crash the system. When games work, it usually crash after not so long.. Even opening the KDE menu can trigger the crash, when t= hat append, the mouse usually work but nothing else (can't toggle numlock for example). Using magic keys usually work to reboot the system. Kernel 4.12 DDX GIT Mesa GIT libdrm from 22 Jul (might be old but mesa don't complain when I build it. Video card is a Polaris 10 card (RX480) /var/log/message get flooded by these when I open an opengl context: Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0: GPU fault detected: 146 0x0b02b714 Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0:=20=20 VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00106360 Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0:=20=20 VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0D0B7014 Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0: VM fault (0x14, vmid 6)= at page 1074016, write from 'SDM0' (0x53444d30) (183) Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0: GPU fault detected: 146 0x0b02b714 Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0:=20=20 VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00106362 Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0:=20=20 VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0D0B7014 Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0: VM fault (0x14, vmid 6)= at page 1074018, write from 'SDM0' (0x53444d30) (183) Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0: GPU fault detected: 146 0x0b02b714 Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0:=20=20 VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00106365 Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0:=20=20 VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0D0B7014 Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0: VM fault (0x14, vmid 6)= at page 1074021, write from 'SDM0' (0x53444d30) (183) Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0: GPU fault detected: 146 0x0b02b714 Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0:=20=20 VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00106367 Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0:=20=20 VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0D0B7014 Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0: VM fault (0x14, vmid 6)= at page 1074023, write from 'SDM0' (0x53444d30) (183) Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0: GPU fault detected: 146 0x0b0ab714 Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0:=20=20 VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00106369 Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0:=20=20 VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0D0B7014 Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0: VM fault (0x14, vmid 6)= at page 1074025, write from 'SDM0' (0x53444d30) (183) Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0: GPU fault detected: 146 0x0b0ab714 Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0:=20=20 VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0010636B Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0:=20=20 VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0D0B7014 Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0: VM fault (0x14, vmid 6)= at page 1074027, write from 'SDM0' (0x53444d30) (183) Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0: GPU fault detected: 146 0x0b0ab714 Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0:=20=20 VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0010636D Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0:=20=20 VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0D0B7014 Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0: VM fault (0x14, vmid 6)= at page 1074029, write from 'SDM0' (0x53444d30) (183) Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0: GPU fault detected: 146 0x0b0ab714 Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0:=20=20 VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0010636F Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0:=20=20 VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0D0B7014 Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0: VM fault (0x14, vmid 6)= at page 1074031, write from 'SDM0' (0x53444d30) (183) Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0: GPU fault detected: 146 0x0b12b714 Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0:=20=20 VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00106372 Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0:=20=20 VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0D0B7014 Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0: VM fault (0x14, vmid 6)= at page 1074034, write from 'SDM0' (0x53444d30) (183) Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0: GPU fault detected: 146 0x0b12b714 Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0:=20=20 VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00106374 Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0:=20=20 VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0D0B7014 Sep 11 15:26:44 tanith kernel: amdgpu 0000:0c:00.0: VM fault (0x14, vmid 6)= at page 1074036, write from 'SDM0' (0x53444d30) (183)
(In reply to Mathieu Belanger from comment #6) > I might have the same bug >=20 > I does not append with Mesa git from mid august but a version from beg= inning > of September do it. [...] > Kernel 4.12 If that means amd-staging-4.12, you're probably running into bug 102500.
(In reply to Michel D=C3=A4nzer from comment #7) > (In reply to Mathieu Belanger from comment #6) > > I might have the same bug > >=20 > > I does not append with Mesa git from mid august but a version fro= m beginning > > of September do it. >=20 > [...] >=20 > > Kernel 4.12 >=20 > If that means amd-staging-4.12, you're probably running into bug 102500. Yes, I did fix the one I wrote by switching the 4.13-rc5 (amd-staging-next,= I think) Now I might have got similar to OP, "randomly" crash and the mous= e was still alive. After about 5 minutes X suicided and I was able to get the message l= og and I saw a ton of: [drm:amdgpu_gem_object_create [amdgpu]] *ERROR* Failed to allocate GEM obje= ct (131072, 6, 131072, -12) That bug was also not present with 4.12/mid august mesa.
I forgot to mention, while the crash occured, the mouse was wo=
rking but
everything else was hang, including magic keys was doing nothing.
After X felt, I tried to login and I got an error about missing OpenGL 2 fr=
om
KDE so I did a full reboot, here the end of my message log.
[loop]
Sep 14 13:57:56 uk-dev kernel: [drm:amdgpu_gem_object_create [amdgpu]] *ERR=
OR*
Failed to allocate GEM object (33554432, 6, 131072, -12)
Sep 14 13:57:56 uk-dev kernel: [TTM] Out of kernel memory
Sep 14 13:57:56 uk-dev kernel: [TTM] Out of kernel memory
[/loop]
Sep 14 13:57:56 uk-dev kernel: [drm:amdgpu_gem_object_create [amdgpu]] *ERR=
OR*
Failed to allocate GEM object (33554432, 6, 131072, -12)
Sep 14 13:57:56 uk-dev kernel: [drm] Atomic commit: RESET. crtc id
0:[ffff880405ebb800]
Sep 14 13:57:56 uk-dev kernel: [drm] dc_commit_state: 0 streams
Sep 14 13:57:56 uk-dev polkitd[3633]: Unregistered Authentication Agent for
unix-session:/org/freedesktop/ConsoleKit/Session1 (system bus name :1.18,
object path /org/kde/PolicyKit1/AuthenticationAgent, locale en_US.utf8)
(disconnected from bus)
Sep 14 13:57:56 uk-dev kernel: [drm] Atomic commit: SET crtc id 0:
[ffff880405ebb800]
Sep 14 13:57:56 uk-dev kernel: [drm] dc_commit_state: 1 streams
Sep 14 13:57:56 uk-dev kernel: [drm] core_stream 0x4b321c00: src: 0, 0, 384=
0,
2160; dst: 0, 0, 3840, 2160, colorSpace:1
Sep 14 13:57:56 uk-dev kernel: [drm] \x09pix_clk_khz: 533250, h_total: 4000,
v_total: 2222, pixelencoder:1, displaycolorDepth:2
Sep 14 13:57:56 uk-dev kernel: [drm] \x09sink name: U28E590, serial: 810373=
197
Sep 14 13:57:56 uk-dev kernel: [drm] \x09link: 0
Sep 14 13:57:56 uk-dev kernel: [drm] dce_get_required_clocks_state: clocks
unsupported
Sep 14 13:57:56 uk-dev kernel: [drm] Link: 0 eDP panel mode supported: 0 eDP
panel mode enabled: 0=20
Sep 14 13:57:56 uk-dev kernel: [drm] [LKTN]\x09[DP][ConnIdx:0] HBR2x4 pass
VS=3D2, PE=3D0^
Sep 14 13:57:56 uk-dev kernel: [drm] [Mode]\x09[DP][ConnIdx:0] {3840x2160,
4000x2222@533250Khz}^
Sep 14 13:58:57 uk-dev slim[21180]: pam_unix(slim:session): session opened =
for
user destroyfx by destroyfx(uid=3D0)
[loop]
Sep 14 13:58:57 uk-dev kernel: [TTM] Out of kernel memory
Sep 14 13:58:57 uk-dev kernel: [TTM] Out of kernel memory
Sep 14 13:58:57 uk-dev kernel: [drm:amdgpu_gem_object_create [amdgpu]] *ERR=
OR*
Failed to allocate GEM object (131072, 6, 131072, -12)
[/loop]
| What | Removed | Added |
|---|---|---|
| Resolution | --- | MOVED |
| Status | NEW | RESOLVED |
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this = link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1276.