[Macchiato] events_power_efficient sync_cmos_clock
Marcin Wojtas
mw at semihalf.com
Thu Mar 1 23:16:30 GMT 2018
Hi Stuart,
2018-03-01 23:31 GMT+01:00 Stuart Monteith <stoo at stoo.me.uk>:
> I’m thinking this firmware image has some problems.
>
> I’ll repeat the errors I’ve seem before:
>
> [ 34.915041] Unable to handle kernel paging request at virtual address f0512014
> [ 34.922307] Mem abort info:
> [ 34.925119] ESR = 0x96000005
> [ 34.928191] Exception class = DABT (current EL), IL = 32 bits
> [ 34.934140] SET = 0, FnV = 0
> [ 34.937214] EA = 0, S1PTW = 0
> [ 34.940373] Data abort info:
> [ 34.943270] ISV = 0, ISS = 0x00000005
> [ 34.947126] CM = 0, WnR = 0
> [ 34.950106] user pgtable: 4k pages, 48-bit VAs, pgd = 00000000ade66294
> [ 34.956666] [00000000f0512014] *pgd=0000000000000000
> [ 34.961661] Internal error: Oops: 96000005 [#1] SMP
>
> [ 35.036639] pstate: 80000005 (Nzcv daif -PAN -UAO)
> [ 35.041450] pc : 0x202610d4
> [ 35.044255] lr : 0x202611d4
> [ 35.047059] sp : ffff000009dc39a0
> [ 35.050386] x29: ffff000009dc3c50 x28: 0000000000000000
> [ 35.055722] x27: 0000000000000000 x26: ffff3b5ab29bd6c8
> [ 35.061056] x25: 0000000000000000 x24: 0000000000000001
> [ 35.066392] x23: 00000000000007e2 x22: 0000000000258243
> [ 35.071726] x21: 0000000000000003 x20: 0000000080000000
> [ 35.077061] x19: 000000002026299d x18: 0000ffffa0c41a50
> [ 35.082396] x17: 0000ffffa0bbe228 x16: ffff3b5ab229b798
> [ 35.087731] x15: 0000112fd8000000 x14: 00026a8d45000000
> [ 35.093066] x13: 0000000000000002 x12: 0000000000000018
> [ 35.098400] x11: 0000000000000020 x10: 0000000000000001
> [ 35.103736] x9 : 0000000000000002 x8 : ffff000009dc3b48
> [ 35.109071] x7 : ffff000009dc3a30 x6 : 0000000000000000
> [ 35.114405] x5 : 000000000000002b x4 : 00000000f0512000
> [ 35.119740] x3 : 000000000000002b x2 : 0000000000000001
> [ 35.125075] x1 : 0000000000000014 x0 : 00000000f0512000
> [ 35.130411] Process kworker/2:1 (pid: 53, stack limit = 0x00000000a959289c)
> [ 35.137402] Call trace:
> [ 35.139858] 0x202610d4
> [ 35.142317] efi_set_time+0x8c/0xb8
> [ 35.145819] rtc_set_time+0x80/0x138
> [ 35.149409] rtc_set_ntp_time+0xc4/0x140
> [ 35.153347] sync_hw_clock+0x7c/0x160
> [ 35.157024] process_one_work+0x19c/0x3e0
> [ 35.161048] worker_thread+0x54/0x440
> [ 35.164726] kthread+0x134/0x138
> [ 35.167967] ret_from_fork+0x10/0x1c
> [ 35.171557] Code: 38206822 2a0203e0 d65f03c0 d37ef421 (38606820)
> [ 35.177676] ---[ end trace 92030962cc0ea356 ]—
>
I've just tried RTC efi with ubuntu 2016.04 and buildroot, all works
fine, so the issue is pretty awkward:
[ 2.310833] rtc-efi rtc-efi: setting system clock to 2018-03-01
23:09:28 UTC (1519945768)
[...]
# date
Thu Mar 1 23:09:53 UTC 2018
# date 111111112017
Sat Nov 11 11:11:00 UTC 2017
# hwclock -w
# hwclock -r
Sat Nov 11 11:11:06 2017 0.000000 seconds
# date
Sat Nov 11 11:11:09 UTC 2017
>
> When configuring a new grub configuration, there is a hang reading from /sys/firmware/efi/vars :
>
> root 771 594 0 21:08 pts/0 00:00:00 sudo apt-get dist-upgrade
> root 772 771 0 21:08 pts/0 00:00:01 apt-get dist-upgrade
> root 907 772 0 21:08 pts/1 00:00:00 /usr/bin/dpkg --status-fd 13 --no-triggers --force-depends --remove linux-image-4.14.0-2-arm64:arm64
> root 908 907 0 21:08 pts/1 00:00:00 /bin/sh -e /var/lib/dpkg/info/linux-image-4.14.0-2-arm64.postrm remove
> root 911 908 0 21:08 pts/1 00:00:00 run-parts --report --exit-on-error --arg=4.14.0-2-arm64 --arg=/boot/vmlinuz-4.14.0-2-arm64 /etc/kernel/postrm.d
> root 918 911 0 21:08 pts/1 00:00:00 /bin/sh /usr/sbin/grub-mkconfig -o /boot/grub/grub.cfg
> root 1735 918 0 21:08 pts/1 00:00:00 /bin/sh /etc/grub.d/30_uefi-firmware
> root 1737 1735 0 21:08 pts/1 00:00:00 /bin/sh /etc/grub.d/30_uefi-firmware
> root 1738 1737 0 21:08 pts/1 00:00:00 /bin/sh /etc/grub.d/30_uefi-firmware
> root 1739 1738 0 21:08 pts/1 00:00:00 cat /sys/firmware/efi/vars/OsIndicationsSupported-8be4df61-93ca-11d2-aa0d-00e098032b8c/data
> root 1740 1738 0 21:08 pts/1 00:00:00 cut -b1
>
>~
The image I sent to Leif was most likely with no variables, so maybe
this is the reason.
Can you please provide me with the debian image you use and full
bootlog from reset to rootfs, including RTC errors?
Thanks,
Marcin
More information about the Macchiato
mailing list