touch-packages team mailing list archive

[Romain <1438301@xxxxxxxxxxxxxxxxxx>]

Here is the result of a fwts test:

lid: Interactive lid button test.
--------------------------------------------------------------------------------
Test 1 of 3: Test LID buttons report open correctly.
FAILED [HIGH] LidNotOpen: Test 1, Detected a closed LID state.

Test 2 of 3: Test LID buttons on a single open/close.
Got 4 SCI interrupt(s).
Got 4 interrupt(s) on GPE gpe17.
Got 4 interrupt(s) on GPE gpe_all.
PASSED: Test 2, Detected ACPI LID events while waiting for LID to closed.
FAILED [HIGH] NoLidState: Test 2, Could not detect lid closed state.
Got 2 SCI interrupt(s).
Got 2 interrupt(s) on GPE gpe17.
Got 2 interrupt(s) on GPE gpe_all.
PASSED: Test 2, Detected ACPI LID events while waiting for LID to open.
FAILED [HIGH] NoLidState: Test 2, Could not detect lid open state.

Test 3 of 3: Test LID buttons on multiple open/close events.
Some machines may have EC or ACPI faults that cause detection of multiple open
/close events to fail.
Got 2 SCI interrupt(s).
Got 2 interrupt(s) on GPE gpe17.
Got 2 interrupt(s) on GPE gpe_all.
PASSED: Test 3, Detected ACPI LID events while waiting for LID to closed.
FAILED [HIGH] NoLidState: Test 3, Could not detect lid closed state.
Got 2 SCI interrupt(s).
Got 2 interrupt(s) on GPE gpe17.
Got 2 interrupt(s) on GPE gpe_all.
PASSED: Test 3, Detected ACPI LID events while waiting for LID to open.
FAILED [HIGH] NoLidState: Test 3, Could not detect lid open state.
Got 2 SCI interrupt(s).
Got 2 interrupt(s) on GPE gpe17.
Got 2 interrupt(s) on GPE gpe_all.
PASSED: Test 3, Detected ACPI LID events while waiting for LID to closed.
FAILED [HIGH] NoLidState: Test 3, Could not detect lid closed state.
Got 2 SCI interrupt(s).
Got 2 interrupt(s) on GPE gpe17.
Got 2 interrupt(s) on GPE gpe_all.
PASSED: Test 3, Detected ACPI LID events while waiting for LID to open.
FAILED [HIGH] NoLidState: Test 3, Could not detect lid open state.
Got 2 SCI interrupt(s).
Got 2 interrupt(s) on GPE gpe17.
Got 2 interrupt(s) on GPE gpe_all.
PASSED: Test 3, Detected ACPI LID events while waiting for LID to closed.
FAILED [HIGH] NoLidState: Test 3, Could not detect lid closed state.
Got 2 SCI interrupt(s).
Got 2 interrupt(s) on GPE gpe17.
Got 2 interrupt(s) on GPE gpe_all.
PASSED: Test 3, Detected ACPI LID events while waiting for LID to open.
FAILED [HIGH] NoLidState: Test 3, Could not detect lid open state.

Definitively wrong LID detection, even on laptop. Digging in that
direction.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1438301

Title:
  suspends after a few minutes on machines with a bogus (closed) lid
  switch

Status in systemd package in Ubuntu:
  Won't Fix
Status in systemd source package in Vivid:
  Won't Fix

Bug description:
  On a desktop machine which claims to have a closed lid (on the
  motherboard), but doesn't actually have a lid, logind will suspend the
  machine shortly after boot as a safety measure to avoid burning your
  laptop in a bag. This is wrong in the above situation where the
  announced lid switch does not exist or isn't actually closed.

  Workaround: Set HandleLidSwitch=ignore in /etc/systemd/logind.conf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1438301/+subscriptions