Hi all, On Wed, May 2, 2018 at 4:39 AM, Qu, Jim <Jim.Qu at amd.com> wrote: > Hi , > > If you are sure that the HW worked fine before. I think you should: > > 1. Be sure that HW works fine now. > 2. recall the driver to the point at where it works well, and then replace them one by one to confirm component which causes the issue. > 3. try to update the last VBIOS to adapt new driver. > > Thanks > JimQu > > ________________________________________ > å??件人: amd-gfx <amd-gfx-bounces at lists.freedesktop.org> 代表 Christian König <christian.koenig at amd.com> > å??é??æ?¶é?´: 2018å¹´4æ??30æ?¥ 1:16:14 > æ?¶ä»¶äºº: Mathieu Malaterre; Deucher, Alexander > æ??é??: David Airlie; Zhou, David(ChunMing); dri-devel; amd-gfx at lists.freedesktop.org; LKML > 主é¢?: Re: Tracking: radeon 0000:00:10.0: ring 0 stalled for more than 10240msec > > Am 23.04.2018 um 20:50 schrieb Mathieu Malaterre: >> Hi there, >> >> I am pretty sure I was able to run kodi on an old Mac Mini G4 (big >> endian) with AMD RV280. Today it is failing to start with: > > Well, that is rather old hardware. I suggest to make sure first that the > hw isn't broken in some way. > >> How should I go and debug this (other than plain git-bisect) ? > > You first need to figure out what's the failing component. Either Mesa, > DDX or the Kernel are possible candidates. > > Another possibility is that you updated kodi and kodi is now doing > something the hw doesn't like. That was my mistake, I forgot about AGP vs PCI on radeon. Should be fixed in next release: https://patchwork.kernel.org/patch/10360887/ > Regards, > Christian. > _______________________________________________ > amd-gfx mailing list > amd-gfx at lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/amd-gfx
