Bug 79895 - Google Hangout crashes radeon
Summary: Google Hangout crashes radeon
Status: RESOLVED INVALID
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/radeonsi (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact: Default DRI bug account
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-10 20:15 UTC by darkbasic
Modified: 2018-04-02 11:06 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description darkbasic 2014-06-10 20:15:32 UTC
Kernel 3.15.0-rc8 + PTE patches

[380782.919272] Watchdog[21745]: segfault at 0 ip 00007f405eb822b8 sp 00007f404b8b9850 error 6 in chrome[7f405afc6000+5807000]
[380783.427655] radeon 0000:01:00.0: ring 0 stalled for more than 11720msec
[380783.427659] radeon 0000:01:00.0: GPU lockup (waiting for 0x00000000006e62e5 last fence id 0x00000000006e62e4 on ring 0)
[380783.427662] radeon 0000:01:00.0: failed to get a new IB (-35)
[380783.852997] radeon 0000:01:00.0: Saved 240 dwords of commands on ring 0.
[380783.853042] radeon 0000:01:00.0: GPU softreset: 0x0000006C
[380783.853043] radeon 0000:01:00.0:   GRBM_STATUS               = 0xA0003028
[380783.853044] radeon 0000:01:00.0:   GRBM_STATUS_SE0           = 0x00000006
[380783.853045] radeon 0000:01:00.0:   GRBM_STATUS_SE1           = 0x00000006
[380783.853046] radeon 0000:01:00.0:   SRBM_STATUS               = 0x200000C0
[380783.853080] radeon 0000:01:00.0:   SRBM_STATUS2              = 0x00000000
[380783.853082] radeon 0000:01:00.0:   R_008674_CP_STALLED_STAT1 = 0x00000000
[380783.853083] radeon 0000:01:00.0:   R_008678_CP_STALLED_STAT2 = 0x00010000
[380783.853084] radeon 0000:01:00.0:   R_00867C_CP_BUSY_STAT     = 0x00000002
[380783.853085] radeon 0000:01:00.0:   R_008680_CP_STAT          = 0x80010243
[380783.853086] radeon 0000:01:00.0:   R_00D034_DMA_STATUS_REG   = 0x44483106
[380783.853087] radeon 0000:01:00.0:   R_00D834_DMA_STATUS_REG   = 0x44C84246
[380783.853089] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00000000
[380783.853090] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000
[380784.261939] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x0000DDFF
[380784.261993] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00100140
[380784.263140] radeon 0000:01:00.0:   GRBM_STATUS               = 0x00003028
[380784.263141] radeon 0000:01:00.0:   GRBM_STATUS_SE0           = 0x00000006
[380784.263142] radeon 0000:01:00.0:   GRBM_STATUS_SE1           = 0x00000006
[380784.263143] radeon 0000:01:00.0:   SRBM_STATUS               = 0x200000C0
[380784.263177] radeon 0000:01:00.0:   SRBM_STATUS2              = 0x00000000
[380784.263178] radeon 0000:01:00.0:   R_008674_CP_STALLED_STAT1 = 0x00000000
[380784.263180] radeon 0000:01:00.0:   R_008678_CP_STALLED_STAT2 = 0x00000000
[380784.263181] radeon 0000:01:00.0:   R_00867C_CP_BUSY_STAT     = 0x00000000
[380784.263182] radeon 0000:01:00.0:   R_008680_CP_STAT          = 0x00000000
[380784.263183] radeon 0000:01:00.0:   R_00D034_DMA_STATUS_REG   = 0x44C83D57
[380784.263184] radeon 0000:01:00.0:   R_00D834_DMA_STATUS_REG   = 0x44C83D57
[380784.263261] radeon 0000:01:00.0: GPU reset succeeded, trying to resume
[380784.301675] [drm] probing gen 2 caps for device 8086:151 = 261ad03/e
[380784.301678] [drm] PCIE gen 3 link speeds already enabled
[380784.303658] [drm] PCIE GART of 1024M enabled (table at 0x0000000000276000).
[380784.303740] radeon 0000:01:00.0: WB enabled
[380784.303742] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x00000000c0000c00 and cpu addr 0xffff880417946c00
[380784.303743] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x00000000c0000c04 and cpu addr 0xffff880417946c04
[380784.303744] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x00000000c0000c08 and cpu addr 0xffff880417946c08
[380784.303745] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x00000000c0000c0c and cpu addr 0xffff880417946c0c
[380784.303746] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x00000000c0000c10 and cpu addr 0xffff880417946c10
[380784.304140] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90006135a18
[380784.625264] [drm:r600_ring_test] *ERROR* radeon: ring 0 test failed (scratch(0x850C)=0xCAFEDEAD)
[380784.625268] [drm:si_resume] *ERROR* si startup failed on resume
[380784.625304] [drm:radeon_pm_resume_dpm] *ERROR* radeon: dpm resume failed
[380784.625374] switching from power state:
[380784.625376]         ui class: none
[380784.625377]         internal class: boot 
[380784.625378]         caps: 
[380784.625379]         uvd    vclk: 0 dclk: 0
[380784.625380]                 power level 0    sclk: 50000 mclk: 15000 vddc: 950 vddci: 875 pcie gen: 3
[380784.625381]         status: c b 
[380784.625382] switching to power state:
[380784.625383]         ui class: performance
[380784.625384]         internal class: none
[380784.625385]         caps: 
[380784.625386]         uvd    vclk: 0 dclk: 0
[380784.625387]                 power level 0    sclk: 30000 mclk: 15000 vddc: 850 vddci: 875 pcie gen: 3
[380784.625388]                 power level 1    sclk: 50100 mclk: 125000 vddc: 950 vddci: 875 pcie gen: 3
[380784.625390]                 power level 2    sclk: 81000 mclk: 125000 vddc: 1090 vddci: 875 pcie gen: 3
[380784.625390]         status: r
Comment 1 Michel Dänzer 2014-06-11 03:09:19 UTC
Please provide more details how to reproduce the problem: How exactly are you using Hangouts when this happens?
Comment 2 darkbasic 2014-06-11 09:36:50 UTC
I'm just doing a videoconference with another people: sooner or later it crashes. google-talkplugin version is 5.4.1.0.
Comment 3 darkbasic 2014-06-13 13:07:41 UTC
Maybe it has something to do with this:
https://bugs.freedesktop.org/show_bug.cgi?id=79980
Comment 4 Oded Gabbay 2016-05-24 14:15:08 UTC
Does this still happens to you ?
Comment 5 darkbasic 2016-05-24 15:32:59 UTC
I can't test it ATM because my Gentoo desktop needs to be fixed after some LTO/graphite tests and I don't use it since a couple of months. I will probably find some time to fix it in the next couple of months, but I'm using ony my Broadwell laptop right now. I hope Zen will be up to expectations because Intel driver is so fucking damn bugged that I can't tollerate it anymore.
Comment 6 darkbasic 2016-05-24 15:34:34 UTC
P.S.
Maybe we should simply close it considering how old this bug report is and not being able to test it: it has probably already being fixed.
Comment 7 Timothy Arceri 2018-04-02 11:06:39 UTC
Original bug reporter unable to reproduce. Closing.


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.