| Summary: | Age of Wonders III gpu lockup | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | dawide2211 |
| Component: | Drivers/Gallium/r600 | Assignee: | Default DRI bug account <dri-devel> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Default DRI bug account <dri-devel> |
| Severity: | major | ||
| Priority: | medium | CC: | ernstp |
| Version: | 10.5 | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
Journalctl
glxinfo |
||
Created attachment 115095 [details]
glxinfo
I tried to launch the game with R600_DEBUG=nohyperz but it still crashes the gpu so I guess it's not an hyperz issue. Same here on Mesa 10.6.0-devel (git-b2e871b 2015-04-19 vivid-oibaf-ppa) and Radeon 6850. This should be the kernel log: Jun 14 16:58:36 mammut kernel: [ 2220.181720] radeon 0000:01:00.0: ring 0 stalled for more than 10203msec Jun 14 16:58:36 mammut kernel: [ 2220.181728] radeon 0000:01:00.0: GPU lockup (current fence id 0x000000000004b79c last fence id 0x000000000004b7b0 on ring 0) Jun 14 16:58:36 mammut kernel: [ 2220.199761] radeon 0000:01:00.0: Saved 626 dwords of commands on ring 0. Jun 14 16:58:36 mammut kernel: [ 2220.199795] radeon 0000:01:00.0: GPU softreset: 0x00000009 Jun 14 16:58:36 mammut kernel: [ 2220.199799] radeon 0000:01:00.0: GRBM_STATUS = 0xE7730828 Jun 14 16:58:36 mammut kernel: [ 2220.199802] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0xFC000001 Jun 14 16:58:36 mammut kernel: [ 2220.199804] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0xFC000001 Jun 14 16:58:36 mammut kernel: [ 2220.199807] radeon 0000:01:00.0: SRBM_STATUS = 0x20000AC0 Jun 14 16:58:36 mammut kernel: [ 2220.199810] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 Jun 14 16:58:36 mammut kernel: [ 2220.199813] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 Jun 14 16:58:36 mammut kernel: [ 2220.199816] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00010800 Jun 14 16:58:36 mammut kernel: [ 2220.199819] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00028006 Jun 14 16:58:36 mammut kernel: [ 2220.199822] radeon 0000:01:00.0: R_008680_CP_STAT = 0x80038647 Jun 14 16:58:36 mammut kernel: [ 2220.199825] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 Jun 14 16:58:36 mammut kernel: [ 2220.200533] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00007F6B Jun 14 16:58:36 mammut kernel: [ 2220.200588] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100 Jun 14 16:58:36 mammut kernel: [ 2220.201746] radeon 0000:01:00.0: GRBM_STATUS = 0x00003828 Jun 14 16:58:36 mammut kernel: [ 2220.201749] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000007 Jun 14 16:58:36 mammut kernel: [ 2220.201753] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 Jun 14 16:58:36 mammut kernel: [ 2220.201756] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 Jun 14 16:58:36 mammut kernel: [ 2220.201759] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 Jun 14 16:58:36 mammut kernel: [ 2220.201762] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 Jun 14 16:58:36 mammut kernel: [ 2220.201764] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 Jun 14 16:58:36 mammut kernel: [ 2220.201767] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 Jun 14 16:58:36 mammut kernel: [ 2220.201770] radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000 Jun 14 16:58:36 mammut kernel: [ 2220.201773] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 Jun 14 16:58:36 mammut kernel: [ 2220.201812] radeon 0000:01:00.0: GPU reset succeeded, trying to resume Jun 14 16:58:36 mammut kernel: [ 2220.225115] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 Jun 14 16:58:36 mammut kernel: [ 2220.227672] [drm] PCIE GART of 1024M enabled (table at 0x0000000000274000). Jun 14 16:58:36 mammut kernel: [ 2220.227775] radeon 0000:01:00.0: WB enabled Jun 14 16:58:36 mammut kernel: [ 2220.227778] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff8802217d1c00 Jun 14 16:58:36 mammut kernel: [ 2220.227781] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff8802217d1c0c Jun 14 16:58:36 mammut kernel: [ 2220.229234] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000072118 and cpu addr 0xffffc90001832118 Jun 14 16:58:36 mammut kernel: [ 2220.245682] [drm] ring test on 0 succeeded in 3 usecs Jun 14 16:58:36 mammut kernel: [ 2220.245693] [drm] ring test on 3 succeeded in 6 usecs Jun 14 16:58:36 mammut kernel: [ 2220.422650] [drm] ring test on 5 succeeded in 2 usecs Jun 14 16:58:36 mammut kernel: [ 2220.422658] [drm] UVD initialized successfully. Jun 14 16:58:36 mammut kernel: [ 2220.422823] switching from power state: Jun 14 16:58:36 mammut kernel: [ 2220.422824] ui class: none Jun 14 16:58:36 mammut kernel: [ 2220.422825] internal class: boot Jun 14 16:58:36 mammut kernel: [ 2220.422826] caps: Jun 14 16:58:36 mammut kernel: [ 2220.422827] uvd vclk: 0 dclk: 0 Jun 14 16:58:36 mammut kernel: [ 2220.422828] power level 0 sclk: 10000 mclk: 15000 vddc: 950 vddci: 950 Jun 14 16:58:36 mammut kernel: [ 2220.422829] power level 1 sclk: 10000 mclk: 15000 vddc: 950 vddci: 950 Jun 14 16:58:36 mammut kernel: [ 2220.422829] power level 2 sclk: 10000 mclk: 15000 vddc: 950 vddci: 950 Jun 14 16:58:36 mammut kernel: [ 2220.422830] status: c b Jun 14 16:58:36 mammut kernel: [ 2220.422831] switching to power state: Jun 14 16:58:36 mammut kernel: [ 2220.422831] ui class: performance Jun 14 16:58:36 mammut kernel: [ 2220.422832] internal class: none Jun 14 16:58:36 mammut kernel: [ 2220.422833] caps: Jun 14 16:58:36 mammut kernel: [ 2220.422834] uvd vclk: 0 dclk: 0 Jun 14 16:58:36 mammut kernel: [ 2220.422834] power level 0 sclk: 10000 mclk: 15000 vddc: 950 vddci: 950 Jun 14 16:58:36 mammut kernel: [ 2220.422835] power level 1 sclk: 60000 mclk: 100000 vddc: 1100 vddci: 1100 Jun 14 16:58:36 mammut kernel: [ 2220.422836] power level 2 sclk: 77500 mclk: 100000 vddc: 1150 vddci: 1100 Jun 14 16:58:36 mammut kernel: [ 2220.422836] status: r Works now! Probably http://cgit.freedesktop.org/mesa/mesa/commit/?id=97ec2c694fe568e375ec7a2b85c1acb1e4666b54 ? *** This bug has been marked as a duplicate of bug 73528 *** |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 115094 [details] Journalctl I'm using an HD6750 on Arch Linux with the latest updates. The gpu lockup when I try to start a new game. The main menu and the intro to the missions seems to work fine, the lockup happens whenever the game try start a map.