From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102048] Radeon module takes over two seconds to initialize on a Radeon HD 8470D (Richland)
Date: Sat, 05 Aug 2017 13:18:22 +0000 [thread overview]
Message-ID: <bug-102048-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1170 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=102048
Bug ID: 102048
Summary: Radeon module takes over two seconds to initialize on
a Radeon HD 8470D (Richland)
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel@lists.freedesktop.org
Reporter: paulepanter@users.sourceforge.net
Created attachment 133255
--> https://bugs.freedesktop.org/attachment.cgi?id=133255&action=edit
Output of `dmesg`
Starting Linux with `initcall_debug` shows that the radeon module takes over
two seconds to load on a Asus F2A85-M PRO.
```
initcall radeon_init+0x0/0xaf [radeon] returned 0 after 2278773 usecs
```
```
$ lspci -s 0:01.0 -nn
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Richland [Radeon HD 8470D] [1002:9996]
```
Please find the Linux messages captured by running `dmesg` attached.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2605 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 reply other threads:[~2017-08-05 13:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-05 13:18 bugzilla-daemon [this message]
2017-08-06 11:37 ` [Bug 102048] Radeon module takes over two seconds to initialize on a Radeon HD 8470D (Richland) bugzilla-daemon
2017-08-07 11:58 ` 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-102048-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.