From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 60879] [radeonsi] X11 can't start with acceleration enabled Date: Sat, 03 May 2014 13:02:13 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1796941877==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id DFB4B6E7D8 for ; Sat, 3 May 2014 06:02:13 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1796941877== Content-Type: multipart/alternative; boundary="1399122133.bf422753.13040"; charset="us-ascii" --1399122133.bf422753.13040 Date: Sat, 3 May 2014 13:02:13 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable https://bugs.freedesktop.org/show_bug.cgi?id=3D60879 --- Comment #81 from Pali Roh=C3=A1r --- (In reply to comment #74) > Created attachment 98257 [details] [review] > Fix v2 >=20 > Pali, I have sent this patch to the mailing list for review, can you conf= irm > that it fixes the issue for you. Hello, I applied this patch on top of mesa, but it is not working :-( Xserv= er show only black screen. And in dmesg I see this: [ 31.269778] radeon 0000:05:00.0: GPU fault detected: 147 0x09e25201 [ 31.269785] radeon 0000:05:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR=20= =20 0x0E6B9BCF [ 31.269788] radeon 0000:05:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02052001 [ 31.269792] VM fault (0x01, vmid 1) at page 241933263, read from CB_CMASK (82) In Xorg.0.log are no errors. After killing X in dmesg are these lines: [ 307.388090] radeon 0000:05:00.0: GPU lockup CP stall for more than 276120msec [ 307.388104] radeon 0000:05:00.0: GPU lockup (waiting for 0x0000000000000= 002 last fence id 0x0000000000000001 on ring 0) [ 312.832194] pci_pm_runtime_suspend(): radeon_pmops_runtime_suspend+0x0/0= xc0 [radeon] returns -22 [ 320.270503] detected fb_set_par error, error code: -22 When I start X again, it immediately crash and in Xorg.0.log are these erro= rs: [ 320.199] drmOpenDevice: node name is /dev/dri/card0 [ 320.199] drmOpenDevice: open result is -1, (Invalid argument) [ 320.199] drmOpenByBusid: Searching for BusID pci:0000:05:00.0 [ 320.199] drmOpenDevice: node name is /dev/dri/card0 [ 320.199] drmOpenDevice: open result is -1, (Invalid argument) ... [ 320.270] (EE) RADEON(0): [drm] Failed to open DRM device for pci:0000:05:00.0: No such file or directory [ 320.270] (EE) RADEON(0): Kernel modesetting setup failed [ 320.270] (II) UnloadModule: "radeon" [ 320.270] (II) Unloading radeon [ 320.270] (EE) Screen(s) found, but none have a usable configuration. [ 320.270]=20 Fatal server error: [ 320.270] no screens found Old patch (which can be applied on older mesa version) worked fine without = any problem. Note that I did not changed kernel, still using same version 3.14-= rc1. --=20 You are receiving this mail because: You are the assignee for the bug. --1399122133.bf422753.13040 Date: Sat, 3 May 2014 13:02:13 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Commen= t # 81 on bug 60879<= /a> from Pali Roh=C3=A1r 
(In reply to comment #=
74)
> Created attachment 98257 =
[d=
etails] [review] [review]
> Fix v2
>=20
> Pali, I have sent this patch to the mailing list for review, can you c=
onfirm
> that it fixes the issue for you.

Hello, I applied this patch on top of mesa, but it is not working :-( Xserv=
er
show only black screen. And in dmesg I see this:

[   31.269778] radeon 0000:05:00.0: GPU fault detected: 147 0x09e25201
[   31.269785] radeon 0000:05:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR=20=
=20
0x0E6B9BCF
[   31.269788] radeon 0000:05:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x02052001
[   31.269792] VM fault (0x01, vmid 1) at page 241933263, read from CB_CMASK
(82)

In Xorg.0.log are no errors.

After killing X in dmesg are these lines:

[  307.388090] radeon 0000:05:00.0: GPU lockup CP stall for more than
276120msec
[  307.388104] radeon 0000:05:00.0: GPU lockup (waiting for 0x0000000000000=
002
last fence id 0x0000000000000001 on ring 0)
[  312.832194] pci_pm_runtime_suspend(): radeon_pmops_runtime_suspend+0x0/0=
xc0
[radeon] returns -22
[  320.270503] detected fb_set_par error, error code: -22

When I start X again, it immediately crash and in Xorg.0.log are these erro=
rs:

[   320.199] drmOpenDevice: node name is /dev/dri/card0
[   320.199] drmOpenDevice: open result is -1, (Invalid argument)
[   320.199] drmOpenByBusid: Searching for BusID pci:0000:05:00.0
[   320.199] drmOpenDevice: node name is /dev/dri/card0
[   320.199] drmOpenDevice: open result is -1, (Invalid argument)
...
[   320.270] (EE) RADEON(0): [drm] Failed to open DRM device for
pci:0000:05:00.0: No such file or directory
[   320.270] (EE) RADEON(0): Kernel modesetting setup failed
[   320.270] (II) UnloadModule: "radeon"
[   320.270] (II) Unloading radeon
[   320.270] (EE) Screen(s) found, but none have a usable configuration.
[   320.270]=20
Fatal server error:
[   320.270] no screens found

Old patch (which can be applied on older mesa version) worked fine without =
any
problem. Note that I did not changed kernel, still using same version 3.14-=
rc1.

You are receiving this mail because: =20=20=20=20=20=20
  • You are the assignee for the bug.
--1399122133.bf422753.13040-- --===============1796941877== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============1796941877==--