All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102497] Fatal error during GPU init when using an aarch64 board
Date: Thu, 31 Aug 2017 20:03:36 +0000	[thread overview]
Message-ID: <bug-102497-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 102497
           Summary: Fatal error during GPU init when using an aarch64
                    board
           Product: DRI
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Radeon
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: bero@lindev.ch

Putting a Radeon graphics card into the PCI slot of an Aarch64 board (the
particular one I tried is the Solidrun MACCHIATObin) results in:

[Wed Jul 12 14:01:10 2017] [drm] Initialized drm 1.1.0 20060810
[Wed Jul 12 14:01:10 2017] [drm] radeon kernel modesetting enabled.
[Wed Jul 12 14:01:10 2017] [drm] initializing kernel modesetting (RV620
0x1002:0x95C5 0x174B:0xE400).
[Wed Jul 12 14:01:10 2017] [drm] register mmio base: 0xF6120000
[Wed Jul 12 14:01:10 2017] [drm] register mmio size: 65536
[Wed Jul 12 14:01:10 2017] ATOM BIOS: 
[Wed Jul 12 14:01:10 2017] [drm] GPU not posted. posting now...
[Wed Jul 12 14:01:10 2017] radeon 0000:01:00.0: VRAM: 512M 0x0000000000000000 -
0x000000001FFFFFFF (512M used)
[Wed Jul 12 14:01:10 2017] radeon 0000:01:00.0: GTT: 512M 0x0000000020000000 -
0x000000003FFFFFFF
[Wed Jul 12 14:01:10 2017] [drm] Detected VRAM RAM=512M, BAR=0M
[Wed Jul 12 14:01:10 2017] [drm] RAM width 64bits DDR
[Wed Jul 12 14:01:10 2017] [TTM] Zone  kernel: Available graphics memory:
1889730 kiB
[Wed Jul 12 14:01:10 2017] [TTM] Initializing pool allocator
[Wed Jul 12 14:01:10 2017] [TTM] Initializing DMA pool allocator
[Wed Jul 12 14:01:10 2017] radeon 0000:01:00.0: Fatal error during GPU init
[Wed Jul 12 14:01:10 2017] [drm] radeon: finishing device.
[Wed Jul 12 14:01:10 2017] [TTM] Trying to take down uninitialized memory
manager type 1
[Wed Jul 12 14:01:10 2017] [TTM] Finalizing pool allocator
[Wed Jul 12 14:01:10 2017] [TTM] Finalizing DMA pool allocator
[Wed Jul 12 14:01:10 2017] [TTM] Zone  kernel: Used memory at exit: 0 kiB
[Wed Jul 12 14:01:10 2017] [drm] radeon: ttm finalized
[Wed Jul 12 14:01:10 2017] radeon: probe of 0000:01:00.0 failed with error -12

I've tried 3 different radeon cards:

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV620
LE [Radeon HD 3450]

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
RV710/M92 [Mobility Radeon HD 4530/4570/545v]

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
RV530LE [Radeon X1600/X1650 PRO]

All behave the exact same.

I presume the problem is caused by the (lack of) BIOS on aarch64 boards not
initializing the GPU the same way an x86 box does.

This is on kernel 4.4.52 (latest kernel supported by the board; could try
pulling DRI patches from newer kernels if there's any hope of changes being
there already), libdrm 2.4.82

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

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

             reply	other threads:[~2017-08-31 20:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-31 20:03 bugzilla-daemon [this message]
2017-08-31 20:10 ` [Bug 102497] Fatal error during GPU init when using an aarch64 board bugzilla-daemon
2018-08-02 17:59 ` 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-102497-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.