dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Nick Bowler <nbowler@draconx.ca>
To: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: PROBLEM: Asus C201 video mode problems on HDMI hotplug (regression)
Date: Thu, 2 Nov 2017 01:16:58 -0400	[thread overview]
Message-ID: <CADyTPEyatxOS0z3-4fapUiuxhPsp0985YcQvgFvdp_Pesm1idg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1800 bytes --]

Hi,

On my Asus C201 laptop (rk3288) the HDMI has been behaving weirdly after
Linux upgrade.

~50% of the time after a hotplug, there is a vertical pink bar on the
left of the display area and audio is not working at all.  According to
the sink device the display size is 1282x720 which seems pretty wrong
(normal and working situation is 1280x720).

I posted photos of non-working versus working states here:

  https://imgur.com/a/qhAZG

Unplugging and plugging the cable again will correct the issue (it seems
to, for the most part, alternate between working and not-working states,
although not always).  It always works on power up with the cable initially
connected.

This is a regression from 4.11, where hotplug works perfectly every time.

I attached dmesg output (gzipped) from 4.14-rc7 (I booted up and
re-plugged the cable twice, which triggered non-working state and then
back to working state -- although seems no messages are logged from
these hotplugs).

I am working to bisect this, might take a while.  Partial progress
follows...

Let me know of anything else I should try.

Thanks,
  Nick

git bisect start
# bad: [0b07194bb55ed836c2cc7c22e866b87a14681984] Linux 4.14-rc7
git bisect bad 0b07194bb55ed836c2cc7c22e866b87a14681984
# bad: [fa394784e74b918f44fca1e6a1f826cf818350d2] Linux 4.12.14
git bisect bad fa394784e74b918f44fca1e6a1f826cf818350d2
# good: [bd1a9eb6a755e1cb342725a11242251d2bfad567] Linux 4.11.12
git bisect good bd1a9eb6a755e1cb342725a11242251d2bfad567
# good: [a351e9b9fc24e982ec2f0e76379a49826036da12] Linux 4.11
git bisect good a351e9b9fc24e982ec2f0e76379a49826036da12
# bad: [8f28472a739e8e39adc6e64ee5b460df039f0e4f] Merge tag
'usb-4.12-rc1' of
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb
git bisect bad 8f28472a739e8e39adc6e64ee5b460df039f0e4f

[-- Attachment #2: aidos-4.14-rc7.log.gz --]
[-- Type: application/x-gzip, Size: 6784 bytes --]

             reply	other threads:[~2017-11-02  5:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-02  5:16 Nick Bowler [this message]
2017-11-05 16:41 ` PROBLEM: Asus C201 video mode problems on HDMI hotplug (regression) Nick Bowler
2017-11-16  6:28   ` Nick Bowler
2017-11-27  4:05     ` Archit Taneja
2017-11-27  9:00       ` Laurent Pinchart
2017-11-27 16:34         ` Nick Bowler
2017-11-28  3:30         ` Nick Bowler
2017-12-01  0:11           ` Nick Bowler
2017-12-02 17:11             ` Jose Abreu
2017-12-03  5:20               ` Nick Bowler
2017-12-04 10:04                 ` Jose Abreu
2017-12-04 18:33                   ` Nick Bowler
2017-12-05  6:18                     ` Nick Bowler
2017-12-04 19:06             ` Laurent Pinchart
2017-12-04 19:30               ` Nick Bowler
2017-12-04 19:34                 ` Laurent Pinchart
2017-12-05  3:22                   ` Nick Bowler
2017-12-05  9:41                     ` Laurent Pinchart

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=CADyTPEyatxOS0z3-4fapUiuxhPsp0985YcQvgFvdp_Pesm1idg@mail.gmail.com \
    --to=nbowler@draconx.ca \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).