All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 92722] radeon 0000:01:00.0: VCE init error (-22) on Kernel >= 4.2
Date: Thu, 29 Oct 2015 07:06:22 +0000	[thread overview]
Message-ID: <bug-92722-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 92722
           Summary: radeon 0000:01:00.0: VCE init error (-22) on Kernel >=
                    4.2
           Product: Mesa
           Version: 11.0
          Hardware: Other
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: lblmr@yopmail.com
        QA Contact: dri-devel@lists.freedesktop.org

Hey guys, 

When I run any 4.2 kernel, I get this VCE init error

Oct 28 21:44:46 hosty kernel: [drm] PCIE gen 3 link speeds already enabled
Oct 28 21:44:46 hosty kernel: [drm] PCIE GART of 2048M enabled (table at
0x0000000000040000).
Oct 28 21:44:46 hosty kernel: radeon 0000:01:00.0: WB enabled
Oct 28 21:44:46 hosty kernel: radeon 0000:01:00.0: fence driver on ring 0 use
gpu addr 0x0000000080000c00 and cpu addr 0xffff88021d960c00
Oct 28 21:44:46 hosty kernel: radeon 0000:01:00.0: fence driver on ring 1 use
gpu addr 0x0000000080000c04 and cpu addr 0xffff88021d960c04
Oct 28 21:44:46 hosty kernel: radeon 0000:01:00.0: fence driver on ring 2 use
gpu addr 0x0000000080000c08 and cpu addr 0xffff88021d960c08
Oct 28 21:44:46 hosty kernel: radeon 0000:01:00.0: fence driver on ring 3 use
gpu addr 0x0000000080000c0c and cpu addr 0xffff88021d960c0c
Oct 28 21:44:46 hosty kernel: radeon 0000:01:00.0: fence driver on ring 4 use
gpu addr 0x0000000080000c10 and cpu addr 0xffff88021d960c10
Oct 28 21:44:46 hosty kernel: radeon 0000:01:00.0: VCE init error (-22).
Oct 28 21:44:46 hosty kernel: [drm] Supports vblank timestamp caching Rev 2
(21.10.2013).
Oct 28 21:44:46 hosty kernel: [drm] Driver supports precise vblank timestamp
query.
Oct 28 21:44:46 hosty kernel: radeon 0000:01:00.0: radeon: MSI limited to
32-bit
Oct 28 21:44:46 hosty kernel: radeon 0000:01:00.0: radeon: using MSI.
Oct 28 21:44:46 hosty kernel: [drm] radeon: irq initialized.


More info here: https://bugzilla.redhat.com/show_bug.cgi?id=1262649#c4

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

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

             reply	other threads:[~2015-10-29  7:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-29  7:06 bugzilla-daemon [this message]
2015-11-06 17:42 ` [Bug 92722] radeon 0000:01:00.0: VCE init error (-22) on Kernel >= 4.2 bugzilla-daemon
2015-12-24  6:29 ` bugzilla-daemon
2016-04-01 10:53 ` bugzilla-daemon
2016-04-01 10:54 ` bugzilla-daemon
2016-04-01 10:55 ` bugzilla-daemon
2016-04-04  7:54 ` bugzilla-daemon
2016-04-04 10:15 ` bugzilla-daemon
2019-11-19  9:09 ` 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-92722-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.