Re: Clock looping back in time on 7.8-stable VM and uptime going back

Tue, 06 Jan 2026 07:51:20 -0800 

Hi all,
I just wanted to confirm that using kern.timecounter.hardware=tsc in the guest fixes the issue. 
I've had no clock loop issue for over a month now.
There's definitively something behaving incorrectly with vmmci and pvclock. 

Arnaud

On 01/12/2025 00:08:47, "Arnaud Brand" <[email protected]> wrote:


Hi Stefan,

Thanks for your answer !

The problem just happened a few minutes ago.
Process stuck and clock looping between 23:18:47 and 23:18:51

GUEST in stuck/loop state :
ns1 ~$ sysctl kern.timecounter
kern.timecounter.tick=1
kern.timecounter.timestepwarnings=0
kern.timecounter.hardware=pvclock0
kern.timecounter.choice=i8254(0) pvclock0(1500) tsc(-1000)
ns1 ~$ sysctl hw.sensors
hw.sensors.pvclock0.timedelta0=-0.106237 secs, OK, Sun Nov 30 23:18:39.261
hw.sensors.vmmci0.timedelta0=-0.106263 secs, OK, Sun Nov 30 23:18:39.261
ns1 ~$

HOST when GUEST is stuck/looping :
occam ~$ sysctl kern.timecounter
kern.timecounter.tick=1
kern.timecounter.timestepwarnings=0
kern.timecounter.hardware=tsc
kern.timecounter.choice=i8254(0) acpihpet0(1000) tsc(2000) acpitimer0(1000)
occam ~$ sysctl hw.sensors
hw.sensors.cpu0.frequency0=950000000.00 Hz
hw.sensors.cpu1.frequency0=950000000.00 Hz
hw.sensors.cpu2.frequency0=950000000.00 Hz
hw.sensors.cpu3.frequency0=950000000.00 Hz
hw.sensors.km0.temp0=61.25 degC
occam ~$

NTPD logs on GUEST :
ns1 ~# grep -e "Nov 30 .* ntpd" /var/log/{daemon,messages} | tail -10
/var/log/daemon:Nov 30 23:15:02 ns1 ntpd[89561]: clock is now synced
/var/log/daemon:Nov 30 23:15:02 ns1 ntpd[89561]: clock is now unsynced
/var/log/daemon:Nov 30 23:16:33 ns1 ntpd[87272]: adjusting local clock by 
0.123105s
/var/log/daemon:Nov 30 23:16:33 ns1 ntpd[87272]: adjusting local clock by 
0.118146s
/var/log/daemon:Nov 30 23:16:33 ns1 ntpd[89561]: clock is now synced
/var/log/daemon:Nov 30 23:16:33 ns1 ntpd[89561]: clock is now unsynced
/var/log/daemon:Nov 30 23:18:03 ns1 ntpd[87272]: adjusting local clock by 
0.120853s
/var/log/daemon:Nov 30 23:18:03 ns1 ntpd[87272]: adjusting local clock by 
0.115878s
/var/log/daemon:Nov 30 23:18:03 ns1 ntpd[89561]: clock is now synced
/var/log/daemon:Nov 30 23:18:03 ns1 ntpd[89561]: clock is now unsynced
ns1 ~#

NTPD logs on HOST :
occam ~$ grep -e "Nov 30 .* ntpd" /var/log/{daemon,messages} | tail -10
/var/log/daemon:Nov 30 03:46:12 occam ntpd[72199]: adjusting clock frequency by 
0.662668 to 23.159785ppm
/var/log/daemon:Nov 30 14:41:26 occam ntpd[72199]: adjusting clock frequency by 
-0.622550 to 22.537236ppm
/var/log/daemon:Nov 30 23:11:39 occam ntpd[72199]: adjusting clock frequency by 
0.772198 to 23.309433ppm
occam ~$

Output of a script to keep track on clock state on GUEST :
2025/11/30-23:11:38 -> 2/2 sensors valid, clock unsynced
2025/11/30-23:12:38 -> 2/2 sensors valid, clock unsynced
2025/11/30-23:13:38 -> 2/2 sensors valid, clock unsynced, clock offset is 
88.232ms
2025/11/30-23:14:38 -> 2/2 sensors valid, clock unsynced
2025/11/30-23:15:38 -> 2/2 sensors valid, clock unsynced
2025/11/30-23:16:38 -> 2/2 sensors valid, clock unsynced, clock offset is 
93.145ms
2025/11/30-23:17:38 -> 2/2 sensors valid, clock unsynced
2025/11/30-23:18:38 -> 2/2 sensors valid, clock unsynced

GUEST in working state
ns1 ~$ sysctl kern.timecounter
kern.timecounter.tick=1
kern.timecounter.timestepwarnings=0
kern.timecounter.hardware=pvclock0
kern.timecounter.choice=i8254(0) pvclock0(1500) tsc(-1000)
ns1 ~$ sysctl hw.sensors
hw.sensors.pvclock0.timedelta0=-2.231211 secs, OK, Sun Nov 30 23:34:21.857
hw.sensors.vmmci0.timedelta0=-2.231267 secs, OK, Sun Nov 30 23:34:21.857
ns1 ~$

HOST in working state
occam ~$ sysctl kern.timecounter
kern.timecounter.tick=1
kern.timecounter.timestepwarnings=0
kern.timecounter.hardware=tsc
kern.timecounter.choice=i8254(0) acpihpet0(1000) tsc(2000) acpitimer0(1000)
occam ~$ sysctl hw.sensors
hw.sensors.cpu0.frequency0=950000000.00 Hz
hw.sensors.cpu1.frequency0=950000000.00 Hz
hw.sensors.cpu2.frequency0=950000000.00 Hz
hw.sensors.cpu3.frequency0=950000000.00 Hz
hw.sensors.km0.temp0=61.50 degC
occam ~$


It looks like acpitimer0 is not available in the guest, only in the host (or 
I'm doing it wrong by just typing  sysctl kern.timecounter.hardware=acpitimer0 )
I've found another (rather old) thread on reddit where the person suggests 
using tsc in the guest.
I'll give it a try.
If it doesn't work I'll try compiling a new kernel but this might take a while 
on this hardware.

Thanks for your help !
Cheers
Arnaud

On 30/11/2025 23:12:38, "Stefan Fritsch" <[email protected]> wrote:


Hi Arnaud,

On Sun, 30 Nov 2025, Arnaud Brand wrote:


 >Synopsis:    Clock looping over the same 4 seconds until date/time is reset
 and uptime going back too
 >Category:    system
 >Environment:
     System      : OpenBSD 7.8
     Details     : OpenBSD 7.8 (GENERIC) #54: Sun Oct 12 12:45:58 MDT 2025
              [email protected]:/usr/src/sys/arch/amd64/compile/GENERIC

     Architecture: OpenBSD.amd64
     Machine     : amd64
 >Description:
 This clock loop problem occurs on a 7.8-stable VM running on a 7.8-stable host
 running vmd on a PCEngine APU4D device.
 Both host and VM boot fine, without errors.
 After some time the system clock in the VM seems to be looping over the same 4
 seconds indefinitely.
 Process that refresh the display on regular intervals (like top or systat for
 example), do not refresh their display automatically anymore, even when set to
 refresh at shorter intervals that the clock loop interval ("systat 1" or "top
 -s1" for example doesn't refresh either).
 Shell commands mostly work : apparently as long as you don't need to sleep,
 you're OK.
 sleep in the ksh shell never returns.
 Login in via SSH also never finishes, but existing SSH sessions work fine
 (with the exception of sleeps as stated above).
 I've tried various openntpd setups on the VM (no ntpd, sensor *, sensor vmmci,
 sensor pvclock) as suggested by other users on misc@, but it doesn't seem to
 change anything.
 Time on the host is kept up to date via openntpd (pool.ntp.org,
 time.cloudflare.com, and constraints quad9 IPv4+v6 and www.google.com).
 >How-To-Repeat:
 The problem occurs seemingly randomly, sometimes after 20 minutes, sometimes
 after 10 hours.
 I couldn't find anything in any log file that happens around the moment the
 time starts to loop.
 I looked at the host log files and dmesg to try to find an event that I could
 correlate, without any success.
 Sleeping processes appear to be in the "nanoslp" state in ps.
 >Fix:
 It's a temporary workaround, not a fix, but resetting the date in the VM
 resumes the clock and unblocks the sleeping processes.
 Just typing "doas date 202511291629" does the trick (with the current
 date/time of course) : any stuck "top" or "systat" then comes back to live.
 Killing ntpd and starting it also does the trick.



Please provide the output of

sysctl kern.timecounter

both in the guest and on the host. And of

sysctl hw.sensors

in the guest, both while it still works and when the clock is stuck.
Are you running ntpd in the guest? If yes, does it log something
interesting?

If you have kern.timecounter.hardware=pvclock0 in the guest, you could try
to set it to acpitimer0 during boot and see if that changes anything.

You could also try to compile a kernel for the guest that has this commit
reverted:

commit 3d7a3484350c19bc464e714cbd7454adb563a465
Author: sf <[email protected]>
Date:   Fri Jun 20 14:06:34 2025 +0000

    pvclock: Fix reading clock, add time sensor


Cheers,
Stefan





 dmesg:
 OpenBSD 7.8 (GENERIC) #54: Sun Oct 12 12:45:58 MDT 2025
     [email protected]:/usr/src/sys/arch/amd64/compile/GENERIC
 real mem = 1593810944 (1519MB)
 avail mem = 1519071232 (1448MB)
 random: good seed from bootblocks
 mpath0 at root
 scsibus0 at mpath0: 256 targets
 mainbus0 at root
 bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf2760 (10 entries)
 bios0: vendor SeaBIOS version "1.16.3p0-OpenBSD-vmm" date 01/01/2011
 bios0: OpenBSD VMM
 acpi at bios0 not configured
 cpu0 at mainbus0: (uniprocessor)
 cpu0: AMD GX-412TC SOC, 22.39 MHz, 16-30-01
 cpu0: cpuid 1
 
edx=78ba97f<FPU,VME,DE,PSE,TSC,MSR,PAE,CX8,SEP,PGE,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2>
 
ecx=b6d82203<SSE3,PCLMUL,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,HV>
 cpu0: cpuid 6 eax=4<ARAT>
 cpu0: cpuid 7.0 ebx=8<BMI1>
 cpu0: cpuid d.1 eax=1<XSAVEOPT>
 cpu0: cpuid 80000001 edx=27d3fbff<NXE,MMXX,FFXSR,PAGE1GB,LONG>
 
ecx=1d4037fb<LAHF,CMPLEG,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TOPEXT,DBKP,PERFTSC,PCTRL3>
 cpu0: cpuid 80000007 edx=100<ITSC>
 cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 2-way I-cache, 2MB 64b/line
 16-way L2 cache
 cpu0: smt 0, core 0, package 0
 pvbus0 at mainbus0: KVM, OpenBSD
 pvclock0 at pvbus0
 pci0 at mainbus0 bus 0
 pchb0 at pci0 dev 0 function 0 "OpenBSD VMM Host" rev 0x00
 virtio0 at pci0 dev 1 function 0 "Qumranet Virtio 1.x RNG" rev 0x01
 viornd0 at virtio0
 virtio0: irq 3
 virtio1 at pci0 dev 2 function 0 "Qumranet Virtio 1.x Network" rev 0x01
 vio0 at virtio1: 1 queue, address fe:e1:bb:d1:0b:3a
 virtio1: irq 5
 virtio2 at pci0 dev 3 function 0 "Qumranet Virtio 1.x Storage" rev 0x01
 vioblk0 at virtio2
 virtio2: irq 6
 scsibus1 at vioblk0: 1 targets
 sd0 at scsibus1 targ 0 lun 0: <VirtIO, Block Device, >
 sd0: 16384MB, 512 bytes/sector, 33554432 sectors
 virtio3 at pci0 dev 4 function 0 "Qumranet Virtio 1.x Storage" rev 0x01
 vioblk1 at virtio3
 virtio3: irq 7
 scsibus2 at vioblk1: 1 targets
 sd1 at scsibus2 targ 0 lun 0: <VirtIO, Block Device, >
 sd1: 5120MB, 512 bytes/sector, 10485760 sectors
 virtio4 at pci0 dev 5 function 0 "OpenBSD VMM Control" rev 0x00
 vmmci0 at virtio4
 virtio4: irq 9
 isa0 at mainbus0
 isadma0 at isa0
 com0 at isa0 port 0x3f8/8 irq 4: ns8250, no fifo
 com0: console
 vscsi0 at root
 scsibus3 at vscsi0: 256 targets
 softraid0 at root
 scsibus4 at softraid0: 256 targets
 root on sd0a (ebeea7a175419e52.a) swap on sd0b dump on sd0b

 usbdevs:
 usbdevs: no USB controllers found

 pcidump:
 Domain /dev/pci0:
  0:0:0: OpenBSD VMM Host
     0x0000: Vendor ID: 0b5d, Product ID: 0666
     0x0004: Command: 0103, Status: 0000
     0x0008:    Class: 06 Bridge, Subclass: 00 Host,
         Interface: 00, Revision: 00
     0x000c: BIST: 00, Header Type: 00, Latency Timer: 00,
         Cache Line Size: 00
     0x0010: BAR empty (00000000)
     0x0014: BAR empty (00000000)
     0x0018: BAR empty (00000000)
     0x001c: BAR empty (00000000)
     0x0020: BAR empty (00000000)
     0x0024: BAR empty (00000000)
     0x0028: Cardbus CIS: 00000000
     0x002c: Subsystem Vendor ID: 0b5d Product ID: 0000
     0x0030: Expansion ROM Base Address: 00000000
     0x0038: 00000000
     0x003c: Interrupt Pin: 00 Line: 00 Min Gnt: 00 Max Lat: 00
     0x0000: 06660b5d 00000103 06000000 00000000
     0x0010: 00000000 00000000 00000000 00000000
     0x0020: 00000000 00000000 00000000 00000b5d
     0x0030: 00000000 00000000 00000000 00000000
     0x0040: 00000000 00000000 00000000 00000000
     0x0050: 00000000 00000000 00000000 00000000
     0x0060: 00000000 00000000 00000000 00000000
     0x0070: 00000000 00000000 00000000 00000000
     0x0080: 00000000 00000000 00000000 00000000
     0x0090: 00000000 00000000 00000000 00000000
     0x00a0: 00000000 00000000 00000000 00000000
     0x00b0: 00000000 00000000 00000000 00000000
     0x00c0: 00000000 00000000 00000000 00000000
     0x00d0: 00000000 00000000 00000000 00000000
     0x00e0: 00000000 00000000 00000000 00000000
     0x00f0: 00000000 00000000 00000000 00000000
  0:1:0: Qumranet Virtio 1.x RNG
     0x0000: Vendor ID: 1af4, Product ID: 1044
     0x0004: Command: 0107, Status: 0010
     0x0008:    Class: 08 System, Subclass: 80 Miscellaneous,
         Interface: 00, Revision: 01
     0x000c: BIST: 00, Header Type: 00, Latency Timer: 00,
         Cache Line Size: 00
     0x0010: BAR io addr: 0x00001000/0x1000
     0x0014: BAR empty (00000000)
     0x0018: BAR empty (00000000)
     0x001c: BAR empty (00000000)
     0x0020: BAR empty (00000000)
     0x0024: BAR empty (00000000)
     0x0028: Cardbus CIS: 00000000
     0x002c: Subsystem Vendor ID: 0b5d Product ID: 0004
     0x0030: Expansion ROM Base Address: 00000000
     0x0038: 00000000
     0x003c: Interrupt Pin: 01 Line: 03 Min Gnt: 00 Max Lat: 00
     0x0040: Capability 0x09: Vendor Specific
     0x0058: Capability 0x09: Vendor Specific
     0x0070: Capability 0x09: Vendor Specific
     0x0000: 10441af4 00100107 08800001 00000000
     0x0010: 00001001 00000000 00000000 00000000
     0x0020: 00000000 00000000 00000000 00040b5d
     0x0030: 00000000 00000040 00000000 00000103
     0x0040: 01105809 00000000 00000000 00000038
     0x0050: 00000000 00000000 03107009 00000000
     0x0060: 00000200 00000001 00000000 00000000
     0x0070: 02100009 00000000 00000100 00000002
     0x0080: 00000000 00000000 00000000 00000000
     0x0090: 00000000 00000000 00000000 00000000
     0x00a0: 00000000 00000000 00000000 00000000
     0x00b0: 00000000 00000000 00000000 00000000
     0x00c0: 00000000 00000000 00000000 00000000
     0x00d0: 00000000 00000000 00000000 00000000
     0x00e0: 00000000 00000000 00000000 00000000
     0x00f0: 00000000 00000000 00000000 00000000
  0:2:0: Qumranet Virtio 1.x Network
     0x0000: Vendor ID: 1af4, Product ID: 1041
     0x0004: Command: 0107, Status: 0010
     0x0008:    Class: 08 System, Subclass: 80 Miscellaneous,
         Interface: 00, Revision: 01
     0x000c: BIST: 00, Header Type: 00, Latency Timer: 00,
         Cache Line Size: 00
     0x0010: BAR io addr: 0x00002000/0x1000
     0x0014: BAR empty (00000000)
     0x0018: BAR empty (00000000)
     0x001c: BAR empty (00000000)
     0x0020: BAR empty (00000000)
     0x0024: BAR empty (00000000)
     0x0028: Cardbus CIS: 00000000
     0x002c: Subsystem Vendor ID: 0b5d Product ID: 0001
     0x0030: Expansion ROM Base Address: 00000000
     0x0038: 00000000
     0x003c: Interrupt Pin: 01 Line: 05 Min Gnt: 00 Max Lat: 00
     0x0040: Capability 0x09: Vendor Specific
     0x0058: Capability 0x09: Vendor Specific
     0x0070: Capability 0x09: Vendor Specific
     0x0088: Capability 0x09: Vendor Specific
     0x0000: 10411af4 00100107 08800001 00000000
     0x0010: 00002001 00000000 00000000 00000000
     0x0020: 00000000 00000000 00000000 00010b5d
     0x0030: 00000000 00000040 00000000 00000105
     0x0040: 01105809 00000000 00000000 00000038
     0x0050: 00000000 00000000 04107009 00000000
     0x0060: 00000300 00000008 00000000 00000000
     0x0070: 03108809 00000000 00000200 00000001
     0x0080: 00000000 00000000 02100009 00000000
     0x0090: 00000100 00000002 00000000 00000000
     0x00a0: 00000000 00000000 00000000 00000000
     0x00b0: 00000000 00000000 00000000 00000000
     0x00c0: 00000000 00000000 00000000 00000000
     0x00d0: 00000000 00000000 00000000 00000000
     0x00e0: 00000000 00000000 00000000 00000000
     0x00f0: 00000000 00000000 00000000 00000000
  0:3:0: Qumranet Virtio 1.x Storage
     0x0000: Vendor ID: 1af4, Product ID: 1042
     0x0004: Command: 0107, Status: 0010
     0x0008:    Class: 01 Mass Storage, Subclass: 00 SCSI,
         Interface: 00, Revision: 01
     0x000c: BIST: 00, Header Type: 00, Latency Timer: 00,
         Cache Line Size: 00
     0x0010: BAR io addr: 0x00003000/0x1000
     0x0014: BAR empty (00000000)
     0x0018: BAR empty (00000000)
     0x001c: BAR empty (00000000)
     0x0020: BAR empty (00000000)
     0x0024: BAR empty (00000000)
     0x0028: Cardbus CIS: 00000000
     0x002c: Subsystem Vendor ID: 0b5d Product ID: 0002
     0x0030: Expansion ROM Base Address: 00000000
     0x0038: 00000000
     0x003c: Interrupt Pin: 01 Line: 06 Min Gnt: 00 Max Lat: 00
     0x0040: Capability 0x09: Vendor Specific
     0x0058: Capability 0x09: Vendor Specific
     0x0070: Capability 0x09: Vendor Specific
     0x0088: Capability 0x09: Vendor Specific
     0x0000: 10421af4 00100107 01000001 00000000
     0x0010: 00003001 00000000 00000000 00000000
     0x0020: 00000000 00000000 00000000 00020b5d
     0x0030: 00000000 00000040 00000000 00000106
     0x0040: 01105809 00000000 00000000 00000038
     0x0050: 00000000 00000000 04107009 00000000
     0x0060: 00000300 00000018 00000000 00000000
     0x0070: 03108809 00000000 00000200 00000001
     0x0080: 00000000 00000000 02100009 00000000
     0x0090: 00000100 00000002 00000000 00000000
     0x00a0: 00000000 00000000 00000000 00000000
     0x00b0: 00000000 00000000 00000000 00000000
     0x00c0: 00000000 00000000 00000000 00000000
     0x00d0: 00000000 00000000 00000000 00000000
     0x00e0: 00000000 00000000 00000000 00000000
     0x00f0: 00000000 00000000 00000000 00000000
  0:4:0: Qumranet Virtio 1.x Storage
     0x0000: Vendor ID: 1af4, Product ID: 1042
     0x0004: Command: 0107, Status: 0010
     0x0008:    Class: 01 Mass Storage, Subclass: 00 SCSI,
         Interface: 00, Revision: 01
     0x000c: BIST: 00, Header Type: 00, Latency Timer: 00,
         Cache Line Size: 00
     0x0010: BAR io addr: 0x00004000/0x1000
     0x0014: BAR empty (00000000)
     0x0018: BAR empty (00000000)
     0x001c: BAR empty (00000000)
     0x0020: BAR empty (00000000)
     0x0024: BAR empty (00000000)
     0x0028: Cardbus CIS: 00000000
     0x002c: Subsystem Vendor ID: 0b5d Product ID: 0002
     0x0030: Expansion ROM Base Address: 00000000
     0x0038: 00000000
     0x003c: Interrupt Pin: 01 Line: 07 Min Gnt: 00 Max Lat: 00
     0x0040: Capability 0x09: Vendor Specific
     0x0058: Capability 0x09: Vendor Specific
     0x0070: Capability 0x09: Vendor Specific
     0x0088: Capability 0x09: Vendor Specific
     0x0000: 10421af4 00100107 01000001 00000000
     0x0010: 00004001 00000000 00000000 00000000
     0x0020: 00000000 00000000 00000000 00020b5d
     0x0030: 00000000 00000040 00000000 00000107
     0x0040: 01105809 00000000 00000000 00000038
     0x0050: 00000000 00000000 04107009 00000000
     0x0060: 00000300 00000018 00000000 00000000
     0x0070: 03108809 00000000 00000200 00000001
     0x0080: 00000000 00000000 02100009 00000000
     0x0090: 00000100 00000002 00000000 00000000
     0x00a0: 00000000 00000000 00000000 00000000
     0x00b0: 00000000 00000000 00000000 00000000
     0x00c0: 00000000 00000000 00000000 00000000
     0x00d0: 00000000 00000000 00000000 00000000
     0x00e0: 00000000 00000000 00000000 00000000
     0x00f0: 00000000 00000000 00000000 00000000
  0:5:0: OpenBSD VMM Control
     0x0000: Vendor ID: 0b5d, Product ID: 0777
     0x0004: Command: 0107, Status: 0000
     0x0008:    Class: 07 Communications, Subclass: 80 Miscellaneous,
         Interface: 00, Revision: 00
     0x000c: BIST: 00, Header Type: 00, Latency Timer: 00,
         Cache Line Size: 00
     0x0010: BAR io addr: 0x00005000/0x1000
     0x0014: BAR empty (00000000)
     0x0018: BAR empty (00000000)
     0x001c: BAR empty (00000000)
     0x0020: BAR empty (00000000)
     0x0024: BAR empty (00000000)
     0x0028: Cardbus CIS: 00000000
     0x002c: Subsystem Vendor ID: 0b5d Product ID: ffff
     0x0030: Expansion ROM Base Address: 00000000
     0x0038: 00000000
     0x003c: Interrupt Pin: 01 Line: 09 Min Gnt: 00 Max Lat: 00
     0x0000: 07770b5d 00000107 07800000 00000000
     0x0010: 00005001 00000000 00000000 00000000
     0x0020: 00000000 00000000 00000000 ffff0b5d
     0x0030: 00000000 00000000 00000000 00000109
     0x0040: 00000000 00000000 00000000 00000000
     0x0050: 00000000 00000000 00000000 00000000
     0x0060: 00000000 00000000 00000000 00000000
     0x0070: 00000000 00000000 00000000 00000000
     0x0080: 00000000 00000000 00000000 00000000
     0x0090: 00000000 00000000 00000000 00000000
     0x00a0: 00000000 00000000 00000000 00000000
     0x00b0: 00000000 00000000 00000000 00000000
     0x00c0: 00000000 00000000 00000000 00000000
     0x00d0: 00000000 00000000 00000000 00000000
     0x00e0: 00000000 00000000 00000000 00000000
     0x00f0: 00000000 00000000 00000000 00000000

 acpidump:

Reply via email to