Re: [yocto] Error during linux booting

2022-10-21 Thread Khem Raj 
On Fri, Oct 21, 2022 at 10:38 AM Zoran Stojsavljevic
 wrote:
>
> > For enabling systemd its best to start with
> > DISTRO = "poky-altcfg"
>
> With all due respect, Khem, I thought that this line in local.conf
> makes systemd as default?!
> INIT_MANAGER ?= "systemd"

yes that will do it. Infact thats what poky-altconfig does largely as well. see
https://git.yoctoproject.org/poky/tree/meta-poky/conf/distro/poky-altcfg.conf#n11

>
> >> Hello Zoran
> >> Yes, i have set INIT_MANAGER ?= "systemd"
>
> Zee
> ___
>
> On Fri, Oct 21, 2022 at 6:28 PM Khem Raj  wrote:
> >
> > If you are using poky then ssytemd is not default init system, its
> > sysvinit. For enabling systemd its best to start with
> >
> > DISTRO = "poky-altcfg"
> >
> > On Sun, Oct 16, 2022 at 11:32 AM Vaibhav Deshpande
> >  wrote:
> > >
> > > Hello
> > >
> > > I am trying to build a yocto image from the kirkstone branch 
> > > (https://github.com/openembedded/openembedded-core/tree/kirkstone) build 
> > > gets successful but at the time of linux booting I am getting below error.
> > >
> > > [0.00] Linux version 5.19.0-rc4 (oe-user@oe-host) 
> > > (riscv64-oe-linux-gcc (GCC) 11.3.0, GNU ld (GNU Binutils) 2.38.20220708) 
> > > #1 SMP Wed Aug 24 14:46:22 UTC 2022
> > > [0.00] random: crng init done
> > > [0.00] Machine model: Ventana VT1 QEMU
> > > [0.00] SBI specification v1.0 detected
> > > [0.00] SBI implementation ID=0x1 Version=0x10001
> > > [0.00] SBI TIME extension detected
> > > [0.00] SBI IPI extension detected
> > > [0.00] SBI RFENCE extension detected
> > > [0.00] SBI SRST extension detected
> > > [0.00] earlycon: uart8250 at MMIO 0x1000 (options '')
> > > [0.00] printk: bootconsole [uart8250] enabled
> > > [0.00] efi: EFI v2.90 by Das U-Boot
> > > [0.00] efi: RTPROP=0xfe73c020 SMBIOS=0xfe738000 
> > > MEMRESERVE=0xfd3ca020
> > > [0.00] Zone ranges:
> > > [0.00]   DMA32[mem 0x8000-0x]
> > > [0.00]   Normal   empty
> > > [0.00] Movable zone start for each node
> > > [0.00] Early memory node ranges
> > > [0.00]   node   0: [mem 0x8000-0xfe737fff]
> > > [0.00]   node   0: [mem 0xfe738000-0xfe738fff]
> > > [0.00]   node   0: [mem 0xfe739000-0xfe73bfff]
> > > [0.00]   node   0: [mem 0xfe73c000-0xfe742fff]
> > > [0.00]   node   0: [mem 0xfe743000-0xfff77fff]
> > > [0.00]   node   0: [mem 0xfff78000-0xfff78fff]
> > > [0.00]   node   0: [mem 0xfff79000-0x]
> > > [0.00] Initmem setup node 0 [mem 
> > > 0x8000-0x]
> > > [0.00] SBI HSM extension detected
> > > [0.00] riscv: base ISA extensions acdfhim
> > > [0.00] riscv: ELF capabilities acdfim
> > > [0.00] riscv: Svinval extension supported
> > > [0.00] percpu: Embedded 18 pages/cpu s34488 r8192 d31048 u73728
> > > [0.00] Built 1 zonelists, mobility grouping on.  Total pages: 
> > > 516096
> > > [0.00] Kernel command line: root=/dev/vda2 rootwait console=ttyS0 
> > > earlycon=uart8250,mmio,0x1000
> > > [0.00] Dentry cache hash table entries: 262144 (order: 9, 2097152 
> > > bytes, linear)
> > > [0.00] Inode-cache hash table entries: 131072 (order: 8, 1048576 
> > > bytes, linear)
> > > [0.00] mem auto-init: stack:off, heap alloc:off, heap free:off
> > > [0.00] Virtual kernel memory layout:
> > > [0.00]   fixmap : 0xff1bfee0 - 0xff1bff00   
> > > (2048 kB)
> > > [0.00]   pci io : 0xff1bff00 - 0xff1c   ( 
> > >  16 MB)
> > > [0.00]  vmemmap : 0xff1c - 0xff20   
> > > (1024 TB)
> > > [0.00]  vmalloc : 0xff20 - 0xff60   
> > > (16384 TB)
> > > [0.00]   lowmem : 0xff60 - 0xff608000   
> > > (2048 MB)
> > > [0.00]   kernel : 0x8000 - 0x   
> > > (2047 MB)
> > > [0.00] Memory: 2034884K/2097152K available (7677K kernel code, 
> > > 4908K rwdata, 4096K rodata, 2204K init, 463K bss, 62268K reserved, 0K 
> > > cma-reserved)
> > > [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=1
> > > [0.00] rcu: Hierarchical RCU implementation.
> > > [0.00] rcu: RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=16.
> > > [0.00] rcu: RCU debug extended QS entry/exit.
> > > [0.00] Tracing variant of Tasks RCU enabled.
> > > [0.00] rcu: RCU calculated value of scheduler-enlistment delay is 
> > > 25 jiffies.
> > > [0.00] rcu: Adjusting geometry for rcu_fanout_leaf=16, 
> > > nr_cpu_ids=16
> > > [0.00] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
> >

Re: [yocto] Error during linux booting

2022-10-21 Thread Zoran 
> For enabling systemd its best to start with
> DISTRO = "poky-altcfg"

With all due respect, Khem, I thought that this line in local.conf
makes systemd as default?!
INIT_MANAGER ?= "systemd"

>> Hello Zoran
>> Yes, i have set INIT_MANAGER ?= "systemd"

Zee
___

On Fri, Oct 21, 2022 at 6:28 PM Khem Raj  wrote:
>
> If you are using poky then ssytemd is not default init system, its
> sysvinit. For enabling systemd its best to start with
>
> DISTRO = "poky-altcfg"
>
> On Sun, Oct 16, 2022 at 11:32 AM Vaibhav Deshpande
>  wrote:
> >
> > Hello
> >
> > I am trying to build a yocto image from the kirkstone branch 
> > (https://github.com/openembedded/openembedded-core/tree/kirkstone) build 
> > gets successful but at the time of linux booting I am getting below error.
> >
> > [0.00] Linux version 5.19.0-rc4 (oe-user@oe-host) 
> > (riscv64-oe-linux-gcc (GCC) 11.3.0, GNU ld (GNU Binutils) 2.38.20220708) #1 
> > SMP Wed Aug 24 14:46:22 UTC 2022
> > [0.00] random: crng init done
> > [0.00] Machine model: Ventana VT1 QEMU
> > [0.00] SBI specification v1.0 detected
> > [0.00] SBI implementation ID=0x1 Version=0x10001
> > [0.00] SBI TIME extension detected
> > [0.00] SBI IPI extension detected
> > [0.00] SBI RFENCE extension detected
> > [0.00] SBI SRST extension detected
> > [0.00] earlycon: uart8250 at MMIO 0x1000 (options '')
> > [0.00] printk: bootconsole [uart8250] enabled
> > [0.00] efi: EFI v2.90 by Das U-Boot
> > [0.00] efi: RTPROP=0xfe73c020 SMBIOS=0xfe738000 
> > MEMRESERVE=0xfd3ca020
> > [0.00] Zone ranges:
> > [0.00]   DMA32[mem 0x8000-0x]
> > [0.00]   Normal   empty
> > [0.00] Movable zone start for each node
> > [0.00] Early memory node ranges
> > [0.00]   node   0: [mem 0x8000-0xfe737fff]
> > [0.00]   node   0: [mem 0xfe738000-0xfe738fff]
> > [0.00]   node   0: [mem 0xfe739000-0xfe73bfff]
> > [0.00]   node   0: [mem 0xfe73c000-0xfe742fff]
> > [0.00]   node   0: [mem 0xfe743000-0xfff77fff]
> > [0.00]   node   0: [mem 0xfff78000-0xfff78fff]
> > [0.00]   node   0: [mem 0xfff79000-0x]
> > [0.00] Initmem setup node 0 [mem 
> > 0x8000-0x]
> > [0.00] SBI HSM extension detected
> > [0.00] riscv: base ISA extensions acdfhim
> > [0.00] riscv: ELF capabilities acdfim
> > [0.00] riscv: Svinval extension supported
> > [0.00] percpu: Embedded 18 pages/cpu s34488 r8192 d31048 u73728
> > [0.00] Built 1 zonelists, mobility grouping on.  Total pages: 516096
> > [0.00] Kernel command line: root=/dev/vda2 rootwait console=ttyS0 
> > earlycon=uart8250,mmio,0x1000
> > [0.00] Dentry cache hash table entries: 262144 (order: 9, 2097152 
> > bytes, linear)
> > [0.00] Inode-cache hash table entries: 131072 (order: 8, 1048576 
> > bytes, linear)
> > [0.00] mem auto-init: stack:off, heap alloc:off, heap free:off
> > [0.00] Virtual kernel memory layout:
> > [0.00]   fixmap : 0xff1bfee0 - 0xff1bff00   
> > (2048 kB)
> > [0.00]   pci io : 0xff1bff00 - 0xff1c   (  
> > 16 MB)
> > [0.00]  vmemmap : 0xff1c - 0xff20   
> > (1024 TB)
> > [0.00]  vmalloc : 0xff20 - 0xff60   
> > (16384 TB)
> > [0.00]   lowmem : 0xff60 - 0xff608000   
> > (2048 MB)
> > [0.00]   kernel : 0x8000 - 0x   
> > (2047 MB)
> > [0.00] Memory: 2034884K/2097152K available (7677K kernel code, 
> > 4908K rwdata, 4096K rodata, 2204K init, 463K bss, 62268K reserved, 0K 
> > cma-reserved)
> > [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=1
> > [0.00] rcu: Hierarchical RCU implementation.
> > [0.00] rcu: RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=16.
> > [0.00] rcu: RCU debug extended QS entry/exit.
> > [0.00] Tracing variant of Tasks RCU enabled.
> > [0.00] rcu: RCU calculated value of scheduler-enlistment delay is 
> > 25 jiffies.
> > [0.00] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=16
> > [0.00] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
> > [0.00] riscv-intc: 64 local interrupts mapped using AIA
> > [0.00] riscv-imsic: imsics@2800:  hart-index-bits: 4,  
> > guest-index-bits: 3
> > [0.00] riscv-imsic: imsics@2800: group-index-bits: 0, 
> > group-index-shift: 24
> > [0.00] riscv-imsic: imsics@2800: mapped 255 interrupts for 16 
> > CPUs at 0x2800
> > [0.00] riscv-imsic: imsics@2800: enable/disable

Re: [yocto] Error during linux booting

2022-10-21 Thread Khem Raj 
If you are using poky then ssytemd is not default init system, its
sysvinit. For enabling systemd its best to start with

DISTRO = "poky-altcfg"

On Sun, Oct 16, 2022 at 11:32 AM Vaibhav Deshpande
 wrote:
>
> Hello
>
> I am trying to build a yocto image from the kirkstone branch 
> (https://github.com/openembedded/openembedded-core/tree/kirkstone) build gets 
> successful but at the time of linux booting I am getting below error.
>
> [0.00] Linux version 5.19.0-rc4 (oe-user@oe-host) 
> (riscv64-oe-linux-gcc (GCC) 11.3.0, GNU ld (GNU Binutils) 2.38.20220708) #1 
> SMP Wed Aug 24 14:46:22 UTC 2022
> [0.00] random: crng init done
> [0.00] Machine model: Ventana VT1 QEMU
> [0.00] SBI specification v1.0 detected
> [0.00] SBI implementation ID=0x1 Version=0x10001
> [0.00] SBI TIME extension detected
> [0.00] SBI IPI extension detected
> [0.00] SBI RFENCE extension detected
> [0.00] SBI SRST extension detected
> [0.00] earlycon: uart8250 at MMIO 0x1000 (options '')
> [0.00] printk: bootconsole [uart8250] enabled
> [0.00] efi: EFI v2.90 by Das U-Boot
> [0.00] efi: RTPROP=0xfe73c020 SMBIOS=0xfe738000 MEMRESERVE=0xfd3ca020
> [0.00] Zone ranges:
> [0.00]   DMA32[mem 0x8000-0x]
> [0.00]   Normal   empty
> [0.00] Movable zone start for each node
> [0.00] Early memory node ranges
> [0.00]   node   0: [mem 0x8000-0xfe737fff]
> [0.00]   node   0: [mem 0xfe738000-0xfe738fff]
> [0.00]   node   0: [mem 0xfe739000-0xfe73bfff]
> [0.00]   node   0: [mem 0xfe73c000-0xfe742fff]
> [0.00]   node   0: [mem 0xfe743000-0xfff77fff]
> [0.00]   node   0: [mem 0xfff78000-0xfff78fff]
> [0.00]   node   0: [mem 0xfff79000-0x]
> [0.00] Initmem setup node 0 [mem 
> 0x8000-0x]
> [0.00] SBI HSM extension detected
> [0.00] riscv: base ISA extensions acdfhim
> [0.00] riscv: ELF capabilities acdfim
> [0.00] riscv: Svinval extension supported
> [0.00] percpu: Embedded 18 pages/cpu s34488 r8192 d31048 u73728
> [0.00] Built 1 zonelists, mobility grouping on.  Total pages: 516096
> [0.00] Kernel command line: root=/dev/vda2 rootwait console=ttyS0 
> earlycon=uart8250,mmio,0x1000
> [0.00] Dentry cache hash table entries: 262144 (order: 9, 2097152 
> bytes, linear)
> [0.00] Inode-cache hash table entries: 131072 (order: 8, 1048576 
> bytes, linear)
> [0.00] mem auto-init: stack:off, heap alloc:off, heap free:off
> [0.00] Virtual kernel memory layout:
> [0.00]   fixmap : 0xff1bfee0 - 0xff1bff00   (2048 
> kB)
> [0.00]   pci io : 0xff1bff00 - 0xff1c   (  16 
> MB)
> [0.00]  vmemmap : 0xff1c - 0xff20   (1024 
> TB)
> [0.00]  vmalloc : 0xff20 - 0xff60   
> (16384 TB)
> [0.00]   lowmem : 0xff60 - 0xff608000   (2048 
> MB)
> [0.00]   kernel : 0x8000 - 0x   (2047 
> MB)
> [0.00] Memory: 2034884K/2097152K available (7677K kernel code, 4908K 
> rwdata, 4096K rodata, 2204K init, 463K bss, 62268K reserved, 0K cma-reserved)
> [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=1
> [0.00] rcu: Hierarchical RCU implementation.
> [0.00] rcu: RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=16.
> [0.00] rcu: RCU debug extended QS entry/exit.
> [0.00] Tracing variant of Tasks RCU enabled.
> [0.00] rcu: RCU calculated value of scheduler-enlistment delay is 25 
> jiffies.
> [0.00] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=16
> [0.00] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
> [0.00] riscv-intc: 64 local interrupts mapped using AIA
> [0.00] riscv-imsic: imsics@2800:  hart-index-bits: 4,  
> guest-index-bits: 3
> [0.00] riscv-imsic: imsics@2800: group-index-bits: 0, 
> group-index-shift: 24
> [0.00] riscv-imsic: imsics@2800: mapped 255 interrupts for 16 
> CPUs at 0x2800
> [0.00] riscv-imsic: imsics@2800: enable/disable sync using 
> interrupt 2
> [0.00] riscv-imsic: imsics@2800: providing IPIs using interrupt 1
> [0.00] rcu: srcu_init: Setting srcu_struct sizes based on contention.
> [0.00] riscv_timer_init_dt: Registering clocksource cpuid [0] hartid 
> [15]
> [0.00] clocksource: riscv_clocksource: mask: 0x 
> max_cycles: 0x24e6a1710, max_idle_ns: 440795202120 ns
> [0.000175] sched_clock: 64 bits at 10MHz, resolution 100ns, wraps every 
> 4398046511100ns
>

Re: [yocto] Error during linux booting

2022-10-21 Thread Vaibhav Deshpande 
Hello Laurent

I am building for qemuriscv64

Command :-
MACHINE=qemuriscv64 bitbake core-image-full-cmdline


Thank you.

Regards
Vaibhav Vivek Deshpande


On Thu, Oct 20, 2022 at 11:00 PM Laurent Gauthier <
laurent.gauth...@soccasys.com> wrote:

> Hi Vaibhav,
>
> Out of curiosity which image did you build?
>
> Kind regards, Laurent.
>
> On Thu, Oct 20, 2022 at 7:07 PM Vaibhav Deshpande
>  wrote:
> >
> > Helo
> >
> > I have added systemd in rootfs by adding IMAGE_INSTALL = " systemd" in
> local.conf and the issue solved
> > is this required for the latest yocto version (kirkstone)?
> >
> >
> > Thank you.
> >
> > Regards
> > Vaibhav Vivek Deshpande
> >
> >
> > On Mon, Oct 17, 2022 at 1:28 AM Zoran Stojsavljevic <
> zoran.stojsavlje...@gmail.com> wrote:
> >>
> >> Interesting... Looking into the log massage itself!
> >>
> >> > [0.00] Kernel command line: root=/dev/vda2 rootwait
> console=ttyS0 earlycon=uart8250,mmio,0x1000
> >>
> >> Command line does not specify baud rate... Usually by default it is
> >> 115200. Just a kludge.
> >>
> >> Then:
> >>
> >> > [0.00] earlycon: uart8250 at MMIO 0x1000 (options
> '')
> >> > [0.00] printk: bootconsole [uart8250] enabled
> >>
> >> bootconsole enabled, seems correct.
> >>
> >> Then:
> >>
> >> > [1.628806] Serial: 8250/16550 driver, 4 ports, IRQ sharing
> disabled
> >> > [1.648238] printk: console [ttyS0] disabled
> >> > [1.652252] 1000.uart: ttyS0 at MMIO 0x1000 (irq = 166,
> base_baud = 230400) is a 16550A
> >> > [1.656816] printk: console [ttyS0] enabled
> >> > [1.656816] printk: console [ttyS0] enabled
> >> > [1.657728] printk: bootconsole [uart8250] disabled
> >> > [1.657728] printk: bootconsole [uart8250] disabled
> >>
> >> From what we see that the base baud rate is 230400 (?), everything
> >> else is, seems, correct.
> >>
> >> So, three things, which came adhoc to my mind:
> >> [1] Please, check the baud rate;
> >> [2] Please, check to which group /dev/ttyS0 belongs (root dialout)?
> >> [3] The terminal should be interactive, but no way to check this (from
> >> the logs)???
> >>
> >> My two cent worth answer,
> >> Zee
> >> ___
> >>
> >> On Sun, Oct 16, 2022 at 8:32 PM Vaibhav Deshpande
> >>  wrote:
> >> >
> >> > Hello
> >> >
> >> > I am trying to build a yocto image from the kirkstone branch (
> https://github.com/openembedded/openembedded-core/tree/kirkstone) build
> gets successful but at the time of linux booting I am getting below error.
> >>
> >> ...[snap]...
> >
> >
> > 
> >
>
>
> --
> Laurent Gauthier
> Embedded Linux Systems & Software
> Phone: +33 630 483 429
> https://soccasys.com
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58389): https://lists.yoctoproject.org/g/yocto/message/58389
Mute This Topic: https://lists.yoctoproject.org/mt/94368916/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Error during linux booting

2022-10-21 Thread Vaibhav Deshpande 
Hello Zoran

Yes, i have set INIT_MANAGER ?= "systemd"

it does not related to console but init

Failure logs : -

sh-5.1# ls -l /sbin/init
ls: cannot access '/sbin/init': No such file or directory

sh-5.1# ls -l /lib/systemd/
total 8
drwxr-xr-x 2 root root 4096 Mar  9  2018 system
drwxr-xr-x 2 root root 4096 Mar  9  2018 system-preset


Working Logs (after adding IMAGE_INSTALL = " systemd") :-

root@qemuriscv64:/# ls -l /sbin/init
lrwxrwxrwx 1 root root 22 Mar  9  2018 /sbin/init -> ../lib/systemd/systemd

root@qemuriscv64:/# ls /lib/systemd/
journald.conf.d  system-shutdown  systemd-growfs
 systemd-network-generator  systemd-shutdown  systemd-update-done
libsystemd-shared-250.so  system-sleep  systemd-hibernate-resume
 systemd-networkd  systemd-sleep  systemd-update-helper
logind.conf.d  system.conf.d  systemd-hostnamed
 systemd-networkd-wait-online  systemd-socket-proxyd   systemd-update-utmp
network  systemd  systemd-initctlsystemd-pstore  systemd-sulogin-shell
  systemd-user-runtime-dir
ntp-units.d  systemd-ac-power  systemd-journaldsystemd-quotacheck
 systemd-sysctl  systemd-user-sessions
resolv.conf  systemd-backlight  systemd-localedsystemd-random-seed
 systemd-time-wait-sync  systemd-userdbd
system  systemd-boot-check-no-failures  systemd-logind
 systemd-remount-fs  systemd-timedated  systemd-userwork
system-generators  systemd-cgroups-agent  systemd-makefs
 systemd-reply-password  systemd-timesyncd  systemd-vconsole-setup
system-preset  systemd-fsck  systemd-modules-loadsystemd-resolved
 systemd-udevd  systemd-volatile-root
root@qemuriscv64:/#


Thank you

Regards
Vaibhav Vivek Deshpande


On Fri, Oct 21, 2022 at 5:18 AM Zoran Stojsavljevic <
zoran.stojsavlje...@gmail.com> wrote:

> > I have added systemd in rootfs by adding
> > MAGE_INSTALL = " systemd" in local.conf
> > and the issue solved is this required for the
> > latest yocto version (kirkstone)?
>
> You did set the INIT_MANAGER ?= "systemd", didn't you?
>
> And how (in which manner) systemd influences the console, or consoles
> setup?
>
> Consoles' setup should be done much earlier then systemd!?
>
> Zee
> ___
>
> On Thu, Oct 20, 2022 at 7:07 PM Vaibhav Deshpande
>  wrote:
> >
> > Helo
> >
> > I have added systemd in rootfs by adding IMAGE_INSTALL = " systemd" in
> local.conf and the issue solved
> > is this required for the latest yocto version (kirkstone)?
> >
> >
> > Thank you.
> >
> > Regards
> > Vaibhav Vivek Deshpande
> >
> >
> > On Mon, Oct 17, 2022 at 1:28 AM Zoran Stojsavljevic <
> zoran.stojsavlje...@gmail.com> wrote:
> >>
> >> Interesting... Looking into the log massage itself!
> >>
> >> > [0.00] Kernel command line: root=/dev/vda2 rootwait
> console=ttyS0 earlycon=uart8250,mmio,0x1000
> >>
> >> Command line does not specify baud rate... Usually by default it is
> >> 115200. Just a kludge.
> >>
> >> Then:
> >>
> >> > [0.00] earlycon: uart8250 at MMIO 0x1000 (options
> '')
> >> > [0.00] printk: bootconsole [uart8250] enabled
> >>
> >> bootconsole enabled, seems correct.
> >>
> >> Then:
> >>
> >> > [1.628806] Serial: 8250/16550 driver, 4 ports, IRQ sharing
> disabled
> >> > [1.648238] printk: console [ttyS0] disabled
> >> > [1.652252] 1000.uart: ttyS0 at MMIO 0x1000 (irq = 166,
> base_baud = 230400) is a 16550A
> >> > [1.656816] printk: console [ttyS0] enabled
> >> > [1.656816] printk: console [ttyS0] enabled
> >> > [1.657728] printk: bootconsole [uart8250] disabled
> >> > [1.657728] printk: bootconsole [uart8250] disabled
> >>
> >> From what we see that the base baud rate is 230400 (?), everything
> >> else is, seems, correct.
> >>
> >> So, three things, which came adhoc to my mind:
> >> [1] Please, check the baud rate;
> >> [2] Please, check to which group /dev/ttyS0 belongs (root dialout)?
> >> [3] The terminal should be interactive, but no way to check this (from
> >> the logs)???
> >>
> >> My two cent worth answer,
> >> Zee
> >> ___
> >>
> >> On Sun, Oct 16, 2022 at 8:32 PM Vaibhav Deshpande
> >>  wrote:
> >> >
> >> > Hello
> >> >
> >> > I am trying to build a yocto image from the kirkstone branch (
> https://github.com/openembedded/openembedded-core/tree/kirkstone) build
> gets successful but at the time of linux booting I am getting below error.
> >>
> >> ...[snap]...
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58388): https://lists.yoctoproject.org/g/yocto/message/58388
Mute This Topic: https://lists.yoctoproject.org/mt/94368916/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Error during linux booting

2022-10-20 Thread Zoran 
> I have added systemd in rootfs by adding
> MAGE_INSTALL = " systemd" in local.conf
> and the issue solved is this required for the
> latest yocto version (kirkstone)?

You did set the INIT_MANAGER ?= "systemd", didn't you?

And how (in which manner) systemd influences the console, or consoles setup?

Consoles' setup should be done much earlier then systemd!?

Zee
___

On Thu, Oct 20, 2022 at 7:07 PM Vaibhav Deshpande
 wrote:
>
> Helo
>
> I have added systemd in rootfs by adding IMAGE_INSTALL = " systemd" in 
> local.conf and the issue solved
> is this required for the latest yocto version (kirkstone)?
>
>
> Thank you.
>
> Regards
> Vaibhav Vivek Deshpande
>
>
> On Mon, Oct 17, 2022 at 1:28 AM Zoran Stojsavljevic 
>  wrote:
>>
>> Interesting... Looking into the log massage itself!
>>
>> > [0.00] Kernel command line: root=/dev/vda2 rootwait console=ttyS0 
>> > earlycon=uart8250,mmio,0x1000
>>
>> Command line does not specify baud rate... Usually by default it is
>> 115200. Just a kludge.
>>
>> Then:
>>
>> > [0.00] earlycon: uart8250 at MMIO 0x1000 (options '')
>> > [0.00] printk: bootconsole [uart8250] enabled
>>
>> bootconsole enabled, seems correct.
>>
>> Then:
>>
>> > [1.628806] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
>> > [1.648238] printk: console [ttyS0] disabled
>> > [1.652252] 1000.uart: ttyS0 at MMIO 0x1000 (irq = 166, 
>> > base_baud = 230400) is a 16550A
>> > [1.656816] printk: console [ttyS0] enabled
>> > [1.656816] printk: console [ttyS0] enabled
>> > [1.657728] printk: bootconsole [uart8250] disabled
>> > [1.657728] printk: bootconsole [uart8250] disabled
>>
>> From what we see that the base baud rate is 230400 (?), everything
>> else is, seems, correct.
>>
>> So, three things, which came adhoc to my mind:
>> [1] Please, check the baud rate;
>> [2] Please, check to which group /dev/ttyS0 belongs (root dialout)?
>> [3] The terminal should be interactive, but no way to check this (from
>> the logs)???
>>
>> My two cent worth answer,
>> Zee
>> ___
>>
>> On Sun, Oct 16, 2022 at 8:32 PM Vaibhav Deshpande
>>  wrote:
>> >
>> > Hello
>> >
>> > I am trying to build a yocto image from the kirkstone branch 
>> > (https://github.com/openembedded/openembedded-core/tree/kirkstone) build 
>> > gets successful but at the time of linux booting I am getting below error.
>>
>> ...[snap]...

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58387): https://lists.yoctoproject.org/g/yocto/message/58387
Mute This Topic: https://lists.yoctoproject.org/mt/94368916/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Error during linux booting

2022-10-20 Thread Laurent Gauthier 
Hi Vaibhav,

Out of curiosity which image did you build?

Kind regards, Laurent.

On Thu, Oct 20, 2022 at 7:07 PM Vaibhav Deshpande
 wrote:
>
> Helo
>
> I have added systemd in rootfs by adding IMAGE_INSTALL = " systemd" in 
> local.conf and the issue solved
> is this required for the latest yocto version (kirkstone)?
>
>
> Thank you.
>
> Regards
> Vaibhav Vivek Deshpande
>
>
> On Mon, Oct 17, 2022 at 1:28 AM Zoran Stojsavljevic 
>  wrote:
>>
>> Interesting... Looking into the log massage itself!
>>
>> > [0.00] Kernel command line: root=/dev/vda2 rootwait console=ttyS0 
>> > earlycon=uart8250,mmio,0x1000
>>
>> Command line does not specify baud rate... Usually by default it is
>> 115200. Just a kludge.
>>
>> Then:
>>
>> > [0.00] earlycon: uart8250 at MMIO 0x1000 (options '')
>> > [0.00] printk: bootconsole [uart8250] enabled
>>
>> bootconsole enabled, seems correct.
>>
>> Then:
>>
>> > [1.628806] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
>> > [1.648238] printk: console [ttyS0] disabled
>> > [1.652252] 1000.uart: ttyS0 at MMIO 0x1000 (irq = 166, 
>> > base_baud = 230400) is a 16550A
>> > [1.656816] printk: console [ttyS0] enabled
>> > [1.656816] printk: console [ttyS0] enabled
>> > [1.657728] printk: bootconsole [uart8250] disabled
>> > [1.657728] printk: bootconsole [uart8250] disabled
>>
>> From what we see that the base baud rate is 230400 (?), everything
>> else is, seems, correct.
>>
>> So, three things, which came adhoc to my mind:
>> [1] Please, check the baud rate;
>> [2] Please, check to which group /dev/ttyS0 belongs (root dialout)?
>> [3] The terminal should be interactive, but no way to check this (from
>> the logs)???
>>
>> My two cent worth answer,
>> Zee
>> ___
>>
>> On Sun, Oct 16, 2022 at 8:32 PM Vaibhav Deshpande
>>  wrote:
>> >
>> > Hello
>> >
>> > I am trying to build a yocto image from the kirkstone branch 
>> > (https://github.com/openembedded/openembedded-core/tree/kirkstone) build 
>> > gets successful but at the time of linux booting I am getting below error.
>>
>> ...[snap]...
>
>
> 
>


-- 
Laurent Gauthier
Embedded Linux Systems & Software
Phone: +33 630 483 429
https://soccasys.com

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58385): https://lists.yoctoproject.org/g/yocto/message/58385
Mute This Topic: https://lists.yoctoproject.org/mt/94368916/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Error during linux booting

2022-10-20 Thread Vaibhav Deshpande 
Helo

I have added systemd in rootfs by adding IMAGE_INSTALL = " systemd" in
local.conf and the issue solved
is this required for the latest yocto version (kirkstone)?


Thank you.

Regards
Vaibhav Vivek Deshpande


On Mon, Oct 17, 2022 at 1:28 AM Zoran Stojsavljevic <
zoran.stojsavlje...@gmail.com> wrote:

> Interesting... Looking into the log massage itself!
>
> > [0.00] Kernel command line: root=/dev/vda2 rootwait
> console=ttyS0 earlycon=uart8250,mmio,0x1000
>
> Command line does not specify baud rate... Usually by default it is
> 115200. Just a kludge.
>
> Then:
>
> > [0.00] earlycon: uart8250 at MMIO 0x1000 (options '')
> > [0.00] printk: bootconsole [uart8250] enabled
>
> bootconsole enabled, seems correct.
>
> Then:
>
> > [1.628806] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
> > [1.648238] printk: console [ttyS0] disabled
> > [1.652252] 1000.uart: ttyS0 at MMIO 0x1000 (irq = 166,
> base_baud = 230400) is a 16550A
> > [1.656816] printk: console [ttyS0] enabled
> > [1.656816] printk: console [ttyS0] enabled
> > [1.657728] printk: bootconsole [uart8250] disabled
> > [1.657728] printk: bootconsole [uart8250] disabled
>
> From what we see that the base baud rate is 230400 (?), everything
> else is, seems, correct.
>
> So, three things, which came adhoc to my mind:
> [1] Please, check the baud rate;
> [2] Please, check to which group /dev/ttyS0 belongs (root dialout)?
> [3] The terminal should be interactive, but no way to check this (from
> the logs)???
>
> My two cent worth answer,
> Zee
> ___
>
> On Sun, Oct 16, 2022 at 8:32 PM Vaibhav Deshpande
>  wrote:
> >
> > Hello
> >
> > I am trying to build a yocto image from the kirkstone branch (
> https://github.com/openembedded/openembedded-core/tree/kirkstone) build
> gets successful but at the time of linux booting I am getting below error.
>
> ...[snap]...
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58384): https://lists.yoctoproject.org/g/yocto/message/58384
Mute This Topic: https://lists.yoctoproject.org/mt/94368916/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Error during linux booting

2022-10-16 Thread Zoran 
Interesting... Looking into the log massage itself!

> [0.00] Kernel command line: root=/dev/vda2 rootwait console=ttyS0 
> earlycon=uart8250,mmio,0x1000

Command line does not specify baud rate... Usually by default it is
115200. Just a kludge.

Then:

> [0.00] earlycon: uart8250 at MMIO 0x1000 (options '')
> [0.00] printk: bootconsole [uart8250] enabled

bootconsole enabled, seems correct.

Then:

> [1.628806] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
> [1.648238] printk: console [ttyS0] disabled
> [1.652252] 1000.uart: ttyS0 at MMIO 0x1000 (irq = 166, base_baud 
> = 230400) is a 16550A
> [1.656816] printk: console [ttyS0] enabled
> [1.656816] printk: console [ttyS0] enabled
> [1.657728] printk: bootconsole [uart8250] disabled
> [1.657728] printk: bootconsole [uart8250] disabled

>From what we see that the base baud rate is 230400 (?), everything
else is, seems, correct.

So, three things, which came adhoc to my mind:
[1] Please, check the baud rate;
[2] Please, check to which group /dev/ttyS0 belongs (root dialout)?
[3] The terminal should be interactive, but no way to check this (from
the logs)???

My two cent worth answer,
Zee
___

On Sun, Oct 16, 2022 at 8:32 PM Vaibhav Deshpande
 wrote:
>
> Hello
>
> I am trying to build a yocto image from the kirkstone branch 
> (https://github.com/openembedded/openembedded-core/tree/kirkstone) build gets 
> successful but at the time of linux booting I am getting below error.

...[snap]...

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58345): https://lists.yoctoproject.org/g/yocto/message/58345
Mute This Topic: https://lists.yoctoproject.org/mt/94368916/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Error during linux booting

2022-10-16 Thread Vaibhav Deshpande 
Hello

I am trying to build a yocto image from the kirkstone branch (
https://github.com/openembedded/openembedded-core/tree/kirkstone) build
gets successful but at the time of linux booting I am getting below error.

[0.00] Linux version 5.19.0-rc4 (oe-user@oe-host)
(riscv64-oe-linux-gcc (GCC) 11.3.0, GNU ld (GNU Binutils) 2.38.20220708) #1
SMP Wed Aug 24 14:46:22 UTC 2022
[0.00] random: crng init done
[0.00] Machine model: Ventana VT1 QEMU
[0.00] SBI specification v1.0 detected
[0.00] SBI implementation ID=0x1 Version=0x10001
[0.00] SBI TIME extension detected
[0.00] SBI IPI extension detected
[0.00] SBI RFENCE extension detected
[0.00] SBI SRST extension detected
[0.00] earlycon: uart8250 at MMIO 0x1000 (options '')
[0.00] printk: bootconsole [uart8250] enabled
[0.00] efi: EFI v2.90 by Das U-Boot
[0.00] efi: RTPROP=0xfe73c020 SMBIOS=0xfe738000
MEMRESERVE=0xfd3ca020
[0.00] Zone ranges:
[0.00]   DMA32[mem 0x8000-0x]
[0.00]   Normal   empty
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x8000-0xfe737fff]
[0.00]   node   0: [mem 0xfe738000-0xfe738fff]
[0.00]   node   0: [mem 0xfe739000-0xfe73bfff]
[0.00]   node   0: [mem 0xfe73c000-0xfe742fff]
[0.00]   node   0: [mem 0xfe743000-0xfff77fff]
[0.00]   node   0: [mem 0xfff78000-0xfff78fff]
[0.00]   node   0: [mem 0xfff79000-0x]
[0.00] Initmem setup node 0 [mem
0x8000-0x]
[0.00] SBI HSM extension detected
[0.00] riscv: base ISA extensions acdfhim
[0.00] riscv: ELF capabilities acdfim
[0.00] riscv: Svinval extension supported
[0.00] percpu: Embedded 18 pages/cpu s34488 r8192 d31048 u73728
[0.00] Built 1 zonelists, mobility grouping on.  Total pages: 516096
[0.00] Kernel command line: root=/dev/vda2 rootwait console=ttyS0
earlycon=uart8250,mmio,0x1000
[0.00] Dentry cache hash table entries: 262144 (order: 9, 2097152
bytes, linear)
[0.00] Inode-cache hash table entries: 131072 (order: 8, 1048576
bytes, linear)
[0.00] mem auto-init: stack:off, heap alloc:off, heap free:off
[0.00] Virtual kernel memory layout:
[0.00]   fixmap : 0xff1bfee0 - 0xff1bff00
(2048 kB)
[0.00]   pci io : 0xff1bff00 - 0xff1c   (
 16 MB)
[0.00]  vmemmap : 0xff1c - 0xff20
(1024 TB)
[0.00]  vmalloc : 0xff20 - 0xff60
(16384 TB)
[0.00]   lowmem : 0xff60 - 0xff608000
(2048 MB)
[0.00]   kernel : 0x8000 - 0x
(2047 MB)
[0.00] Memory: 2034884K/2097152K available (7677K kernel code,
4908K rwdata, 4096K rodata, 2204K init, 463K bss, 62268K reserved, 0K
cma-reserved)
[0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=1
[0.00] rcu: Hierarchical RCU implementation.
[0.00] rcu: RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=16.
[0.00] rcu: RCU debug extended QS entry/exit.
[0.00] Tracing variant of Tasks RCU enabled.
[0.00] rcu: RCU calculated value of scheduler-enlistment delay is
25 jiffies.
[0.00] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=16
[0.00] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[0.00] riscv-intc: 64 local interrupts mapped using AIA
[0.00] riscv-imsic: imsics@2800:  hart-index-bits: 4,
 guest-index-bits: 3
[0.00] riscv-imsic: imsics@2800: group-index-bits: 0,
group-index-shift: 24
[0.00] riscv-imsic: imsics@2800: mapped 255 interrupts for 16
CPUs at 0x2800
[0.00] riscv-imsic: imsics@2800: enable/disable sync using
interrupt 2
[0.00] riscv-imsic: imsics@2800: providing IPIs using interrupt
1
[0.00] rcu: srcu_init: Setting srcu_struct sizes based on
contention.
[0.00] riscv_timer_init_dt: Registering clocksource cpuid [0]
hartid [15]
[0.00] clocksource: riscv_clocksource: mask: 0x
max_cycles: 0x24e6a1710, max_idle_ns: 440795202120 ns
[0.000175] sched_clock: 64 bits at 10MHz, resolution 100ns, wraps every
4398046511100ns
[0.003481] Timer interrupt in S-mode is available via sstc extension
[0.025738] Console: colour dummy device 80x25
[0.029321] Calibrating delay loop (skipped), value calculated using
timer frequency.. 20.00 BogoMIPS (lpj=4)
[0.031650] pid_max: default: 32768 minimum: 301
[0.034091] LSM: Security Framework initializing
[0.040644] Mount-cache hash table entries: 4096 (order: 3, 32768

Re: [yocto] Error during linux booting

2022-08-30 Thread Khem Raj 

On 8/30/22 2:34 AM, Vaibhav Deshpande wrote:

++

Regards
Vaibhav Vivek Deshpande


On Thu, Aug 25, 2022 at 4:32 PM Vaibhav Deshpande 
mailto:vdeshpa...@ventanamicro.com>> wrote:


Hello

I am trying to build a yocto image from the kirkstone
branch (https://github.com/openembedded/openembedded-core/tree/kirkstone 
) build gets 
successful but at the time of linux booting I am getting below error.

[    0.00] Linux version 5.19.0-rc4 (oe-user@oe-host)
(riscv64-oe-linux-gcc (GCC) 11.3.0, GNU ld (GNU Binutils)
2.38.20220708) #1 SMP Wed Aug 24 14:46:22 UTC 2022
[    0.00] random: crng init done
[    0.00] Machine model: Ventana VT1 QEMU
[    0.00] SBI specification v1.0 detected
[    0.00] SBI implementation ID=0x1 Version=0x10001
[    0.00] SBI TIME extension detected
[    0.00] SBI IPI extension detected
[    0.00] SBI RFENCE extension detected
[    0.00] SBI SRST extension detected
[    0.00] earlycon: uart8250 at MMIO 0x1000
(options '')
[    0.00] printk: bootconsole [uart8250] enabled
[    0.00] efi: EFI v2.90 by Das U-Boot
[    0.00] efi: RTPROP=0xfe73c020 SMBIOS=0xfe738000
MEMRESERVE=0xfd3ca020
[    0.00] Zone ranges:
[    0.00]   DMA32    [mem 0x8000-0x]
[    0.00]   Normal   empty
[    0.00] Movable zone start for each node
[    0.00] Early memory node ranges
[    0.00]   node   0: [mem 0x8000-0xfe737fff]
[    0.00]   node   0: [mem 0xfe738000-0xfe738fff]
[    0.00]   node   0: [mem 0xfe739000-0xfe73bfff]
[    0.00]   node   0: [mem 0xfe73c000-0xfe742fff]
[    0.00]   node   0: [mem 0xfe743000-0xfff77fff]
[    0.00]   node   0: [mem 0xfff78000-0xfff78fff]
[    0.00]   node   0: [mem 0xfff79000-0x]
[    0.00] Initmem setup node 0 [mem
0x8000-0x]
[    0.00] SBI HSM extension detected
[    0.00] riscv: base ISA extensions acdfhim
[    0.00] riscv: ELF capabilities acdfim
[    0.00] riscv: Svinval extension supported
[    0.00] percpu: Embedded 18 pages/cpu s34488 r8192 d31048 u73728
[    0.00] Built 1 zonelists, mobility grouping on.  Total
pages: 516096
[    0.00] Kernel command line: root=/dev/vda2 rootwait
console=ttyS0 earlycon=uart8250,mmio,0x1000
[    0.00] Dentry cache hash table entries: 262144 (order: 9,
2097152 bytes, linear)
[    0.00] Inode-cache hash table entries: 131072 (order: 8,
1048576 bytes, linear)
[    0.00] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.00] Virtual kernel memory layout:
[    0.00]       fixmap : 0xff1bfee0 -
0xff1bff00   (2048 kB)
[    0.00]       pci io : 0xff1bff00 -
0xff1c   (  16 MB)
[    0.00]      vmemmap : 0xff1c -
0xff20   (1024 TB)
[    0.00]      vmalloc : 0xff20 -
0xff60   (16384 TB)
[    0.00]       lowmem : 0xff60 -
0xff608000   (2048 MB)
[    0.00]       kernel : 0x8000 -
0x   (2047 MB)
[    0.00] Memory: 2034884K/2097152K available (7677K kernel
code, 4908K rwdata, 4096K rodata, 2204K init, 463K bss, 62268K
reserved, 0K cma-reserved)
[    0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16,
Nodes=1
[    0.00] rcu: Hierarchical RCU implementation.
[    0.00] rcu: RCU restricting CPUs from NR_CPUS=64 to
nr_cpu_ids=16.
[    0.00] rcu: RCU debug extended QS entry/exit.
[    0.00] Tracing variant of Tasks RCU enabled.
[    0.00] rcu: RCU calculated value of scheduler-enlistment
delay is 25 jiffies.
[    0.00] rcu: Adjusting geometry for rcu_fanout_leaf=16,
nr_cpu_ids=16
[    0.00] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[    0.00] riscv-intc: 64 local interrupts mapped using AIA
[    0.00] riscv-imsic: imsics@2800:  hart-index-bits: 4,
  guest-index-bits: 3
[    0.00] riscv-imsic: imsics@2800: group-index-bits: 0,
group-index-shift: 24
[    0.00] riscv-imsic: imsics@2800: mapped 255 interrupts
for 16 CPUs at 0x2800
[    0.00] riscv-imsic: imsics@2800: enable/disable sync
using interrupt 2
[    0.00] riscv-imsic: imsics@2800: providing IPIs using
interrupt 1
[    0.00] rcu: srcu_init: Setting srcu_struct sizes based on
contention.
[    0.00] riscv_timer_init_dt: Registering clocksource cpuid
[0] hartid [15]
[    

Re: [yocto] Error during linux booting

2022-08-30 Thread Vaibhav Deshpande 
++

Regards
Vaibhav Vivek Deshpande


On Thu, Aug 25, 2022 at 4:32 PM Vaibhav Deshpande <
vdeshpa...@ventanamicro.com> wrote:

> Hello
>
> I am trying to build a yocto image from the kirkstone branch (
> https://github.com/openembedded/openembedded-core/tree/kirkstone) build
> gets successful but at the time of linux booting I am getting below error.
>
> [0.00] Linux version 5.19.0-rc4 (oe-user@oe-host)
> (riscv64-oe-linux-gcc (GCC) 11.3.0, GNU ld (GNU Binutils) 2.38.20220708) #1
> SMP Wed Aug 24 14:46:22 UTC 2022
> [0.00] random: crng init done
> [0.00] Machine model: Ventana VT1 QEMU
> [0.00] SBI specification v1.0 detected
> [0.00] SBI implementation ID=0x1 Version=0x10001
> [0.00] SBI TIME extension detected
> [0.00] SBI IPI extension detected
> [0.00] SBI RFENCE extension detected
> [0.00] SBI SRST extension detected
> [0.00] earlycon: uart8250 at MMIO 0x1000 (options '')
> [0.00] printk: bootconsole [uart8250] enabled
> [0.00] efi: EFI v2.90 by Das U-Boot
> [0.00] efi: RTPROP=0xfe73c020 SMBIOS=0xfe738000
> MEMRESERVE=0xfd3ca020
> [0.00] Zone ranges:
> [0.00]   DMA32[mem 0x8000-0x]
> [0.00]   Normal   empty
> [0.00] Movable zone start for each node
> [0.00] Early memory node ranges
> [0.00]   node   0: [mem 0x8000-0xfe737fff]
> [0.00]   node   0: [mem 0xfe738000-0xfe738fff]
> [0.00]   node   0: [mem 0xfe739000-0xfe73bfff]
> [0.00]   node   0: [mem 0xfe73c000-0xfe742fff]
> [0.00]   node   0: [mem 0xfe743000-0xfff77fff]
> [0.00]   node   0: [mem 0xfff78000-0xfff78fff]
> [0.00]   node   0: [mem 0xfff79000-0x]
> [0.00] Initmem setup node 0 [mem
> 0x8000-0x]
> [0.00] SBI HSM extension detected
> [0.00] riscv: base ISA extensions acdfhim
> [0.00] riscv: ELF capabilities acdfim
> [0.00] riscv: Svinval extension supported
> [0.00] percpu: Embedded 18 pages/cpu s34488 r8192 d31048 u73728
> [0.00] Built 1 zonelists, mobility grouping on.  Total pages:
> 516096
> [0.00] Kernel command line: root=/dev/vda2 rootwait console=ttyS0
> earlycon=uart8250,mmio,0x1000
> [0.00] Dentry cache hash table entries: 262144 (order: 9, 2097152
> bytes, linear)
> [0.00] Inode-cache hash table entries: 131072 (order: 8, 1048576
> bytes, linear)
> [0.00] mem auto-init: stack:off, heap alloc:off, heap free:off
> [0.00] Virtual kernel memory layout:
> [0.00]   fixmap : 0xff1bfee0 - 0xff1bff00
> (2048 kB)
> [0.00]   pci io : 0xff1bff00 - 0xff1c   (
>  16 MB)
> [0.00]  vmemmap : 0xff1c - 0xff20
> (1024 TB)
> [0.00]  vmalloc : 0xff20 - 0xff60
> (16384 TB)
> [0.00]   lowmem : 0xff60 - 0xff608000
> (2048 MB)
> [0.00]   kernel : 0x8000 - 0x
> (2047 MB)
> [0.00] Memory: 2034884K/2097152K available (7677K kernel code,
> 4908K rwdata, 4096K rodata, 2204K init, 463K bss, 62268K reserved, 0K
> cma-reserved)
> [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=1
> [0.00] rcu: Hierarchical RCU implementation.
> [0.00] rcu: RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=16.
> [0.00] rcu: RCU debug extended QS entry/exit.
> [0.00] Tracing variant of Tasks RCU enabled.
> [0.00] rcu: RCU calculated value of scheduler-enlistment delay is
> 25 jiffies.
> [0.00] rcu: Adjusting geometry for rcu_fanout_leaf=16,
> nr_cpu_ids=16
> [0.00] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
> [0.00] riscv-intc: 64 local interrupts mapped using AIA
> [0.00] riscv-imsic: imsics@2800:  hart-index-bits: 4,
>  guest-index-bits: 3
> [0.00] riscv-imsic: imsics@2800: group-index-bits: 0,
> group-index-shift: 24
> [0.00] riscv-imsic: imsics@2800: mapped 255 interrupts for 16
> CPUs at 0x2800
> [0.00] riscv-imsic: imsics@2800: enable/disable sync using
> interrupt 2
> [0.00] riscv-imsic: imsics@2800: providing IPIs using
> interrupt 1
> [0.00] rcu: srcu_init: Setting srcu_struct sizes based on
> contention.
> [0.00] riscv_timer_init_dt: Registering clocksource cpuid [0]
> hartid [15]
> [0.00] clocksource: riscv_clocksource: mask: 0x
> max_cycles: 0x24e6a1710, max_idle_ns: 440795202120 ns
> [0.000175] sched_clock: 64 bits at 10MHz, resolution 100ns, wraps
> every 4398046511100ns
> [0.003481] Timer interrupt in S-mode is available via sstc extension
> [0.025738] Console: