intel

[iotg] [ehl] [ehl-aaeon] system shuts off instead of rebooting during cold-reboot test

Bug #1945940 reported by Doug Jacobs on 2021-10-04

6

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	intel	Fix Committed	Undecided	Unassigned
	Lookout-canyon-series	Fix Released	Undecided	Unassigned	intel sprint2

Bug Description

[Summary]During the warm and cold reboot stress tests, the system is rebooted several times. The system restarts properly with the warm tests but during the cold tests, it just shuts off. You have to manually power it back on. At that point, CDTS reconnects and starts the next cycle.

[Steps to reproduce]
Start up the Cold Reboot Stress tests on CDTS against the DUT

[Expected result]
The system should properly reboot each time.

[Actual result]
The system shuts off.

[Failure rate]100%

[Additional information]
CID: 202109-29496
SKU:
system-manufacturer: AAEON
system-product-name: UPN-EHL01
bios-version: UNEHAM0D
CPU: Intel Atom(R) x6425RE Processor @ 1.90GHz (4x)
GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4571] (rev 01)
kernel-version: 5.13.0-1004-intel

[Stage]
Issue reported and logs collected right after it happened

Tags:

Revision history for this message

Doug Jacobs (djacobs98) wrote on 2021-10-04:

#1

checkbox-session.tgz Edit (278.6 KiB, application/x-tar)

Automatically attached

Revision history for this message

Doug Jacobs (djacobs98) wrote on 2021-10-04:

#2

snap_list.log Edit (1.2 KiB, text/plain)

Automatically attached

Revision history for this message

Doug Jacobs (djacobs98) wrote on 2021-10-04:

#3

acpidump.log Edit (1.1 MiB, text/plain)

Automatically attached

Revision history for this message

Doug Jacobs (djacobs98) wrote on 2021-10-04:

#4

sosreport-linux-2021-10-04-dezwwyg.tar.gz Edit (8.9 MiB, application/x-tar)

Automatically attached

Revision history for this message

Alex Hung (alexhung) wrote on 2021-10-04:

#5

A system relies on realtime clock (RTC) to do a cold boot to start automatically. There can be some possibilities:

1. RTC hardware isn't stable enough (related to motherboard and / or BIOS)
2. RTC wake-up time expired before system shut down, and alarm was triggered too early.

One can use command "rtcwake" to verify RTC.

For example, I use "sudo rtcwake -m mem -s 15" to put my system to s3 and wake it up after 15 seconds. One can use "sudo rtcwake -m off -s 120" to power off a system and wake it up after 120 seconds

Revision history for this message

Alex Hung (alexhung) wrote on 2021-10-04:

#6

Please note ACPI spec actually requires RTC wake-up from S5 (off) to be NOT supported. However, Intel's hardware usually supports it and AMD may not.

Revision history for this message

Kent Lin (kent-jclin) wrote on 2021-10-16:

#7

This is fixed with Intel Corporation: EHLSFWI1.R00.3162.A01.2104131432 (UEFI)

Changed in intel:
status:	New → Fix Committed

Revision history for this message

Pierre Equoy (pieq) wrote on 2021-10-25:

#8

Tested OK on device 202109-29496 (Aaeon EHL board).

In the BIOS > Advanced > [AAEON Features] Power Management > [Wake Events] RTC wake system from S5

Make sure the option "Bypass" is selected.

Then boot the device, and try running the Checkbox cold boot tests, or just run command such as:

sudo rtcwake -m off -s 120

as advertised by Alex in comment 5.

@Alex, not sure I understand comment 6. Does it mean the ACPI standard actually goes **against** implementing RTC wake from S5?

tags:

added: cqa-verified

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.