About RT-Linux runs on Bao

[Sunt-git]

I applied rt-patch (patch-5.11-rt7.patch.gz ) to linux 5.11.0, and successfully generated a rt-patched Linux image. Then I ran Bao and successfully started RT-Linux, but when the Linux startup information stays on the user login interface, Linux cannot receive the account information I entered, and ssh cannot log in to Linux. The platform is aarch64 qemu-virt. What is the reason? Does rt-linux need a different dts file?

The startup information of rt-linux is as follows

[    0.785284] e1000: Copyright (c) 1999-2006 Intel Corporation.
[    0.785364] e1000e: Intel(R) PRO/1000 Network Driver
[    0.785378] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[    0.785461] igb: Intel(R) Gigabit Ethernet Network Driver
[    0.785470] igb: Copyright (c) 2007-2014 Intel Corporation.
[    0.785531] igbvf: Intel(R) Gigabit Virtual Function Network Driver
[    0.785538] igbvf: Copyright (c) 2009 - 2012 Intel Corporation.
[    0.785805] sky2: driver version 1.30
[    0.786818] VFIO - User Level meta-driver version: 0.3
[    0.789468] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    0.789577] ehci-pci: EHCI PCI platform driver
[    0.789727] ehci-platform: EHCI generic platform driver
[    0.789825] ehci-orion: EHCI orion driver
[    0.789915] ehci-exynos: EHCI Exynos driver
[    0.789994] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    0.790122] ohci-pci: OHCI PCI platform driver
[    0.790242] ohci-platform: OHCI generic platform driver
[    0.790332] ohci-exynos: OHCI Exynos driver
[    0.790917] usbcore: registered new interface driver usb-storage
[    0.793844] i2c /dev entries driver
[    0.798871] sdhci: Secure Digital Host Controller Interface driver
[    0.798881] sdhci: Copyright(c) Pierre Ossman
[    0.799341] Synopsys Designware Multimedia Card Interface Driver
[    0.799917] sdhci-pltfm: SDHCI platform and OF driver helper
[    0.802546] usbcore: registered new interface driver usbhid
[    0.802563] usbhid: USB HID core driver
[    0.809048] NET: Registered protocol family 17
[    0.809973] 9pnet: Installing 9P2000 support
[    0.810194] Key type dns_resolver registered
[    0.810891] printk: console [hvc0]: printing thread started
[    0.811280] registered taskstats version 1
[    0.811321] Loading compiled-in X.509 certificates
[    0.849085] IP-Config: Guessing netmask 255.255.255.0
[    0.849321] IP-Config: Complete:
[    0.849339]      device=eth0, hwaddr=52:54:00:12:34:56, ipaddr=192.168.42.15, mask=255.255.255.0, gw=255.255.255.255
[    0.849548]      host=192.168.42.15, domain=, nis-domain=(none)
[    0.849557]      bootserver=255.255.255.255, rootserver=255.255.255.255, rootpath=
[    0.851401] ALSA device list:
[    0.851461]   No soundcards found.
[    0.889348] Freeing unused kernel memory: 14592K
[    0.890334] Run /init as init process
Starting syslogd: OK
Starting klogd: OK
Running sysctl: OK
Saving random seed: [    1.782677] random: dd: uninitialized urandom read (512 bytes read)
OK
Starting dropbear sshd: [    2.065715] NET: Registered protocol family 10
[    2.076274] Segment Routing with IPv6
OK

buildroot login: 
Login timed out after 60 seconds
root

buildroot login: 

[josecm]

@Sunt-git I'm not that familiar with Linux-RT and the implications it might have on its configuration (be it Kconfig or device-tree wise). The only issue that comes to mind is that, if you are passing-through virt's virtio-net, because there is no SMMU for virtio devices, you need to have identity mappings for that guest by setting the place_phys/phys parameters in the guest's memory regions configuration so that the PA coincides with the IPA. Are you already doing this in your configuration? If not, could you paste here the configuration you are using?

[Sunt-git]

The configuration i'm using is as follows

#include <config.h>

VM_IMAGE(linux_image, XSTR(BAO_DEMOS_WRKDIR_IMGS/linux.bin));

struct config config = {
    
    CONFIG_HEADER

    .shmemlist_size = 1,
    .shmemlist = (struct shmem[]) {
        [0] = { .size = 0x00010000, }
    },

    .vmlist_size = 1,
    .vmlist = {
        { 
            .image = {
                .base_addr = 0x60000000,
                .load_addr = VM_IMAGE_OFFSET(linux_image),
                .size = VM_IMAGE_SIZE(linux_image)
            },

            .entry = 0x60000000,

            .platform = {
                .cpu_num = 1,
                
                .region_num = 1,
                .regions =  (struct mem_region[]) {
                    {
                        .base = 0x60000000,
                        .size = 0x40000000,
                        .place_phys = true,
                        .phys = 0x60000000
                    }
                },

                .ipc_num = 1,
                .ipcs = (struct ipc[]) {
                    {
                        .base = 0xf0000000,
                        .size = 0x00010000,
                        .shmem_id = 0,
                        .interrupt_num = 1,
                        .interrupts = (uint64_t[]) {52}
                    }
                },

                .dev_num = 2,
                .devs =  (struct dev_region[]) {
                    {
                        /* virtio devices */
                        .pa = 0xa003000,   
                        .va = 0xa003000,  
                        .size = 0x1000,
                        .interrupt_num = 8,
                        .interrupts = (uint64_t[]) {72,73,74,75,76,77,78,79}
                    },
                    {   
                        /* Arch timer interrupt */
                        .interrupt_num = 1,
                        .interrupts = (uint64_t[]) {27}                         
                    }
                },

                .arch = {
                    .gic = {
                       .gicd_addr = 0x8000000,
                       .gicr_addr = 0x80A0000
                    }
                }
            },
        },
        

    },
};

[LSVulnerable]

@Sunt-git hey, i met the same question. Did u solve this problem in the end?

[josecm]

@LSVulnerable @Sunt-git can you provide more information on exactly happens? Do you mean you are not able to enter user/pass or just that linux never accepts the login?