From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100891] failed to send pre message kernel output delays booting/suspending/resuming
Date: Mon, 30 Apr 2018 15:00:00 +0000 [thread overview]
Message-ID: <bug-100891-502-gp6GaTwfrV@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100891-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1591 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100891
--- Comment #5 from MichaelLong <harn-solo@gmx.de> ---
Update:
>From time to time I'm testing this card with newer kernels along with the most
recent set of firmware files. The only difference I was able to observe is that
the amount of debug messages is less and less with every new kernel. With
kernel 4.9 there were so many debug messages emitted that the monitor was in
standby for more than 10min, now e.g. with 4.17-rc3 there only a few messages
(see newer dmesg output), hardly noticeable.
Unfortunately the result remains the same: Shortly after booting, the GPU
temperature is rising constantly, the fans are not starting to spin. My guess
is that eventually the card will overheat or go into some sort of emergency
mode. I was always shutting down earlier.
In the meantime I was also able to test the card in a few other PC systems.
Interestingly the card is working there without any of the above mentioned
issues.
The affected mainboard I'm trying to use the card with is an ASUS X99-E WS 3.1
(https://www.asus.com/Commercial-Servers-Workstations/X99E_WSUSB_31/).
Other cards are running fine. Right now I'm using a 'VGA compatible controller:
Advanced Micro Devices, Inc. [AMD/ATI] Caicos XT [Radeon HD 7470/8470 / R5
235/310 OEM]' without problems.
In the current state this R9 380X is unusable for me. Please let me know if
there is any chance to get this fixed. I'm happy to test out any patches if
needed.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2504 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 prev parent reply other threads:[~2018-04-30 15:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-30 15:40 [Bug 100891] failed to send pre message kernel output delays booting/suspending/resuming bugzilla-daemon
2017-04-30 15:41 ` bugzilla-daemon
2017-05-01 8:41 ` bugzilla-daemon
2017-05-01 8:42 ` bugzilla-daemon
2017-05-14 15:55 ` bugzilla-daemon
2018-04-30 15:00 ` bugzilla-daemon [this message]
2018-04-30 15:00 ` bugzilla-daemon
2018-04-30 15:02 ` bugzilla-daemon
2018-08-22 9:37 ` bugzilla-daemon
2018-10-01 12:12 ` bugzilla-daemon
2019-11-19 8:15 ` 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-100891-502-gp6GaTwfrV@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