Re: [Ask for help] ATI HD 7470 card on arm64 platform
On 7 December 2017 at 19:11, Michel Dänzer wrote: > On 2017-12-07 10:35 AM, Xinliang Liu wrote: >> Hi, >> >> We are trying ATI HD 7470 card on arm64 platform D05 with kernel 4.1.40. >> But it failed with kernel log: >> radeon 0005:01:00: ring 0 stalled for more than 1msec >> radeon 0005:01:00: GPU lockup (current fence id 0x0001 >> last fence id 0x0002 on ring0) >> radeon 0005:01:00: ring 0 stalled for more than 10500msec >> radeon 0005:01:00: GPU lockup (current fence id 0x0001 >> last fence id 0x0002 on ring0) >> radeon 0005:01:00: ring 0 stalled for more than 11000msec >> radeon 0005:01:00: GPU lockup (current fence id 0x0001 >> last fence id 0x0002 on ring0) >> radeon 0005:01:00: ring 0 stalled for more than 11500msec >> radeon 0005:01:00: GPU lockup (current fence id 0x0001 >> last fence id 0x0002 on ring0) >> ... >> >> Any clue? > > Any chance you can try a newer kernel? Somebody else (also @huawei.com > incidentally) reported just this week on the mesa-dev mailing list that > the amdgpu driver in the Ubuntu 4.13 kernel is working on an arm64 platform. > > If a newer kernel still doesn't work on your platform, please provide > the full dmesg output. Hope we have change to try newer kernel. After tracking the mainline we had found that this commit[1] fixed this issue. The root cause is that on old kernel ttm can't succeed to set page writecombine property which make cpu/gpu in fatal status and stub. Anyway, we should use newer kernel and keep on testing. [1] f135b97 drm/ttm: recognize ARM64 arch in ioprot handler https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v4.15-rc2&id=f135b978c2dab3d439eacb8353d3c0aac6af072a > > > BTW, in the other thread it was reported that Mesa has bugs which can be > worked around by compiling it with -fsigned-char. Thanks for letting us know this. Had looked into the mesa bug. Thanks, Xinliang > > > -- > Earthling Michel Dänzer | http://www.amd.com > Libre software enthusiast | Mesa and X developer ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [Ask for help] ATI HD 7470 card on arm64 platform
Hi Christian, On 2017/12/7 17:57, Xinliang Liu wrote: cc z.liuxinli...@hisilicon.com On 7 December 2017 at 17:54, Xinliang Liu wrote: Thanks Christian, add tangyongqian in the loop. On 7 December 2017 at 17:40, Christian König wrote: Hi Xinliang, please provide the output of lspci and the content of /proc/iomem - #lspci -vt -+-[0007:40]---00.0-[41]00.0 Device 19e5:1711 +-[0006:08]---00.0-[09]00.0 Device 19e5:1710 +-[0005:00]---00.0-[01]--+-00.0 Advanced Micro Devices, Inc. [AMD/ATI] Caicos XT [Radeon HD 7470/8470 / R5 235/310 OEM] | \-00.1 Advanced Micro Devices, Inc. [AMD/ATI] Caicos HDMI Audio [Radeon HD 6400 Series] +-[0004:48]---00.0-[49]-- +-[0002:e8]---00.0-[e9]-- \-[:00]- #lspci -vvv 0002:e8:00.0 PCI bridge: Device 19e5:1610 (rev 01) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Latency: 0 Bus: primary=e8, secondary=e9, subordinate=e9, sec-latency=0 I/O behind bridge: f000-0fff Memory behind bridge: fff0-000f Prefetchable memory behind bridge: fff0-000f Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2-,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [50] MSI: Enable- Count=1/32 Maskable+ 64bit+ Address: Data: Masking: Pending: Capabilities: [70] Express (v2) Root Port (Slot-), MSI 00 DevCap: MaxPayload 512 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+ RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 512 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #0, Speed 8GT/s, Width x8, ASPM L1, Exit Latency L0s unlimited, L1 <64us ClockPM- Surprise- LLActRep+ BwNot+ LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- DevCap2: Completion Timeout: Range ABCD, TimeoutDis+, LTR+, OBFF Not Supported ARIFwd+ DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled ARIFwd- LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [100 v2] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr- CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn- Capabilities: [158 v1] #19 Capabilities: [178 v1] Transaction Processing Hints No steering table available Kernel driver in use: pcieport 0004:48:00.0 PCI bridge: Device 19e5:1610 (rev 01) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Latency: 0 Bus: primary=48, secondary=49, subordinate=49, sec-latency=0 I/O behind bridge: f000-0fff Memory behind bridge: fff0-000f Prefetchable memory behind bridge: fff0-000f Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2-,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [50] MSI: E
Re: [Ask for help] ATI HD 7470 card on arm64 platform
On 2017-12-07 10:35 AM, Xinliang Liu wrote: > Hi, > > We are trying ATI HD 7470 card on arm64 platform D05 with kernel 4.1.40. > But it failed with kernel log: > radeon 0005:01:00: ring 0 stalled for more than 1msec > radeon 0005:01:00: GPU lockup (current fence id 0x0001 > last fence id 0x0002 on ring0) > radeon 0005:01:00: ring 0 stalled for more than 10500msec > radeon 0005:01:00: GPU lockup (current fence id 0x0001 > last fence id 0x0002 on ring0) > radeon 0005:01:00: ring 0 stalled for more than 11000msec > radeon 0005:01:00: GPU lockup (current fence id 0x0001 > last fence id 0x0002 on ring0) > radeon 0005:01:00: ring 0 stalled for more than 11500msec > radeon 0005:01:00: GPU lockup (current fence id 0x0001 > last fence id 0x0002 on ring0) > ... > > Any clue? Any chance you can try a newer kernel? Somebody else (also @huawei.com incidentally) reported just this week on the mesa-dev mailing list that the amdgpu driver in the Ubuntu 4.13 kernel is working on an arm64 platform. If a newer kernel still doesn't work on your platform, please provide the full dmesg output. BTW, in the other thread it was reported that Mesa has bugs which can be worked around by compiling it with -fsigned-char. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [Ask for help] ATI HD 7470 card on arm64 platform
cc z.liuxinli...@hisilicon.com On 7 December 2017 at 17:54, Xinliang Liu wrote: > Thanks Christian, > > add tangyongqian in the loop. > > On 7 December 2017 at 17:40, Christian König wrote: >> Hi Xinliang, >> >> please provide the output of lspci and the content of /proc/iomem > > will privide these info asap. > > > >> >> Thanks, >> Christian. >> >> >> Am 07.12.2017 um 10:35 schrieb Xinliang Liu: >>> >>> Hi, >>> >>> We are trying ATI HD 7470 card on arm64 platform D05 with kernel 4.1.40. >>> But it failed with kernel log: >>> radeon 0005:01:00: ring 0 stalled for more than 1msec >>> radeon 0005:01:00: GPU lockup (current fence id 0x0001 >>> last fence id 0x0002 on ring0) >>> radeon 0005:01:00: ring 0 stalled for more than 10500msec >>> radeon 0005:01:00: GPU lockup (current fence id 0x0001 >>> last fence id 0x0002 on ring0) >>> radeon 0005:01:00: ring 0 stalled for more than 11000msec >>> radeon 0005:01:00: GPU lockup (current fence id 0x0001 >>> last fence id 0x0002 on ring0) >>> radeon 0005:01:00: ring 0 stalled for more than 11500msec >>> radeon 0005:01:00: GPU lockup (current fence id 0x0001 >>> last fence id 0x0002 on ring0) >>> ... >>> >>> Any clue? >>> Any required setting on BIOS IO mem bar video ram? It seems that our >>> PCIE controller doesn't support cacheable feature for IO mem bar video >>> ram. >>> >>> >>> Best, >>> Xinliang >> >> ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [Ask for help] ATI HD 7470 card on arm64 platform
Thanks Christian, add tangyongqian in the loop. On 7 December 2017 at 17:40, Christian König wrote: > Hi Xinliang, > > please provide the output of lspci and the content of /proc/iomem will privide these info asap. > > Thanks, > Christian. > > > Am 07.12.2017 um 10:35 schrieb Xinliang Liu: >> >> Hi, >> >> We are trying ATI HD 7470 card on arm64 platform D05 with kernel 4.1.40. >> But it failed with kernel log: >> radeon 0005:01:00: ring 0 stalled for more than 1msec >> radeon 0005:01:00: GPU lockup (current fence id 0x0001 >> last fence id 0x0002 on ring0) >> radeon 0005:01:00: ring 0 stalled for more than 10500msec >> radeon 0005:01:00: GPU lockup (current fence id 0x0001 >> last fence id 0x0002 on ring0) >> radeon 0005:01:00: ring 0 stalled for more than 11000msec >> radeon 0005:01:00: GPU lockup (current fence id 0x0001 >> last fence id 0x0002 on ring0) >> radeon 0005:01:00: ring 0 stalled for more than 11500msec >> radeon 0005:01:00: GPU lockup (current fence id 0x0001 >> last fence id 0x0002 on ring0) >> ... >> >> Any clue? >> Any required setting on BIOS IO mem bar video ram? It seems that our >> PCIE controller doesn't support cacheable feature for IO mem bar video >> ram. >> >> >> Best, >> Xinliang > > ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [Ask for help] ATI HD 7470 card on arm64 platform
Hi Xinliang, please provide the output of lspci and the content of /proc/iomem Thanks, Christian. Am 07.12.2017 um 10:35 schrieb Xinliang Liu: Hi, We are trying ATI HD 7470 card on arm64 platform D05 with kernel 4.1.40. But it failed with kernel log: radeon 0005:01:00: ring 0 stalled for more than 1msec radeon 0005:01:00: GPU lockup (current fence id 0x0001 last fence id 0x0002 on ring0) radeon 0005:01:00: ring 0 stalled for more than 10500msec radeon 0005:01:00: GPU lockup (current fence id 0x0001 last fence id 0x0002 on ring0) radeon 0005:01:00: ring 0 stalled for more than 11000msec radeon 0005:01:00: GPU lockup (current fence id 0x0001 last fence id 0x0002 on ring0) radeon 0005:01:00: ring 0 stalled for more than 11500msec radeon 0005:01:00: GPU lockup (current fence id 0x0001 last fence id 0x0002 on ring0) ... Any clue? Any required setting on BIOS IO mem bar video ram? It seems that our PCIE controller doesn't support cacheable feature for IO mem bar video ram. Best, Xinliang ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Ask for help] ATI HD 7470 card on arm64 platform
Hi, We are trying ATI HD 7470 card on arm64 platform D05 with kernel 4.1.40. But it failed with kernel log: radeon 0005:01:00: ring 0 stalled for more than 1msec radeon 0005:01:00: GPU lockup (current fence id 0x0001 last fence id 0x0002 on ring0) radeon 0005:01:00: ring 0 stalled for more than 10500msec radeon 0005:01:00: GPU lockup (current fence id 0x0001 last fence id 0x0002 on ring0) radeon 0005:01:00: ring 0 stalled for more than 11000msec radeon 0005:01:00: GPU lockup (current fence id 0x0001 last fence id 0x0002 on ring0) radeon 0005:01:00: ring 0 stalled for more than 11500msec radeon 0005:01:00: GPU lockup (current fence id 0x0001 last fence id 0x0002 on ring0) ... Any clue? Any required setting on BIOS IO mem bar video ram? It seems that our PCIE controller doesn't support cacheable feature for IO mem bar video ram. Best, Xinliang ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
