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 102800] DRI_PRIME regression- radeon: Failed to allocate virtual address for buffer
Date: Fri, 15 Sep 2017 20:16:00 +0000	[thread overview]
Message-ID: <bug-102800-502-4WR96EEpoe@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-102800-502@http.bugs.freedesktop.org/>


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

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

--- Comment #2 from higuita@gmx.net ---
Sorry, radeon.runpm=0 does not work too, the card was powered off, so it was
using Intel card

Enabling the dedicated card still fails with the same error.

the dmesg show this when enabling the card:

[  180.869486] radeon: switched on
[  180.898877] [drm] probing gen 2 caps for device 8086:9c18 = 5323c42/0
[  180.898881] [drm] PCIE gen 2 link speeds already enabled
[  180.905022] [drm] PCIE GART of 2048M enabled (table at 0x0000000000040000).
[  180.905150] radeon 0000:06:00.0: WB enabled
[  180.905154] radeon 0000:06:00.0: fence driver on ring 0 use gpu addr
0x0000000080000c00 and cpu addr 0xffff891099a99c00
[  180.905155] radeon 0000:06:00.0: fence driver on ring 1 use gpu addr
0x0000000080000c04 and cpu addr 0xffff891099a99c04
[  180.905157] radeon 0000:06:00.0: fence driver on ring 2 use gpu addr
0x0000000080000c08 and cpu addr 0xffff891099a99c08
[  180.905158] radeon 0000:06:00.0: fence driver on ring 3 use gpu addr
0x0000000080000c0c and cpu addr 0xffff891099a99c0c
[  180.905159] radeon 0000:06:00.0: fence driver on ring 4 use gpu addr
0x0000000080000c10 and cpu addr 0xffff891099a99c10
[  181.613461] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed
(scratch(0x850C)=0xCAFEDEAD)
[  181.613478] [drm:si_resume [radeon]] *ERROR* si startup failed on resume

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

[-- Attachment #1.2: Type: text/html, Size: 2302 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:[~2017-09-15 20:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-15 20:01 [Bug 102800] DRI_PRIME regression- radeon: Failed to allocate virtual address for buffer bugzilla-daemon
2017-09-15 20:08 ` bugzilla-daemon
2017-09-15 20:16 ` bugzilla-daemon [this message]
2017-09-15 20:29 ` bugzilla-daemon
2017-09-15 20:30 ` bugzilla-daemon
2017-09-15 20:30 ` bugzilla-daemon
2017-10-04 15:58 ` bugzilla-daemon
2017-10-09 23:18 ` bugzilla-daemon
2017-10-10 13:21 ` bugzilla-daemon
2017-10-10 13:25 ` bugzilla-daemon
2017-10-10 23:50 ` bugzilla-daemon
2017-11-06  3:38 ` bugzilla-daemon
2017-11-13 20:12 ` bugzilla-daemon
2017-11-13 21:02 ` bugzilla-daemon
2017-11-17  2:04 ` bugzilla-daemon
2017-11-21 23:40 ` bugzilla-daemon
2017-11-24 22:22 ` bugzilla-daemon
2017-12-19  4:16 ` bugzilla-daemon
2018-01-11 23:14 ` bugzilla-daemon
2018-01-12 16:22 ` bugzilla-daemon
2018-01-17 18:21 ` bugzilla-daemon
2019-11-19  9:30 ` 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-102800-502-4WR96EEpoe@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