From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108542] hdmi issues with kernel 4.18
Date: Thu, 25 Oct 2018 19:35:29 +0000 [thread overview]
Message-ID: <bug-108542-502-NIvK0Lmcli@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108542-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 758 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108542
--- Comment #4 from Nicholas Kazlauskas <nicholas.kazlauskas@amd.com> ---
(In reply to davide26079 from comment #3)
> (In reply to Nicholas Kazlauskas from comment #1)
> > Thanks for the bisection.
> >
> > Would you mind posting a full dmesg log for your 4.18.8 kernel?
>
> done. Dunno if that's what you asked for, I am just a newbie...
>
> I did start bisecting the second issue as well, but my free time is limited.
> I think I'll finish this weekend though.
>
> May I hope to get things fixed in a few weeks?
The log you posted should be sufficient. I'm not sure about a timeline for a
fix, however.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1664 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-10-25 19:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-24 18:22 [Bug 108542] hdmi issues with kernel 4.18 bugzilla-daemon
2018-10-25 12:52 ` bugzilla-daemon
2018-10-25 19:26 ` bugzilla-daemon
2018-10-25 19:28 ` bugzilla-daemon
2018-10-25 19:35 ` bugzilla-daemon [this message]
2018-10-27 10:47 ` bugzilla-daemon
2018-10-28 10:23 ` bugzilla-daemon
2018-10-30 16:31 ` bugzilla-daemon
2018-10-31 10:03 ` bugzilla-daemon
2018-11-20 14:07 ` bugzilla-daemon
2018-11-21 15:41 ` bugzilla-daemon
2019-11-19 9:00 ` 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-108542-502-NIvK0Lmcli@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