All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 215584] New: ASUS laptop cannot suspend with external USB-C monitor
Date: Wed, 09 Feb 2022 07:58:58 +0000	[thread overview]
Message-ID: <bug-215584-215701@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=215584

            Bug ID: 215584
           Summary: ASUS laptop cannot suspend with external USB-C monitor
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.15.21
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Platform_x86
          Assignee: drivers_platform_x86@kernel-bugs.osdl.org
          Reporter: william.a.wall.4@gmail.com
        Regression: No

Created attachment 300421
  --> https://bugzilla.kernel.org/attachment.cgi?id=300421&action=edit
journalctl -b -k

I have an ASUS TUF Gaming A15 FA506QE_TUF506QE/FA506QE laptop. On kernel
5.15.21, it suspends just fine when using only the laptop. However, when
connected to an LG 43UD79-B monitor via USB-C (monitor supports DisplayPort
1.2), it wakes up almost immediately after suspend.

fwts s3 claims that this is due to:

kernel: asus_wmi: Unknown key c0 pressed

(and that log does not occur when suspending without the external monitor).

I also attempted this on a 5.16 kernel, but I was unable to get the nvidia
drivers compiled via DKMS and therefore it was not a similar test, as I am
fairly sure that the integrated graphics are not capable of driving the
external monitor.

Is there a way to configure the system to ignore that keypress? I was unable to
recreate it by mashing every possible combination of function keys I could
think of while running showkey.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

                 reply	other threads:[~2022-02-09  7:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-215584-215701@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=platform-driver-x86@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 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.