From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 112008] eDP -> Dual Channel LVDS bridge unable to accept any modelines: Corrupt display!
Date: Tue, 15 Oct 2019 19:56:59 +0000 [thread overview]
Message-ID: <bug-112008-502-UpMAfWOVar@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-112008-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1386 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=112008
--- Comment #5 from Babblebones@gmail.com ---
(In reply to Alex Deucher from comment #4)
> Can you use git bisect the issue and find the exact commit that broke it or
> narrow down when the regression happened? E.g., working in 4.17-rc3 and
> broken in 4.17-rc4?
I have two commits that break my EDID reading and cause the exact same issue so
far.
bisected the mainline to try and find the issue, trailed into your drm-next
git...
The first commit I found that broke my EDID read:
https://cgit.freedesktop.org/~agd5f/linux/commit/?h=amd-staging-drm-next&id=8a61bc085ffab3071c59efcbeff4044c034e7490
Was later reverted.
Followed more commits after this one down a branch and into here...
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=x86-urgent-for-linus&id=bd4caed47a19f25fe8674344ea06d469c27ac314
Surprisingly, swapping out the memory allocs actually breaks the EDID read in
this commit/ branch too. I know for a fact Ubuntu's old kernel 4.18 reverted
this specific and the treewide memory allocation change, which worked!? I
stopped about here, my head was starting to spin as to why THAT would do
anything.
I am ready and able to fork over any binary/parameter/debug dumps to help solve
this.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2594 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-10-15 19:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 2:52 [Bug 112008] eDP -> Dual Channel LVDS bridge unable to accept any modelines: Corrupt display! bugzilla-daemon
2019-10-15 2:54 ` bugzilla-daemon
2019-10-15 3:23 ` bugzilla-daemon
2019-10-15 3:24 ` bugzilla-daemon
2019-10-15 3:25 ` bugzilla-daemon
2019-10-15 14:30 ` bugzilla-daemon
2019-10-15 19:56 ` bugzilla-daemon [this message]
2019-10-21 23:46 ` bugzilla-daemon
2019-11-09 15:41 ` bugzilla-daemon
2019-11-19 9:58 ` 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-112008-502-UpMAfWOVar@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