Lines Matching refs:was

29 After a suspend cycle you can tell how much time was spent in a hardware sleep
132 So there you have it: the PCI device associated with this GPIO wakeup was ``0000:c2:00.4``.
172 from properly entering s0i3.  This was debugged using internal AMD tools
174 when a core was offlined.  It was determined that the hardware didn't get
176 CPU from going into the deepest state. The issue was debugged to a missing
183 A big problem that occurred with Rembrandt was that there was graphical
187 This actually was a misalignment for earlier silicon as well, but was not
202 The HPET was being used to program the wakeup source for the system, however
203 this was causing a spurious wakeup after 5 minutes.  The correct alarm to use
204 was the ACPI alarm.
210 After resuming from s2idle, the NVME disk would disappear.  This was due to the
222 This was fixed in the platform firmware, but a number of systems didn't
237 The timing problem was identified by comparing the values of the idle mask.
244 entering a hardware sleep state if the internal panel was on during the sequence.
345    "0",  "Pin",      "thermal pin BP_THERMTRIP_L was tripped"
346    "1",  "Pin",      "power button was pressed for 4 seconds"
347    "2",  "Pin",      "shutdown pin was tripped"
348    "4",  "Remote",   "remote ASF power off command was received"
349    "9",  "Internal", "internal CPU thermal limit was tripped"
350    "16", "Pin",      "system reset pin BP_SYS_RST_L was tripped"
356    "22", "Pin",      "keyboard reset pin KB_RST_L was tripped"
360    "26", "Remote",   "remote ASF reset command was received"