From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 94874] radeon: Failed to allocate virtual address for buffer
Date: Fri, 08 Apr 2016 23:35:01 +0000 [thread overview]
Message-ID: <bug-94874-502-ZoJWxam7Eg@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-94874-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 4267 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=94874
--- Comment #4 from Paulo Dias <paulo.miguel.dias@gmail.com> ---
Abr 08 20:33:29 hydra kernel: [drm] probing gen 2 caps for device 8086:9c18 =
5323c42/0
Abr 08 20:33:29 hydra kernel: [drm] enabling PCIE gen 2 link speeds, disable
with radeon.pcie_gen2=0
Abr 08 20:33:29 hydra kernel: radeon 0000:03:00.0: Wait for MC idle timedout !
Abr 08 20:33:29 hydra kernel: radeon 0000:03:00.0: Wait for MC idle timedout !
Abr 08 20:33:29 hydra kernel: [drm] PCIE GART of 2048M enabled (table at
0x00000000002E8000).
Abr 08 20:33:29 hydra kernel: radeon 0000:03:00.0: WB enabled
Abr 08 20:33:29 hydra kernel: radeon 0000:03:00.0: fence driver on ring 0 use
gpu addr 0x0000000080000c00 and cpu addr 0xffff8801a332cc00
Abr 08 20:33:29 hydra kernel: radeon 0000:03:00.0: fence driver on ring 1 use
gpu addr 0x0000000080000c04 and cpu addr 0xffff8801a332cc04
Abr 08 20:33:29 hydra kernel: radeon 0000:03:00.0: fence driver on ring 2 use
gpu addr 0x0000000080000c08 and cpu addr 0xffff8801a332cc08
Abr 08 20:33:29 hydra kernel: radeon 0000:03:00.0: fence driver on ring 3 use
gpu addr 0x0000000080000c0c and cpu addr 0xffff8801a332cc0c
Abr 08 20:33:29 hydra kernel: radeon 0000:03:00.0: fence driver on ring 4 use
gpu addr 0x0000000080000c10 and cpu addr 0xffff8801a332cc10
Abr 08 20:33:29 hydra kernel: radeon 0000:03:00.0: fence driver on ring 5 use
gpu addr 0x0000000000075a18 and cpu addr 0xffffc90001435a18
Abr 08 20:33:29 hydra kernel: radeon 0000:03:00.0: VCE init error (-110).
Abr 08 20:33:29 hydra kernel: [drm:r600_ring_test [radeon]] *ERROR* radeon:
ring 0 test failed (scratch(0x850C)=0xFFFFFFFF)
Abr 08 20:33:29 hydra kernel: [drm:si_resume [radeon]] *ERROR* si startup
failed on resume
Abr 08 20:33:29 hydra kernel: [drm:si_dpm_enable [radeon]] *ERROR*
si_init_smc_table failed
Abr 08 20:33:29 hydra kernel: [drm:radeon_pm_resume [radeon]] *ERROR* radeon:
dpm resume failed
Abr 08 20:33:29 hydra kernel: [drm:atom_op_jump [radeon]] *ERROR* atombios
stuck in loop for more than 5secs aborting
Abr 08 20:33:29 hydra kernel: [drm:atom_execute_table_locked [radeon]] *ERROR*
atombios stuck executing CFA0 (len 62, WS 0, PS 0) @ 0xCFBC
Abr 08 20:33:29 hydra kernel: [drm:atom_op_jump [radeon]] *ERROR* atombios
stuck in loop for more than 5secs aborting
Abr 08 20:33:29 hydra kernel: [drm:atom_execute_table_locked [radeon]] *ERROR*
atombios stuck executing CFA0 (len 62, WS 0, PS 0) @ 0xCFBC
Abr 08 20:33:29 hydra kernel: [drm:atom_op_jump [radeon]] *ERROR* atombios
stuck in loop for more than 5secs aborting
Abr 08 20:33:29 hydra kernel: [drm:atom_execute_table_locked [radeon]] *ERROR*
atombios stuck executing CFA0 (len 62, WS 0, PS 0) @ 0xCFBC
Abr 08 20:33:29 hydra kernel: [drm:atom_op_jump [radeon]] *ERROR* atombios
stuck in loop for more than 5secs aborting
Abr 08 20:33:29 hydra kernel: [drm:atom_execute_table_locked [radeon]] *ERROR*
atombios stuck executing CFA0 (len 62, WS 0, PS 0) @ 0xCFBC
Abr 08 20:33:29 hydra kernel: [drm:atom_op_jump [radeon]] *ERROR* atombios
stuck in loop for more than 5secs aborting
Abr 08 20:33:29 hydra kernel: [drm:atom_execute_table_locked [radeon]] *ERROR*
atombios stuck executing CFA0 (len 62, WS 0, PS 0) @ 0xCFBC
Abr 08 20:33:29 hydra kernel: [drm:atom_op_jump [radeon]] *ERROR* atombios
stuck in loop for more than 5secs aborting
Abr 08 20:33:29 hydra kernel: [drm:atom_execute_table_locked [radeon]] *ERROR*
atombios stuck executing CFA0 (len 62, WS 0, PS 0) @ 0xCFBC
Abr 08 20:33:42 hydra kernel: [drm:atom_op_jump [radeon]] *ERROR* atombios
stuck in loop for more than 5secs aborting
Abr 08 20:33:42 hydra kernel: [drm:atom_execute_table_locked [radeon]] *ERROR*
atombios stuck executing C810 (len 320, WS 0, PS 0) @ 0xC937
Abr 08 20:33:42 hydra kernel: [drm:atom_execute_table_locked [radeon]] *ERROR*
atombios stuck executing BAF6 (len 231, WS 4, PS 0) @ 0xBBBC
Abr 08 20:33:42 hydra kernel: [drm:atom_execute_table_locked [radeon]] *ERROR*
atombios stuck executing BA44 (len 90, WS 0, PS 8) @ 0xBA4C
Abr 08 20:33:42 hydra kernel: [drm:si_dpm_enable [radeon]] *ERROR*
si_init_smc_table failed
Abr 08 20:33:42 hydra kernel: [drm:radeon_pm_resume [radeon]] *ERROR* radeon:
dpm resume failed
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 5082 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-04-08 23:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 20:07 [Bug 94874] radeon: Failed to allocate virtual address for buffer bugzilla-daemon
2016-04-08 20:10 ` bugzilla-daemon
2016-04-08 21:24 ` bugzilla-daemon
2016-04-08 21:25 ` bugzilla-daemon
2016-04-08 23:35 ` bugzilla-daemon [this message]
2016-04-15 16:40 ` bugzilla-daemon
2016-04-17 1:55 ` bugzilla-daemon
2016-04-19 6:22 ` bugzilla-daemon
2016-04-20 2:52 ` bugzilla-daemon
2016-04-20 2:52 ` bugzilla-daemon
2016-04-20 2:53 ` bugzilla-daemon
2016-04-20 2:54 ` bugzilla-daemon
2016-04-20 2:57 ` bugzilla-daemon
2016-04-20 3:05 ` bugzilla-daemon
2016-04-20 3:14 ` bugzilla-daemon
2016-04-20 3:14 ` bugzilla-daemon
2016-04-25 17:18 ` bugzilla-daemon
2016-04-25 17:26 ` 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-94874-502-ZoJWxam7Eg@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox