[systemd-bugs] [Bug 77246] New: dual-gpu (vgaswitcheroo) laptop doesn't suspend when lid closed

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Apr 9 10:25:58 PDT 2014


https://bugs.freedesktop.org/show_bug.cgi?id=77246

          Priority: medium
            Bug ID: 77246
          Assignee: systemd-bugs at lists.freedesktop.org
           Summary: dual-gpu (vgaswitcheroo) laptop doesn't suspend when
                    lid closed
        QA Contact: systemd-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: mt-ml at gmx.de
          Hardware: Other
            Status: NEW
           Version: unspecified
         Component: general
           Product: systemd

I'm seeing the same symptoms on my laptop as in
https://bugs.freedesktop.org/show_bug.cgi?id=76267 : closing the lid doesn't
suspend while the suspend button does, but, as I understand, the cause is a
different one so new bug. Please mark as duplicate if I was wrong ;)

In the logs I see this (with SYSTEMD_LOG_LEVEL=debug for logind):
systemd-logind[4178]: Lid closed.
systemd-logind[4178]: Ignoring lid switch request, 2 displays connected.

However there is only one (the integrated) display.

The laptop has two gpus using vgaswitcheroo, an intel igp and a radeon
dedicated gpu, both are working with the free drivers. And both connectors

/sys/class/drm/card0-LVDS-1/status (the igp, actually in use)

and

/sys/class/drm/card1-LVDS-2/status (the radeon gpu, dynamically powered off)

show "connected", so src/login/logind-core.c:manager_count_displays() returns
2.

Is the kernel supposed to advertise two connectors as connected in this case
even though there's only one display? If so, what is a better way to recognize
the actual number of displays connected?

Thanks
Mirco

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20140409/ad13a1c3/attachment-0001.html>


More information about the systemd-bugs mailing list