From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 79895] New: Google Hangout crashes radeon
Date: Tue, 10 Jun 2014 20:15:32 +0000 [thread overview]
Message-ID: <bug-79895-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 5373 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=79895
Priority: medium
Bug ID: 79895
Assignee: dri-devel@lists.freedesktop.org
Summary: Google Hangout crashes radeon
Severity: normal
Classification: Unclassified
OS: All
Reporter: darkbasic@linuxsystems.it
Hardware: Other
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
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
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 6658 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2014-06-10 20:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 20:15 bugzilla-daemon [this message]
2014-06-10 20:24 ` [Bug 79895] Google Hangout crashes radeon bugzilla-daemon
2014-06-11 3:09 ` bugzilla-daemon
2014-06-11 9:36 ` bugzilla-daemon
2014-06-13 13:07 ` bugzilla-daemon
2016-05-24 14:13 ` bugzilla-daemon
2016-05-24 14:14 ` bugzilla-daemon
2016-05-24 14:15 ` bugzilla-daemon
2016-05-24 15:32 ` bugzilla-daemon
2016-05-24 15:34 ` bugzilla-daemon
2018-04-02 11:06 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-79895-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.