dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 21:24:07 +0000	[thread overview]
Message-ID: <bug-94874-502-nDevlwjUL0@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-94874-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 3404 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=94874

--- Comment #2 from Paulo Dias <paulo.miguel.dias@gmail.com> ---
wheni reboot, the first run works, but with errors

Abr 08 18:23:08 hydra kernel: [drm] probing gen 2 caps for device 8086:9c18 =
5323c42/0
Abr 08 18:23:08 hydra kernel: [drm] PCIE gen 2 link speeds already enabled
Abr 08 18:23:08 hydra kernel: [drm] PCIE GART of 2048M enabled (table at
0x00000000002E8000).
Abr 08 18:23:08 hydra kernel: radeon 0000:03:00.0: WB enabled
Abr 08 18:23:08 hydra kernel: radeon 0000:03:00.0: fence driver on ring 0 use
gpu addr 0x0000000080000c00 and cpu addr 0xffff8801a31c5c00
Abr 08 18:23:08 hydra kernel: radeon 0000:03:00.0: fence driver on ring 1 use
gpu addr 0x0000000080000c04 and cpu addr 0xffff8801a31c5c04
Abr 08 18:23:08 hydra kernel: radeon 0000:03:00.0: fence driver on ring 2 use
gpu addr 0x0000000080000c08 and cpu addr 0xffff8801a31c5c08
Abr 08 18:23:08 hydra kernel: radeon 0000:03:00.0: fence driver on ring 3 use
gpu addr 0x0000000080000c0c and cpu addr 0xffff8801a31c5c0c
Abr 08 18:23:08 hydra kernel: radeon 0000:03:00.0: fence driver on ring 4 use
gpu addr 0x0000000080000c10 and cpu addr 0xffff8801a31c5c10
Abr 08 18:23:08 hydra kernel: radeon 0000:03:00.0: fence driver on ring 5 use
gpu addr 0x0000000000075a18 and cpu addr 0xffffc90001435a18
Abr 08 18:23:08 hydra kernel: radeon 0000:03:00.0: VCE init error (-22).
Abr 08 18:23:09 hydra kernel: [drm] ring test on 0 succeeded in 1 usecs
Abr 08 18:23:09 hydra kernel: [drm] ring test on 1 succeeded in 1 usecs
Abr 08 18:23:09 hydra kernel: [drm] ring test on 2 succeeded in 1 usecs
Abr 08 18:23:09 hydra kernel: [drm] ring test on 3 succeeded in 10 usecs
Abr 08 18:23:09 hydra kernel: [drm] ring test on 4 succeeded in 5 usecs
Abr 08 18:23:09 hydra kernel: [drm] ring test on 5 succeeded in 2 usecs
Abr 08 18:23:09 hydra kernel: [drm] UVD initialized successfully.
Abr 08 18:23:09 hydra kernel: [drm] ib test on ring 0 succeeded in 0 usecs
Abr 08 18:23:09 hydra kernel: [drm] ib test on ring 1 succeeded in 0 usecs
Abr 08 18:23:09 hydra kernel: [drm] ib test on ring 2 succeeded in 0 usecs
Abr 08 18:23:09 hydra kernel: [drm] ib test on ring 3 succeeded in 0 usecs
Abr 08 18:23:09 hydra kernel: [drm] ib test on ring 4 succeeded in 0 usecs
Abr 08 18:23:10 hydra kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon:
fence wait timed out.
Abr 08 18:23:10 hydra kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR*
radeon: failed testing IB on ring 5 (-110).
Abr 08 18:23:10 hydra kernel: radeon 0000:03:00.0: scheduling IB failed (-12).
Abr 08 18:23:10 hydra kernel: [drm:radeon_vce_get_create_msg [radeon]] *ERROR*
radeon: failed to schedule ib (-12).
Abr 08 18:23:10 hydra kernel: [drm:radeon_vce_ib_test [radeon]] *ERROR* radeon:
failed to get create msg (-12).
Abr 08 18:23:10 hydra kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR*
radeon: failed testing IB on ring 6 (-12).
Abr 08 18:23:10 hydra kernel: radeon 0000:03:00.0: scheduling IB failed (-12).
Abr 08 18:23:10 hydra kernel: [drm:radeon_vce_get_create_msg [radeon]] *ERROR*
radeon: failed to schedule ib (-12).
Abr 08 18:23:10 hydra kernel: [drm:radeon_vce_ib_test [radeon]] *ERROR* radeon:
failed to get create msg (-12).
Abr 08 18:23:10 hydra kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR*
radeon: failed testing IB on ring 7 (-12).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 4183 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

  parent reply	other threads:[~2016-04-08 21:24 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 [this message]
2016-04-08 21:25 ` bugzilla-daemon
2016-04-08 23:35 ` bugzilla-daemon
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-nDevlwjUL0@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