Created attachment 116559 [details]
As I can count, it's happens about every 10-15 start of VDPAU decoding, kernel traces vary.
Created attachment 116560 [details]
Created attachment 116561 [details]
Well the dmesg you have attached so far doesn't show any problem with the GFX driver, but rather an kernel oops completely unrelated to GFX.
Are you sure the problem is limited to VDPAU or do you have attached the wrong logs?
I'm only sure that this _when_ this is happening: when I start to play video with VDPAU.
And there was no other oopses in near past.
I had doubts about kernel, because I use -ck patchset. But I have switched to vanilla linux from git, and git version of mesa and I have encountered same issue when I started to play video.
Created attachment 116614 [details]
mplayer uvd crash 270x
This is going to be the last from me on R9270X issues as my card seems to have died :-(
Shan't be buying HIS again - it was only 15 months old.
But anyway I retested my mplayer start uvd script when I saw this and it did go quicker than usual (12 starts), so I don't know if something new has developed.
My Oops does mention GPU stuff - historically I have managed to get Oopses/OOMs that don't with the same test.
Maybe Yuriy could try with mesa commit
reverted to see if it is something different from my old bug
(In reply to Andy Furniss from comment #6)
> Created attachment 116614 [details]
> mplayer uvd crash 270x
At least that crash shows something GFX driver related. Yuriy's dmesg looks like a crash in the poll() system call which doesn't looks like it is related to GFX at all.
Especially I don't have any idea where to start looking for the cause of this.
> This is going to be the last from me on R9270X issues as my card seems to
> have died :-(
Well that's sad. Did an elco plopped open or does it just don't work any more? Maybe we could do something about it.
(In reply to Christian König from comment #7)
> > This is going to be the last from me on R9270X issues as my card seems to
> > have died :-(
> Well that's sad. Did an elco plopped open or does it just don't work any
> more? Maybe we could do something about it.
Well now I am not 100% sure as I am getting mobo issues without it - took me 3 attempts to post today (without card - mobo has RS880).
Saying that it does still seem to be also broken - I guess I won't know until I can test it in another mobo, which I can't do any time soon.
The symptoms are that it will display bios level things like boot up and the instant browser/stuff the mobo has, but there are minor corruptions with DVI and HDMI output doesn't come on at all. As soon as a driver loads (Windows 7 or Linux) I am hard locked - even h/w reset button won't work.
*** Bug 83998 has been marked as a duplicate of this bug. ***
-- 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/1220.