Startup not working issue in Control Panel Power Schedule

Peter Suh · July 12, 2022

Below is the result of collecting the operation status for TCRP users.

DS3617xs (Operation OK)
DS3615xs (Operation OK)
DS3622xs+ (Operation OK)
DVA3221 (Operation OK)
DVA1622 (Operation OK)
DS918+ (Operation Not OK)
DS920+ (Operation Not OK)
DS1621+ (Operation Not OK)
DS2422+ (Operation Not OK)
DS1520+ (Operation Not OK)

GeminiLake (DS920+, DS1520+, etc.), known as a DTC-only model
and V1000 (DS1621+, DS2422+, etc.), this function does not work, and DS918+ also does not work.

Monitoring equipment DVA3221, DVA1622 (based on DTC) is OK.

Jun Mode and Jot Mode seem to be a common phenomenon without any distinction.

ACPI ext is related to the power button and has nothing to do with this power schedule reservation.

Is there any way to solve this problem?

psychodracon · October 30, 2022

@pocopico I've tested your extension on bare metal which is Core i5 9500T and MSI B250 MORTAR (modded to work with Coffe Lake), loader build for DS918+, DSM 7.1.1-42962 Update 2 using tinycore-redpill v0.9.2.9. Everything worked flawlessly. One boot at 7.00, second one at 9.00. Thank you very much!

Edited October 30, 2022 by psychodracon
More details

Marcus6 · July 19, 2022

I also interested to find the answer for this question.

My Xpenology worked quite well on scheduled startup and shutdown with DSM 6.2.

After updating to TCRP DSM 7.1 DS918+ it stopped to startup. Shutdown however works.

fxlupo · September 27, 2022

Same here.

Worked well with DSM 6.2.
Updated to arpl v0.4-alpha11 / DSM 7.1.1-42962 Update 1 / DS918+ (Baremetal - Asrock J3455)

Scheduled startup does not work. When I edit the settings and save I get a message "Connection failed. Check your network setting"

But the message has no effect, because if I change the shutdown time, then the NAS also shuts down at this time.

Peter Suh · October 11, 2022

I recently discovered one thing while testing the Power ON scheduling of a DS1621xs+ (Broadwellnk) with a Dell T1700.
After installing as bare metal with a USB stick and setting the schedule, I removed the USB stick.
Powered on at the scheduled time even with the stick removed.
Perhaps it is a natural result, but I wonder if DSM does not record sleep in the state of S5 in BIOS as DSM shuts down.
The log monitored by the serial port contains the following contents.

[ 255.465129] e1000e: EEE TX LPI TIMER: 00000011
[ 255.503506] pin 0 is protected by driver.
[ 256.008416] Turned off USB vbus gpio 0 (ACTIVE_LOW)
[ 256.013322] pin 0 is protected by driver.
[ 256.517433] Turned off USB vbus gpio 0 (ACTIVE_LOW)
[ 256.522340] pin 0 is protected by driver.
[ 257.026426] Turned off USB vbus gpio 0 (ACTIVE_LOW)
[ 257.031334] pin 0 is protected by driver.
[ 257.535448] Turned off USB vbus gpio 0 (ACTIVE_LOW)
[ 257.540361] pin 0 is protected by driver.
[ 258.045440] Turned off USB vbus gpio 0 (ACTIVE_LOW)
[ 258.058643] ACPI: Preparing to enter system sleep state S5
[ 258.064381] reboot: Power down
[258.067641] acpi_power_off called
[ 258.071000] Confirm SLP_TYP poweroff status 0 pm1a 1c01 pm1b 1
[ 258.087118] Confirm OS poweroff status 0 pm1a 3c01 pm1b 2001

The same log is also present on DS1621+, which does not operate on the Power On schedule.

[ 1410.300950] e1000e: EEE TX LPI TIMER: 00000011
[ 1410.820297] ACPI: Preparing to enter system sleep state S5
[ 1410.826560] reboot: Power down
[ 1410.829879] acpi_power_off called
[ 1410.833257] Confirm SLP_TYP poweroff status 0 pm1a 1c01 pm1b 1
[ 1410.850268] Confirm OS poweroff status 0 pm1a 3c01 pm1b 2001

DS1621+ has the same action of "ACPI: Preparing to enter system sleep state S5", but I think it may not be properly recorded in BIOS.

Rick4 · October 17, 2022

At me doesn't work with latest arpl-0.5-alpha1.img ARPL, in this case i get error, dsm set bios time 2 hours earlier than real time. I tried with 5-6 flash drives, and 3-4 internal SSDs, doesn't affect, only scheduled power on/ off doesn't work. If i try first, power off working, because dsm read time from synced source, but after that, power on doesn't work.

Tied with more sets:

Asrock J1900B-ITX and DS3617xs operation NOT ok

Kontron KTQM87-itx mobo and DS3617xs operation NOT ok

Asrock Q1900B and DS920+ or DS3617xs operation NOT ok

Asrock J4025 and DS920+ or DS3617xs operation NOT ok

Asrock H110m-itx+ i7-6700+ DS3617xs operation NOT ok

Edited October 17, 2022 by Rick4

Peter Suh · October 17, 2022

46 minutes ago, Rick4 said:

At me doesn't work with latest arpl-0.5-alpha1.img ARPL, in this case i get error, dsm set bios time 2 hours earlier than real time. I tried with 5-6 flash drives, and 3-4 internal SSDs, doesn't affect, only scheduled power on/ off doesn't work. If i try first, power off working, because dsm read time from synced source, but after that, power on doesn't work.

Tied with more sets:

Asrock J1900B-ITX and DS3617xs operation NOT ok

Kontron KTQM87-itx mobo and DS3617xs operation NOT ok

Asrock Q1900B and DS920+ or DS3617xs operation NOT ok

Asrock J4025 and DS920+ or DS3617xs operation NOT ok

Asrock H110m-itx+ i7-6700+ DS3617xs operation NOT ok

Could you please confirm if it is the same in TCRP?
One MOBO is enough.

Rick4 · October 17, 2022

1 hour ago, Peter Suh said:

Could you please confirm if it is the same in TCRP?
One MOBO is enough.

It was the latest ARPL, and within updated all modules, addons, etc etc and was the latest 42962 loader, so i think, it's same. I do not examined it harder.

pedroj666 · October 17, 2022

In my case, if I activate the S5 option in the bios my pc goes into a shutdown loop and then after 2 seconds it turns itself on again.

I have an Asus PRIME H410I-PLUS with a Celeron G5905 (10 Gen) running perfectly stable on ds3622xs+ with TCRP 0.9.2.7

Peter Suh · October 18, 2022

8 hours ago, pedroj666 said:

In my case, if I activate the S5 option in the bios my pc goes into a shutdown loop and then after 2 seconds it turns itself on again.

I have an Asus PRIME H410I-PLUS with a Celeron G5905 (10 Gen) running perfectly stable on ds3622xs+ with TCRP 0.9.2.7

The DS1621+ has the same behavior as "ACPI: Preparing to enter system sleep state S5", but I believe it may not be properly written to the BIOS.

@pedroj666

I'm not sure about the S5 mentioned above, just speculation.
Did you get an idea from my article about the need to set up the S5 by any chance?
Or, did any other post mention that the S5 needs to be tweaked?

pedroj666 · October 18, 2022

7 hours ago, Peter Suh said:

The DS1621+ has the same behavior as "ACPI: Preparing to enter system sleep state S5", but I believe it may not be properly written to the BIOS.

@pedroj666

I'm not sure about the S5 mentioned above, just speculation.
Did you get an idea from my article about the need to set up the S5 by any chance?
Or, did any other post mention that the S5 needs to be tweaked?

I have another older pc, with a 7 gen intel, where I tested the ds3622xs+ to see if the Power schedule StartUP worked and on that pc.

I had to activate S5 in the bios for the pc to start up at the time I set it up. My problem is that if I don't activate the s5 in the bios the pc does not start at the programmed time and that on my pc with 10 Gen cpu it doesn't work because when I tell the pc to turn off it turns on after 2 seconds by itself!

Edited October 18, 2022 by pedroj666

Peter Suh · October 18, 2022

22 minutes ago, pedroj666 said:

I have another older pc, with a 7 gen intel, where I tested the ds3622xs+ to see if the Power schedule StartUP worked and on that pc.

I had to activate S5 in the bios for the pc to start up at the time I set it up. My problem is that if I don't activate the s5 in the bios the pc does not start at the programmed time and that on my pc with 10 Gen cpu it doesn't work because when I tell the pc to turn off it turns on after 2 seconds by itself!

good. I also have several generations of Intel PCs.

I'll be looking into the relationship between each Intel generation CPU and the S5 on baremetal.

I guess I'll have to give it some time to look around.

Marcus6 · October 18, 2022

As an obvious workaround, I've set startup time in Bios. Works well.

pedroj666 · October 18, 2022

1 hour ago, Marcus6 said:

As an obvious workaround, I've set startup time in Bios. Works well.

That's what I currently do.

But this option in the bios has many limitations!

For example, at least in my bios, you can only configure a single power up schedule with the following options: daily, weekly or monthly.

You can't make the pc turn on on tuesday and then saturday without changing the bios settings!

Marcus6 · October 18, 2022

My other stupid idea was to workaround with smart plug, as I have my nas starting every time the power comes back. So if smart plug has an ability to be configured to work by schedule it can switch on the power and start NAS when it is needed. May be it would help with more tricky schedule cases.

Peter Suh · October 18, 2022

If two XPEs are being operated, and one is always on or turned on before XPE No. 2, there may be a way to turn it on through WOL at a certain time by including the

"synonet --wake" command in the scheduler as shown below.
This is also a kind of shortcut.

https://www.nextofwindows.com/how-to-wake-up-windows-machine-via-wol-from-synology-nas

Rick4 · October 20, 2022

On 10/18/2022 at 4:36 PM, Peter Suh said:

If two XPEs are being operated, and one is always on or turned on before XPE No. 2, there may be a way to turn it on through WOL at a certain time by including the

"synonet --wake" command in the scheduler as shown below.
This is also a kind of shortcut.

https://www.nextofwindows.com/how-to-wake-up-windows-machine-via-wol-from-synology-nas

Just tried that method, but unsuccesful. I set a 2nd nas the WOL, and then add a task with internal ip ans syno mac. But boesn't wake up. Tried with and adroid phone and a wake-on lan app, my 2nd server visible, command sent, but server doesn't start up. Same result with a win 11 desktop app. Tried set WOL with synology assistant, looks like OK, but doesn't work. I tried full path method:

/usr/syno/sbin/synonet –wake XX:XX:XX:XX:XX:XX eth0

with eth0 = 1st ethernet connection
eth1 = second
bond = load balancing

What's the solution?

Edited October 20, 2022 by Rick4

Rick4 · October 20, 2022

1 hour ago, Rick4 said:

Just tried that method, but unsuccesful. I set a 2nd nas the WOL, and then add a task with internal ip ans syno mac. But boesn't wake up. Tried with and adroid phone and a wake-on lan app, my 2nd server visible, command sent, but server doesn't start up. Same result with a win 11 desktop app. Tried set WOL with synology assistant, looks like OK, but doesn't work. I tried full path method:

/usr/syno/sbin/synonet –wake XX:XX:XX:XX:XX:XX eth0

with eth0 = 1st ethernet connection
eth1 = second
bond = load balancing

What's the solution?

It works with:

synonet --wake (mac) eth0

but before want use, go mobo bios, and then set in ACPI menu, "pcie devices power on" to enabled.

Peter Suh · October 21, 2022

It works with:
synonet --wake (mac) eth0

but before want use, go mobo bios, and then set in ACPI menu, "pcie devices power on" to enabled.

I have seen cases where there is no WOL activation in the MOBO bios or, if there is, there is a power ON menu through PCIE for WOL activation of the extended nic instead.

Sent from my iPhone using Tapatalk

Rick4 · October 21, 2022

7 hours ago, Peter Suh said:

I have seen cases where there is no WOL activation in the MOBO bios or, if there is, there is a power ON menu through PCIE for WOL activation of the extended nic instead.

Sent from my iPhone using Tapatalk

Yes, mine was same, no WOl menu, but have a PCIE power on menu point. I only indicated that the function works because of this, because many people may not know some parts of the BIOS.

pocopico · October 23, 2022

On 10/17/2022 at 4:24 PM, Rick4 said:

At me doesn't work with latest arpl-0.5-alpha1.img ARPL, in this case i get error, dsm set bios time 2 hours earlier than real time. I tried with 5-6 flash drives, and 3-4 internal SSDs, doesn't affect, only scheduled power on/ off doesn't work. If i try first, power off working, because dsm read time from synced source, but after that, power on doesn't work.

Tied with more sets:

Asrock J1900B-ITX and DS3617xs operation NOT ok

Kontron KTQM87-itx mobo and DS3617xs operation NOT ok

Asrock Q1900B and DS920+ or DS3617xs operation NOT ok

Asrock J4025 and DS920+ or DS3617xs operation NOT ok

Asrock H110m-itx+ i7-6700+ DS3617xs operation NOT ok

Hi,

I have a physical ds3622xsp laptop based server that power scheduling on/off works fine.

can you please check your BIOS ACPI settings and post them here ?

also the output of

dmesg |grep -i acpi

Peter Suh · October 23, 2022

28 minutes ago, pocopico said:
Hi,

I have a physical ds3622xsp laptop based server that power scheduling on/off works fine.

can you please check your BIOS ACPI settings and post them here ?

also the output of
dmesg |grep -i acpi 

It works with:

synonet --wake (mac) eth0

but before want use, go mobo bios, and then set in ACPI menu, "pcie devices power on" to enabled.

————————————————-

Judging from his last words, the conclusion seems to have been successful.

The way to activate wol in the bios is a bit unusual.

Peter Suh · October 23, 2022

32 minutes ago, pocopico said:
Hi,

I have a physical ds3622xsp laptop based server that power scheduling on/off works fine.

can you please check your BIOS ACPI settings and post them here ?

also the output of
dmesg |grep -i acpi 

@pocopico

Can I prepare and upload the acpi logs of DS3622xs+ and DS1621+ on my Dell T1700 instead?

pocopico · October 23, 2022

56 minutes ago, Peter Suh said:

@pocopico

Can I prepare and upload the acpi logs of DS3622xs+ and DS1621+ on my Dell T1700 instead?

Yes, on my physical system the shutdown/startup works out of the box. I assume its something related to BIOS ACPI settings and/or capabilities. There are offcourse PCI devices that will break this if they do not support ACPI shutdown.

On my system that power scheduling works the following are true :

sh-4.4#  cat /sys/class/rtc/rtc0/uevent
MAJOR=254
MINOR=0
DEVNAME=rtc0
PHYSDEVPATH=/devices/pnp0/00:02
PHYSDEVBUS=pnp
PHYSDEVDRIVER=rtc_cmos

sh-4.4# ls /sys/class/rtc/
rtc0

sh-4.4#  cat /proc/driver/rtc
rtc_time        : 09:09:33
rtc_date        : 2022-10-23
alrm_time       : 07:00:00
alrm_date       : 2022-10-24
alarm_IRQ       : no
alrm_pending    : no
update IRQ enabled      : no
periodic IRQ enabled    : no
periodic IRQ frequency  : 1024
max user IRQ frequency  : 64
24hr            : yes
periodic_IRQ    : no
update_IRQ      : no
HPET_emulated   : yes
BCD             : yes
DST_enable      : no
periodic_freq   : 1024
batt_status     : okay

sh-4.4# cat /proc/acpi/wakeup
Device  S-state   Status   Sysfs node
C0B0      S5    *disabled  pci:0000:00:1e.0
C108      S3    *enabled   pci:0000:00:1d.0
C10F      S3    *enabled   pci:0000:00:1d.1
C110      S3    *enabled   pci:0000:00:1d.2
C111      S3    *enabled   pci:0000:00:1d.7
C119      S3    *enabled   pci:0000:00:1a.0
C11A      S3    *enabled   pci:0000:00:1a.1
C11B      S3    *enabled   pci:0000:00:1a.7
C131      S5    *disabled  pci:0000:00:1c.1
C2A1      S5    *disabled  pci:0000:10:00.0
C132      S5    *disabled  pci:0000:00:1c.2
C137      S5    *enabled   pci:0000:18:00.0
C134      S5    *disabled  pci:0000:00:1c.4
C2A2      S5    *disabled
C23D      S5    *disabled  platform:PNP0C32:00

sh-4.4# hwclock --verbose
hwclock from util-linux 2.33.2
System Time: 1666517587.916932
Trying to open: /dev/rtc0
Using the rtc interface to the clock.
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2022/10/23 09:33:08
Hw clock time : 2022/10/23 09:33:08 = 1666517588 seconds since 1969
Time since last adjustment is 1666517588 seconds
Calculated Hardware Clock drift is 0.000000 seconds
2022-10-23 12:33:07.718012+03:00

sh-4.4# dmesg |grep rtc
[    5.609650] rtc_cmos 00:01: RTC can wake from S4
[    5.609921] rtc_cmos 00:01: rtc core: registered rtc_cmos as rtc0
[    5.609973] rtc_cmos 00:01: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
[    5.687269] rtc_cmos 00:01: setting system clock to 2022-10-18 07:39:01 UTC (1666078741)

@Peter Suh can you check for the following also ?

cat /proc/acpi/wakeup

cat /sys/class/rtc/rtc0/uevent

cat /proc/driver/rtc
ls /sys/class/rtc/

More Info :

https://www.mythtv.org/wiki/ACPI_Wakeup#Using_.2Fsys.2Fclass.2Frtc.2Frtc0.2Fwakealarm

Edited October 23, 2022 by pocopico

Peter Suh · October 23, 2022

36 minutes ago, pocopico said:

Yes, on my physical system the shutdown/startup works out of the box. I assume its something related to BIOS ACPI settings and/or capabilities. There are offcourse PCI devices that will break this if they do not support ACPI shutdown.

On my system that power scheduling works the following are true :

sh-4.4#  cat /sys/class/rtc/rtc0/uevent
MAJOR=254
MINOR=0
DEVNAME=rtc0
PHYSDEVPATH=/devices/pnp0/00:02
PHYSDEVBUS=pnp
PHYSDEVDRIVER=rtc_cmos

sh-4.4# ls /sys/class/rtc/
rtc0

sh-4.4#  cat /proc/driver/rtc
rtc_time        : 09:09:33
rtc_date        : 2022-10-23
alrm_time       : 07:00:00
alrm_date       : 2022-10-24
alarm_IRQ       : no
alrm_pending    : no
update IRQ enabled      : no
periodic IRQ enabled    : no
periodic IRQ frequency  : 1024
max user IRQ frequency  : 64
24hr            : yes
periodic_IRQ    : no
update_IRQ      : no
HPET_emulated   : yes
BCD             : yes
DST_enable      : no
periodic_freq   : 1024
batt_status     : okay

sh-4.4# cat /proc/acpi/wakeup
Device  S-state   Status   Sysfs node
C0B0      S5    *disabled  pci:0000:00:1e.0
C108      S3    *enabled   pci:0000:00:1d.0
C10F      S3    *enabled   pci:0000:00:1d.1
C110      S3    *enabled   pci:0000:00:1d.2
C111      S3    *enabled   pci:0000:00:1d.7
C119      S3    *enabled   pci:0000:00:1a.0
C11A      S3    *enabled   pci:0000:00:1a.1
C11B      S3    *enabled   pci:0000:00:1a.7
C131      S5    *disabled  pci:0000:00:1c.1
C2A1      S5    *disabled  pci:0000:10:00.0
C132      S5    *disabled  pci:0000:00:1c.2
C137      S5    *enabled   pci:0000:18:00.0
C134      S5    *disabled  pci:0000:00:1c.4
C2A2      S5    *disabled
C23D      S5    *disabled  platform:PNP0C32:00

@Peter Suh can you check for the following also ?

cat /proc/acpi/wakeup

cat /sys/class/rtc/rtc0/uevent

cat /proc/driver/rtc
ls /sys/class/rtc/

More Info :

https://www.mythtv.org/wiki/ACPI_Wakeup#Using_.2Fsys.2Fclass.2Frtc.2Frtc0.2Fwakealarm

OK, I'll report in detail when I get home. It's outside now.

Rick4 · October 23, 2022

5 hours ago, pocopico said:
Hi,

I have a physical ds3622xsp laptop based server that power scheduling on/off works fine.

can you please check your BIOS ACPI settings and post them here ?

also the output of
dmesg |grep -i acpi 

First: the issue, dsm set wrong time to bios, i see 2 hours earlier, than real.

Second: i succesfully fix it wih WOL function, 1st server can wake 2nd, and then stop timer working with synced dsm time.

I get that lines:

:~# dmesg |grep -i acpi
[ 0.000000] BIOS-e820: [mem 0x0000000079675000-0x00000000796ccfff] ACPI NVS
[ 0.000000] reserve setup_data: [mem 0x0000000079675000-0x00000000796ccfff] A CPI NVS
[ 0.000000] efi: ACPI 2.0=0x79675000 ACPI=0x79675000 SMBIOS=0x79946000 SM BIOS 3.0=0x79945000 ESRT=0x75ce3298
[ 0.000000] ACPI: Early table checksum verification disabled
[ 0.000000] ACPI: RSDP 0x0000000079675000 000024 (v02 ALASKA)
[ 0.000000] ACPI: XSDT 0x00000000796750C0 0000E4 (v01 ALASKA A M I 0107200 9 AMI 00010013)
[ 0.000000] ACPI: FACP 0x0000000079681850 000114 (v06 ALASKA A M I 0107200 9 AMI 00010013)
[ 0.000000] ACPI: DSDT 0x0000000079675250 00C600 (v02 ALASKA A M I 0107200 9 INTL 20160930)
[ 0.000000] ACPI: FACS 0x00000000796CC080 000040
[ 0.000000] ACPI: FPDT 0x0000000079681970 000044 (v01 ALASKA A M I 0107200 9 AMI 00010013)
[ 0.000000] ACPI: FIDT 0x00000000796819C0 00009C (v01 ALASKA A M I 0107200 9 AMI 00010013)
[ 0.000000] ACPI: MCFG 0x0000000079681A60 00003C (v01 ALASKA A M I 0107200 9 MSFT 00000097)
[ 0.000000] ACPI: DBG2 0x0000000079681AA0 000072 (v00 INTEL GLK-SOC 0000000 3 BRXT 0100000D)
[ 0.000000] ACPI: DBGP 0x0000000079681B20 000034 (v01 INTEL GLK-SOC 0000000 3 BRXT 0100000D)
[ 0.000000] ACPI: HPET 0x0000000079681B60 000038 (v01 INTEL GLK-SOC 0000000 3 BRXT 0100000D)
[ 0.000000] ACPI: LPIT 0x0000000079681BA0 00005C (v01 INTEL GLK-SOC 0000000 3 BRXT 0100000D)
[ 0.000000] ACPI: APIC 0x0000000079681C00 000084 (v03 INTEL GLK-SOC 0000000 3 BRXT 0100000D)
[ 0.000000] ACPI: NPKT 0x0000000079681C90 000065 (v01 INTEL GLK-SOC 0000000 3 BRXT 0100000D)
[ 0.000000] ACPI: SSDT 0x0000000079681D00 003E72 (v02 INTEL DptfTab 0000000 3 BRXT 0100000D)
[ 0.000000] ACPI: SSDT 0x0000000079685B80 0010B3 (v02 INTEL UsbCTabl 0000000 3 BRXT 0100000D)
[ 0.000000] ACPI: SSDT 0x0000000079686C40 00153E (v01 Intel_ Platform 0000100 0 INTL 20160930)
[ 0.000000] ACPI: AAFT 0x0000000079688180 00031A (v01 ALASKA OEMAAFT 0107200 9 MSFT 00000097)
[ 0.000000] ACPI: SSDT 0x00000000796884A0 0004D5 (v02 PmRef Cpu0Ist 0000300 0 INTL 20160930)
[ 0.000000] ACPI: SSDT 0x0000000079688980 000775 (v02 CpuRef CpuSsdt 0000300 0 INTL 20160930)
[ 0.000000] ACPI: SSDT 0x0000000079689100 00035F (v02 PmRef Cpu0Tst 0000300 0 INTL 20160930)
[ 0.000000] ACPI: SSDT 0x0000000079689460 0001E6 (v02 PmRef ApTst 0000300 0 INTL 20160930)
[ 0.000000] ACPI: SSDT 0x0000000079689650 0028FE (v02 SaSsdt SaSsdt 0000300 0 INTL 20160930)
[ 0.000000] ACPI: UEFI 0x000000007968BF50 000042 (v01 ALASKA A M I 0000000 2 01000013)
[ 0.000000] ACPI: TPM2 0x000000007968BFA0 000034 (v03 ALASKA A M I 0000000 1 AMI 00000000)
[ 0.000000] ACPI: DMAR 0x000000007968BFE0 0000A8 (v01 INTEL GLK-SOC 0000000 3 BRXT 0100000D)
[ 0.000000] ACPI: WDAT 0x000000007968C090 000104 (v01 0000000 0 00000000)
[ 0.000000] ACPI: WSMT 0x000000007968C1A0 000028 (v01 ALASKA A M I 0107200 9 AMI 00010013)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: PM-Timer IO Port: 0x408
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high level lint[0x1])
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high level lint[0x1])
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high level lint[0x1])
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x04] high level lint[0x1])
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
[ 0.001109] ACPI: Core revision 20150930
[ 0.040763] ACPI: 9 ACPI AML tables successfully acquired and loaded
[ 0.135776] PM: Registering ACPI NVS region [mem 0x79675000-0x796ccfff] (3604 48 bytes)
[ 0.149268] ACPI: bus type PCI registered
[ 0.158983] ACPI: Added _OSI(Module Device)
[ 0.159294] ACPI: Added _OSI(Processor Device)
[ 0.159599] ACPI: Added _OSI(3.0 _SCP Extensions)
[ 0.159919] ACPI: Added _OSI(Processor Aggregator Device)
[ 0.174875] ACPI: Executed 12 blocks of module-level executable AML code
[ 0.193935] ACPI: Dynamic OEM Table Load:
[ 0.194265] ACPI: SSDT 0xFFFF88007A077A00 0001E6 (v02 PmRef ApIst 0000300 0 INTL 20160930)
[ 0.196582] ACPI: Executed 1 blocks of module-level executable AML code
[ 0.199797] ACPI: Interpreter enabled
[ 0.200123] ACPI: (supports S0 S4 S5)
[ 0.200385] ACPI: Using IOAPIC for interrupt routing
[ 0.200962] PCI: Using host bridge windows from ACPI; if necessary, use "pci= nocrs" and report a bug
[ 0.219852] ACPI: Power Resource [DRST] (on)
[ 0.221052] ACPI: Power Resource [DRST] (on)
[ 0.222138] ACPI: Power Resource [DRST] (on)
[ 0.223218] ACPI: Power Resource [DRST] (on)
[ 0.224297] ACPI: Power Resource [DRST] (on)
[ 0.225464] ACPI: Power Resource [DRST] (on)
[ 0.226665] ACPI: Power Resource [WRST] (on)
[ 0.238999] ACPI: Power Resource [FN00] (on)
[ 0.241270] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[ 0.241707] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM S egments MSI]
[ 0.244017] acpi PNP0A08:00: _OSC: OS now controls [PME AER PCIeCapability]
[ 0.244733] acpi PNP0A08:00: host bridge window [mem 0x1000000010000 window] (ignored, not CPU addressable)
[ 0.269091] pci 0000:00:13.0: System wakeup disabled by ACPI
[ 0.271152] pci 0000:00:13.2: System wakeup disabled by ACPI
[ 0.273775] pci 0000:00:15.0: System wakeup disabled by ACPI
[ 0.281211] pci 0000:02:00.0: System wakeup disabled by ACPI
[ 0.288180] ACPI: PCI Interrupt Link [LNKA] (IRQs *3 4 5 6 10 11 12 14 15), d isabled.
[ 0.289047] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 *4 5 6 10 11 12 14 15), d isabled.
[ 0.289891] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15), d isabled.
[ 0.290756] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 *6 10 11 12 14 15), d isabled.
[ 0.291613] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 10 11 12 14 15) *7, disabled.
[ 0.292483] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 11 12 14 15) *9, disabled.
[ 0.293364] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 *10 11 12 14 15), d isabled.
[ 0.294204] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 10 *11 12 14 15), d isabled.
[ 0.298746] ACPI: Enabled 6 GPEs in block 00 to 7F
[ 0.329331] PCI: Using ACPI for IRQ routing
[ 0.385782] pnp: PnP ACPI init
[ 0.388000] system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.391263] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.397086] system 00:02: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.398086] pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active)
[ 0.399455] pnp: PnP ACPI: found 4 devices
[ 0.411163] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_id le_ns: 2085701024 ns
[ 9.255857] ACPI: bus type USB registered
[ 9.707405] ACPI: Power Button [PWRB]
[ 56.119680] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
[ 56.121619] acpi device:54: registered as cooling_device4

5 hours ago, pocopico said:

Edited October 23, 2022 by Rick4

Sign In

Startup not working issue in Control Panel Power Schedule

Question

Peter Suh

84 answers to this question

Recommended Posts

psychodracon

Marcus6

fxlupo

Peter Suh

Rick4

Peter Suh

Rick4

pedroj666

Peter Suh

pedroj666

Peter Suh

Marcus6

pedroj666

Marcus6

Peter Suh

Rick4

Rick4

Peter Suh

Rick4

pocopico

Peter Suh

Peter Suh

pocopico

Peter Suh

Rick4

Join the conversation

Forums

What's new

MUST READ

Members