search for: c1bl

Problems start before any of the kaiser code executes, though it could still be related to CONFIG_KAISER since that has effects beyond kaiser.c. --- (early) Initializing cgroup subsys cpuset (early) Initializing cgroup subsys cpu (early) Linux version 2.6.32-696.18.7.el6.x86_64 (mockbuild at c1bl.rdu2.centos.org) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-18) (GCC) ) #1 SMP Thu Jan 4 17:31:22 UTC 2018 (early) Command line: ro console=hvc0 rootflags=barrier=0 crashkernel=auto SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us earlyprintk=xen (early) KERNEL supported cpus: (early) Intel...

...>] x86_64_start_reservations+0x125 [<ffffffff81c4309c>] xen_start_kernel+0x4fe And my domU has similar boot messages as Sarah Newman's: (early) Initializing cgroup subsys cpuset (early) Initializing cgroup subsys cpu (early) Linux version 2.6.32-696.18.7.el6.x86_64 (mockbuild at c1bl.rdu2.centos.org) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-18) (GCC) ) #1 SMP Thu Jan 4 17:31:22 UTC 2018 (early) Command line: ro root=/dev/xvda3 rd_NO_LUKS rd_NO_LVM rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto LANG=en_US.UTF-8 KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM earlyprintk=xen (hd0,0)...

...the kaiser code executes, though it could >still be related to CONFIG_KAISER since that has effects beyond >kaiser.c. > >--- >(early) Initializing cgroup subsys cpuset >(early) Initializing cgroup subsys cpu >(early) Linux version 2.6.32-696.18.7.el6.x86_64 >(mockbuild at c1bl.rdu2.centos.org) (gcc version 4.4.7 20120313 (Red Hat >4.4.7-18) (GCC) ) #1 SMP Thu >Jan 4 17:31:22 UTC 2018 >(early) Command line: ro console=hvc0 rootflags=barrier=0 >crashkernel=auto SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us >earlyprintk=xen >(early) KERNEL supp...