Booting with "debug=y" works better, as then the initramfs debug goes right on the console, instead of /run/initramfs/initramfs.debug. This shows that even the initrd starts after the error message, so this must come from the kernel itself:
Loading Linux 4.4.0-8-generic ... Loading initial ramdisk ... OF stdout device is: /vdevice/vty@30000000 Preparing to boot Linux version 4.4.0-8-generic (buildd@bos01-ppc64el-008) (gcc version 5.3.1 20160222 (Ubuntu/IBM 5.3.1-9ubuntu3) ) #23-Ubuntu SMP Wed Feb 24 20:43:54 UTC 2016 (Ubuntu 4.4.0-8.23-generic 4.4.2) Detected machine type: 0000000000000101 Max number of cores passed to firmware: 2048 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done command line: BOOT_IMAGE=/boot/vmlinux-4.4.0-8-generic root=UUID=9f6cb10b-904a-4b22-b9e1-80455f176cc2 ro console=hvc0 earlyprintk debug=y memory layout at init: memory_limit : 0000000000000000 (16 MB aligned) alloc_bottom : 0000000005860000 alloc_top : 0000000030000000 alloc_top_hi : 0000000080000000 rmo_top : 0000000030000000 ram_top : 0000000080000000 instantiating rtas at 0x000000002fff0000... done prom_hold_cpus: skipped copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x0000000005870000 -> 0x0000000005870849 Device tree struct 0x0000000005880000 -> 0x0000000005890000 Quiescing Open Firmware ... Booting Linux via __start() ... [ 0.000000] Allocated 4980736 bytes for 2048 pacas at c00000000fb40000 [ 0.000000] Using pSeries machine description [... only kernel messages here ...] [ 0.633920] hctosys: unable to open rtc device (rtc0) [ 0.634546] Freeing unused kernel memory: 6144K (c000000000e80000 - c000000001480000) Loading, please wait... + [ -z ] + BOOT=local + [ -n ] + resume= + maybe_break top + export BOOT + run_scripts /scripts/init-top ** Package changed: initramfs-tools (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1410604 Title: ISST-LTE: unable to open rtc device Status in linux package in Ubuntu: Triaged Bug description: == Comment: #0 - Chanh H. Nguyen <chngu...@us.ibm.com> - 2015-01-09 17:30:08 == We use DVD to install Ubuntu 15.04 kernel 3.18.0-8-generic version on our PowerVM system. After install, I am seeing this error "/build/buildd/linux-3.18.0/drivers/rtc/hctosys.c: unable to open rtc device" on the dmesg log... root@pole1lp3:~# uname -a Linux pole1lp3 3.18.0-8-generic #9-Ubuntu SMP Mon Jan 5 22:52:15 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux root@pole1lp3:~# dmesg |grep rtc [ 0.556763] /build/buildd/linux-3.18.0/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 3.296241] rtc-generic rtc-generic: rtc core: registered rtc-generic as rtc0 root@pole1lp3:~# == Comment: #2 - David Heller <helle...@us.ibm.com> - 2015-01-13 20:53:50 == It must be an order of operations thing: something is trying to do the hctosys before the driver is loaded. A few seconds later the driver loads and it seems fine after that. root@pole1lp3:~# dmesg | grep rtc [ 0.551202] /build/buildd/linux-3.18.0/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 3.353719] rtc-generic rtc-generic: rtc core: registered rtc-generic as rtc0 root@pole1lp3:~# find /dev -name \*rtc\* /dev/rtc /dev/rtc0 root@pole1lp3:~# hwclock Tue 13 Jan 2015 07:36:15 PM CST -0.779773 seconds root@pole1lp3:~# hwclock --hctosys root@pole1lp3:~# date Tue Jan 13 19:38:05 CST 2015 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1410604/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
