https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #88 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
Great, thanks.(In reply to Ricardo Ribalda from comment #87)
> Hi Andrey
>
> I have been running some manual tests (~30 boots) and it has been always ok.
> I did not have
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #87 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Hi Andrey
I have been running some manual tests (~30 boots) and it has been always ok. I
did not have time to setup an automatic test machine.
You are more than welcome to
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #86 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
Hi, any updates (In reply to Andrey Grodzovsky from comment #85)
> (In reply to Ricardo Ribalda from comment #84)
> > Hi Andrey
> >
> > I have removed the
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #85 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
(In reply to Ricardo Ribalda from comment #84)
> Hi Andrey
>
> I have removed the GALLIUM_DDEBUG=flush hack and performed around 10 boots.
> I have not been able to
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #84 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Hi Andrey
I have removed the GALLIUM_DDEBUG=flush hack and performed around 10 boots. I
have not been able to replicate the bug.
I am porting the patch to my current distro
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #83 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
Created attachment 275403
--> https://bugzilla.kernel.org/attachment.cgi?id=275403=edit
set COMPUTE_PGM_RSRC1 for SGPR/VGPR clearing
Please test this patch by Nicolai who
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #82 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Hi Andrey.
Excellent news, thanks for your effort on this.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #81 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
With Betong board it seems I reproduced it, I am trying to debug it more +
involving MESA/LLVM people to take a look.
--
You are receiving this mail because:
You are
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #80 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
(In reply to Ricardo Ribalda from comment #79)
> Hi Jerome
>
> Not really, I am waiting for some feedback from Andrey.
>
>
> With the env. variable:
>
>
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #79 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Hi Jerome
Not really, I am waiting for some feedback from Andrey.
With the env. variable:
GALLIUM_DDEBUG=flush
it works better, but still not perfect.
Andrey, did you
https://bugzilla.kernel.org/show_bug.cgi?id=198883
Jerome Oufella (jer...@oufella.com) changed:
What|Removed |Added
CC||jer...@oufella.com
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #77 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
(In reply to Ricardo Ribalda from comment #76)
> I was testing with GALLIUM_DDEBUG=flush
>
> When I removed it:
>
>
> amdgpu.cg_mask=0 amdgpu.pg_mask=0 : Stalls
>
>
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #76 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
I was testing with GALLIUM_DDEBUG=flush
When I removed it:
amdgpu.cg_mask=0 amdgpu.pg_mask=0 : Stalls
iommu=off amdgpu.cg_mask=0 amdgpu.pg_mask=0 : Also stalls
:(
--
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #75 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
(In reply to Ricardo Ribalda from comment #74)
> Hi Andrey
>
> They patch did not do the trick :(.
>
> Shall I try also with the patch and amdgpu.cg_mask=0 amdgpu.pg_mask=0
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #74 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Hi Andrey
They patch did not do the trick :(.
Shall I try also with the patch and amdgpu.cg_mask=0 amdgpu.pg_mask=0
--
You are receiving this mail because:
You are watching
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #73 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
Created attachment 274867
--> https://bugzilla.kernel.org/attachment.cgi?id=274867=edit
Exclude HIQ patch
So if IOMMU disabling does makes a difference can you please try
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #72 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
With iommu=off I can still see the error after around 3 attempts
With iommu=off amdgpu.cg_mask=0 amdgpu.pg_mask=0 I could not see the stall
after 30 boots
With
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #70 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
Just another while guess also , try mod probing amdgpu with power and clock
gating disabled to see if it makes a difference
sudo modprobe amdgpu cg_mask=0 pg_mask=0
--
You
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #71 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
(In reply to Ricardo Ribalda from comment #69)
> This is my kernel configuration:
>
>
> ricardo@neopili:~/curro/kernel-upstream$ cat .config | grep -i IOMMU
>
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #69 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
This is my kernel configuration:
ricardo@neopili:~/curro/kernel-upstream$ cat .config | grep -i IOMMU
CONFIG_GART_IOMMU=y
# CONFIG_CALGARY_IOMMU is not set
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #68 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
(In reply to Ricardo Ribalda from comment #67)
> I have coreboot. So I do not have the typical menu.
>
> I have an FPGA writing to the main memory, and that could not happen
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #67 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
I have coreboot. So I do not have the typical menu.
I have an FPGA writing to the main memory, and that could not happen if iommu
is enabled without extra configuration.
If
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #66 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
(In reply to Ricardo Ribalda from comment #65)
> Hi
>
> IOMMU is disabled:
>
> root@qt5122:~# ls /sys/class/iommu
> ls: cannot access '/sys/class/iommu': No such file or
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #65 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Hi
IOMMU is disabled:
root@qt5122:~# ls /sys/class/iommu
ls: cannot access '/sys/class/iommu': No such file or directory
root@qt5122:~# dmesg | grep -i iommu
root@qt5122:~#
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #64 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
Actually i was given info that a similar problem on Bettong board was related
to IOMMU. Can you check if IOMMU is enabled in your BIOS , if it is, disable it
and check if the
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #63 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Here you are
gfx80.mmCB_DEBUG_BUS_1 => 0x8801
gfx80.mmCB_DEBUG_BUS_2 => 0x
gfx80.mmCB_DEBUG_BUS_3 => 0x
gfx80.mmCB_DEBUG_BUS_4 => 0x
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #62 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
Hi, sorry , was busy a bit with other stuff.
Can you please give another bit of info reading some debug data from color
buffer (CB)
Reproduce it and then from UMR do
sudo
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #61 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Hi Andrey
You are more quite than you use to ;). Do you need anything else from my side?
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #60 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
(In reply to Ricardo Ribalda from comment #59)
> Hi Andrey
>
> Testing with llvm7 setup:
>
>
> R600_DEBUG=notiling,norbplus xinit
>
> does not avoid the hang :(
>
> [
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #59 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Hi Andrey
Testing with llvm7 setup:
R600_DEBUG=notiling,norbplus xinit
does not avoid the hang :(
[ 31.200134] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #58 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
Please try following to see if it helps avoiding the hang =
R600_DEBUG=notiling,norbplus
try with GALLIUM_DDEBUG=flush to see if it makes a difference (flushes after
each
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #57 from Nicolai Hähnle (nhaeh...@gmail.com) ---
(In reply to Ricardo Ribalda from comment #46)
This was due to the constant address space change in LLVM. It has since been
fixed in Mesa master.
--
You are receiving this mail
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #56 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Bettong is the reference Merlin Falcon board from AMD, I think they reference
it also as DB-FP4. It is also supported by coreboot.
--
You are receiving this mail because:
You
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #55 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Created attachment 274685
--> https://bugzilla.kernel.org/attachment.cgi?id=274685=edit
urm dump with llvm7
--
You are receiving this mail because:
You are watching the
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #54 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Created attachment 274683
--> https://bugzilla.kernel.org/attachment.cgi?id=274683=edit
ddebug dumps with llvm7
--
You are receiving this mail because:
You are watching the
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #53 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
Don't think I have since I don't know what it is.
So since it failed with LLVM 7 that not the problem then.
We can try again getting more detailed logs from SAME hang as
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #52 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
Don't think I have since I don't know what it is.
So since it failed with LLVM 7 that not the problem then.
We can try again getting more detailed logs from SAME hang as
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #51 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Andrey, do you have access to a Bettong board? If so I can send you an image
where you can get the stall.
--
You are receiving this mail because:
You are watching the assignee
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #49 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
(In reply to Andrey Grodzovsky from comment #48)
> Is it LLVM 7.0 in this case ?
Yes: OpenGL renderer string: AMD Radeon R7 Graphics (CARRIZO / DRM 3.23.0 /
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #50 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Created attachment 274679
--> https://bugzilla.kernel.org/attachment.cgi?id=274679=edit
glxinfo with llvm7
--
You are receiving this mail because:
You are watching the
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #48 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
Is it LLVM 7.0 in this case ?
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
dri-devel
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #47 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Just for the fun of it, I have tried 4.16.0-rc4 + llvm git HEAD + mesa git
HEAD + libdrm 2.4.91 + xf86-video-amdgpu_18.0.0 + libxcb_1.13.bb and X starts.
Unfortunately it also
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #46 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
(In reply to Nicolai Hähnle from comment #44)
> For the LLVM problem, please provide the log output from starting X with
> R600_DEBUG=vs,ps in the environment.
Here you are.
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #45 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
(In reply to Michel Dänzer from comment #43)
> (In reply to Ricardo Ribalda from comment #42)
> > With current LLVM7 master X does not start at all. I get the following
> >
https://bugzilla.kernel.org/show_bug.cgi?id=198883
Nicolai Hähnle (nhaeh...@gmail.com) changed:
What|Removed |Added
CC||nhaeh...@gmail.com
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #43 from Michel Dänzer (mic...@daenzer.net) ---
(In reply to Ricardo Ribalda from comment #42)
> With current LLVM7 master X does not start at all. I get the following
> output:
Did you recompile current Mesa Git master against that
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #42 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
With current LLVM7 master X does not start at all. I get the following output:
root@qt5122:~# X
X.Org X Server 1.19.3
Release Date: 2017-03-15
X Protocol Version 11, Revision
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #41 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
I am actually use debian packages for LLVM 7 so can't tell you, but you will
now it's LLVM7 once you install it and run glxinfo - it will show LLVM version
you are using.
--
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #40 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Seems that I am already using the latest firmware files.
I will try to switch to llvm7, but that will require a bit of compilation time,
it is not a 5 minutes job. Just to be
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #39 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
(In reply to Ricardo Ribalda from comment #38)
> Just for the fun of it, I did try the amdgpu.gpu_recovery=1 module parameter,
>
>
> It seems to detect properly the crash,
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #38 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Just for the fun of it, I did try the amdgpu.gpu_recovery=1 module parameter,
It seems to detect properly the crash, but fails miserably on the recovery. The
screens blanks
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #37 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Created attachment 274589
--> https://bugzilla.kernel.org/attachment.cgi?id=274589=edit
Dmesg for 4.16 rc4
--
You are receiving this mail because:
You are watching the
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #36 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Hi Andrey
I just tried with commit ce380619fab99036f5e745c7a865b21c59f005f6
Linux version 4.16.0-rc4-qtec-standard+ (ricardo@neopili) (gcc version 7.3.0
(Debian 7.3.0
-5)) #1
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #35 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
I will take a look at the register dumps and also forward them to a few people
to take a look.
DId you consider to try and run the latest mainline kernel from
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #34 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Created attachment 274581
--> https://bugzilla.kernel.org/attachment.cgi?id=274581=edit
Stalled after starting X. Gdb also stalls
sudo umr -O many,bits -r
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #33 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Last dump belongs to a stall after running dmesg. (similar to yesterdays dump
1).
The next one happens after running Xorg. This time, gdb also stalls when trying
to get a dump:
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #32 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Created attachment 274579
--> https://bugzilla.kernel.org/attachment.cgi?id=274579=edit
sudo umr -O many,bits -r *.gfx80.mmGRBM_STATUS &> stall sudo umr -O many,bits
-r
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #31 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Hi Andrey
I mean a stall, sorry about that.
root@qt5122:~# ps aux | grep Xorg
root 520 0.0 0.0 15936 900 ?S07:59 0:00 xinit
/etc/X11/Xsession --
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #30 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
Using UMR please provide following data:
sudo umr -O many,bits -r *.gfx80.mmGRBM_STATUS
sudo umr -O many,bits -r *.gfx80.HEADER_DUMP
sudo umr -O many,bits -r
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #29 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
Thanks for the logs, just to clear things out, you keep saying 'crash', but you
actually mean hang, right ? Or do observe actual Xorg process crash ? To answer
for sure check
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #28 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Here you go!
umr dump 0 is a crash just after starting X
umr dump 1 is a crash after running dmesg inside xterm just after starting X
Thanks!
--
You are receiving this mail
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #27 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Created attachment 274537
--> https://bugzilla.kernel.org/attachment.cgi?id=274537=edit
umr dump 1
--
You are receiving this mail because:
You are watching the assignee of
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #26 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Created attachment 274535
--> https://bugzilla.kernel.org/attachment.cgi?id=274535=edit
Umr dump 0
--
You are receiving this mail because:
You are watching the assignee of
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #25 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Hi Andrey
Back from the Embedded World.
My firmware versions:
root@qt5122:~# cat /sys/kernel/debug/dri/0/amdgpu_firmware_info
VCE feature version: 0, firmware version:
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #24 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
Created attachment 274473
--> https://bugzilla.kernel.org/attachment.cgi?id=274473=edit
UMR output improvement
--
You are receiving this mail because:
You are watching the
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #23 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
Looked a bit more into the ftraces, fence from gfx ring, context=80 seqno=10
which is a drm_sched_fence.finished fence is never signaled so next time when
same slot (slot 10)
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #22 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
I tried cold resets around 15 times (taking out the power cord) running lightdm
manger or directly xinit and haven't seen any hang.
Let me know your firmware versions -
cat
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #21 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
Yea, you right, forgot all about the cold reset part you mentioned so will
retry again on Monday. In the meanwhile you can at least try switching to LLVM
7 and see if this
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #20 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Did you power cycle your platform between attempts?
By latest upstream you mean tip of the git devel? I did update to the last
release of Mesa, libdrm, llvm, xorg-amdgpu
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #19 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
I tried on my Ubuntu multiple times with both starting and stopping desktop
manager and just xinint. Didn't observe any hang,
this is relevant SW info from my glxinfo
OenGL
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #18 from Michel Dänzer (mic...@daenzer.net) ---
(In reply to Ricardo Ribalda from comment #17)
> -able to login remotely via ssh.
>
> -I tried to reset the gpu by using /sys/kernel/debug/dri/0/amdgpu_gpu_reset,
> and the result is a
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #17 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
The description of what/how it happens and the backtraces:
-able to login remotely via ssh.
-I tried to reset the gpu by using /sys/kernel/debug/dri/0/amdgpu_gpu_reset,
and
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #16 from Michel Dänzer (mic...@daenzer.net) ---
(In reply to Ricardo Ribalda from comment #14)
> Please bare in mind that #151341 seems very related, [...]
What makes you think so? If it's that the backtraces look similar, that's
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #15 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
Yep, I noticed the other bug.
Thanks,
Andrey
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #14 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Thanks Andrey
Please bare in mind that #151341 seems very related, so this bug might be
happening in more platforms.
--
You are receiving this mail because:
You are watching
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #13 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
Thanks for all the info, I will later try to reproduce it on my CZ setup.
Andrey
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #12 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Created attachment 274401
--> https://bugzilla.kernel.org/attachment.cgi?id=274401=edit
glxinfo
--
You are receiving this mail because:
You are watching the assignee of the
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #11 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Distro
I am using Yocto Project
Launching X with:
/etc/init.d/xserver-nodm start
that launches
su -l -c '/etc/xserver-nodm/Xserver &' $USER
that calls xinit internally.
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #10 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
Are you starting X with xstart or xinit or some desktop manager ? Can you also
provide output of glxinfo ? BTW what distro are you running ?
--
You are receiving this mail
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #9 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
I just have to start up the system and around 1 out of 10 times X will crash
with no human intervention.
X manages to render some of the screen, like the window decorator or the
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #8 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
How you reproduce it and how often does it happen ?
Andrey
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #7 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Traces obtained with trace-cmd record -e dma_fence:* -e amdgpu:* -e gpu_sched:*
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #6 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Created attachment 274399
--> https://bugzilla.kernel.org/attachment.cgi?id=274399=edit
trace.txt
--
You are receiving this mail because:
You are watching the assignee of the
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #5 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Created attachment 274397
--> https://bugzilla.kernel.org/attachment.cgi?id=274397=edit
trace.dat
--
You are receiving this mail because:
You are watching the assignee of the
https://bugzilla.kernel.org/show_bug.cgi?id=198883
Andrey Grodzovsky (andrey.grodzov...@amd.com) changed:
What|Removed |Added
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #2 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Created attachment 274355
--> https://bugzilla.kernel.org/attachment.cgi?id=274355=edit
xorg log
--
You are receiving this mail because:
You are watching the assignee of the
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #1 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Created attachment 274353
--> https://bugzilla.kernel.org/attachment.cgi?id=274353=edit
dmesg
--
You are receiving this mail because:
You are watching the assignee of the
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #3 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Created attachment 274357
--> https://bugzilla.kernel.org/attachment.cgi?id=274357=edit
xorg.conf
--
You are receiving this mail because:
You are watching the assignee of the
88 matches
Mail list logo
