Ticket #2426 (closed defect: fixed)

Opened 7 years ago

Last modified 7 years ago

Power button isn't always resuming from suspend on B4s

Reported by: jfuhrer Owned by: dilinger
Priority: blocker Milestone: Trial-3
Component: kernel Version:
Keywords: power Cc: rsmith
Action Needed: Verified: no
Deployments affected: Blocked By:
Blocking:

Description

OFW: Q2C18 Build: 530

On B3/4s, pressing the power button doesn't resume from suspend. The keyboard and other buttons work just fine.

Change History

Changed 7 years ago by jfuhrer

  • summary changed from Power button isn't resuming from suspend on B4s to Power button isn't always resuming from suspend on B4s

Changed 7 years ago by jfuhrer

At first I thought that this was occurring with 100% consistency, but as it turns out it just seems to be very flaky and inconsistent across all B3/4s.

I've also noticed that, when first going into suspend via the power button, the screen doesn't go all the way dark. If I press the power button again, it will become slightly darker. Each time I hit the power button the screen's darkness is altered very slightly. When I hit a key to wake it up, it very briefly goes all the way dark before waking up. I think these may be related.

Changed 7 years ago by jfuhrer

Additionally, If I press the power button several times in rapid succession and then try to resume with a key, the XO never comes out of suspend. This also seems related, but let me know if it merits its own trac ticket.

Changed 7 years ago by kimquirk

  • milestone changed from Untriaged to Trial-2

John and I also did th same set of tests on another B4; and it correctly went in and out of resume with the button push, but the screen never went all the way to black.

If I pushed the suspend button and then pressed a key on the keyboard to wake it up; the screen went all the way to black instead of waking up. Pressing a key will not wake it up -- you have to push the suspend button to wake it up.

Changed 7 years ago by jfuhrer

The serial number of the XO that can reproduce this most consistently is SHF72000098, a B3.

Changed 7 years ago by cjb

  • owner changed from hughsient@… to dilinger
  • component changed from power manager (OHM) to kernel

This likely isn't Richard Hughes' problem. :)

Changed 7 years ago by dilinger

This sounds like the sort of thing that's fixed with the new EC code that we're testing now.. stay tuned.

Changed 7 years ago by jg

  • cc rsmith added
  • keywords power added

Changed 7 years ago by jg

  • milestone changed from Trial-2 to Trial-3

Changed 7 years ago by dilinger

  • status changed from new to closed
  • resolution set to fixed

Ok, this has almost certainly been fixed; unfortunately, I've forgotten the details of what was wrong w/ the EC/kernel that caused this. Anyways, you still experience it with the latest build and firmware, feel free to reopen w/ additional details; otherwise, I'm considering this fixed amongst the flurry of other EC-related fixes.

Note: See TracTickets for help on using tickets.