All of lore.kernel.org
 help / color / mirror / Atom feed
* [raspberry-pi4-xen-series] : Console login failure for xen-image-minimal
@ 2020-07-08  7:12 Ashishx88
  2020-07-08 13:56 ` [meta-virtualization] " Christopher Clark
       [not found] ` <161FCB8FD8858AB7.11266@lists.yoctoproject.org>
  0 siblings, 2 replies; 6+ messages in thread
From: Ashishx88 @ 2020-07-08  7:12 UTC (permalink / raw)
  To: meta-virtualization


[-- Attachment #1.1: Type: text/plain, Size: 1214 bytes --]

Hi Christopher ,

- I have created an xen-image-minimal using the commit & repo mentioned
https://lists.yoctoproject.org/g/meta-virtualization/message/5464 ( https://lists.yoctoproject.org/g/meta-virtualization/message/5464 )
I am able to compile both core-image-minimal & xen-image-minimal .

- When the board boots with the compiled image , i am observing below mentioned issue
Can you provide any inputs or if same issue has been observed with other members :

1) At the login prompt , root credentials fails continuously for few time.
raspberrypi4-64 login: root
Password: root
*( I can assure you that there is no typo error )*

2) After few attempt , i get the  root prompt *root@raspberrypi4-64:~#
* After the prompt within few seconds i get *Login timed out after 60 seconds.
* and behaviour starts again from point-1 mentioned above.
-> Attached along is the minicom log for your reference.

3) Similar login problem i have seen with core-image-minimal
Local.conf :
DISTRO_FEATURES_append = " xen virtualization"
MACHINE = "raspberrypi4-64"

Hence can you please let me know if similar observation is being reported.
and any pointers to look for the issue .

Thanks ,
Ashish

[-- Attachment #1.2: Type: text/html, Size: 2329 bytes --]

[-- Attachment #2: raspberry-pi4-xen-login-problem.txt --]
[-- Type: text/plain, Size: 27220 bytes --]

 

Welcome to minicom 2.7

OPTIONS: I18n 
Compiled on Nov 15 2018, 20:18:47.
Port /dev/ttyUSB0, 12:06:42

Press CTRL-A Z for help on special keys



U-Boot 2020.01 (Jan 06 2020 - 20:56:31 +0000)

DRAM:  3.9 GiB
RPI 4 Model B (0xc03112)
MMC:   mmcnr@7e300000: 1, emmc2@7e340000: 0
Loading Environment from FAT... *** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   Net Initialization Skipped
No ethernet found.
Hit any key to stop autoboot:  0 
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
1619 bytes read in 26 ms (60.5 KiB/s)
## Executing script at 02400000
Add boot arguments for Xen
Add boot arguments for dom0
Add a dom0 node to chosen to put Linux boot information in
Set this for the Linux boot command
Delay to allow the MMC card to be ready
Load Xen into memory
1017168 bytes read in 99 ms (9.8 MiB/s)
Load Linux kernel into memory
16710144 bytes read in 1231 ms (12.9 MiB/s)
Set the address and size for the Linux kernel so Xen can pick it up
chosen {
        xen,dom0-bootargs = "console=hvc0 earlyprintk=xen debug root=/dev/mmcblk0p2 rootwait";
        xen,xen-bootargs = "console=dtuart dtuart=/soc/serial@7e215040 dom0_mem=256M sync_console bootscrub=0";
        ranges;
        #size-cells = <0x00000001>;
        #address-cells = <0x00000001>;
        compatible = "simple_bus";
        kaslr-seed = <0x954fb609 0x6433b0a3>;
        rpi-boardrev-ext = <0x00000000>;
        bootargs = "coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1  smsc95xx.macadd;
        dom0 {
                reg = <0x00400000 0x00fefa00>;
                compatible = "xen,linux-zimage,", "xen,multiboot-module";
        };
        framebuffer@00000000 {
                status = "okay";
                compatible = "simple-framebuffer";
                format = "r5g6b5";
                stride = <0x00000000>;
                height = <0x00000000>;
                width = <0x00000000>;
                reg = <0x00000000 0x00000000>;
        };
};
Boot Xen
## Flattened Device Tree blob at 2eff4500
   Booting using the fdt blob at 0x2eff4500
   Using Device Tree in place at 000000002eff4500, end 000000002f003fff

Starting kernel ...

 Xen 4.13.1-pre
(XEN) Xen version 4.13.1-pre (xen-4.13+gitAUTOINC+b66ce5058e-r0@poky) (aarch64-poky-linux-gcc (GCC) 9.2.0) debug=y  2020-04-14
(XEN) Latest ChangeSet: Tue Apr 14 14:53:03 2020 +0200 git:b66ce50-dirty
(XEN) build-id: 9edfde85f5b405e755d8344f65c43b91b2711710
(XEN) Console output is synchronous.
(XEN) Processor: 410fd083: "ARM Limited", variant: 0x0, part 0xd08, rev 0x3
(XEN) 64-bit Execution:
(XEN)   Processor Features: 0000000000002222 0000000000000000
(XEN)     Exception Levels: EL3:64+32 EL2:64+32 EL1:64+32 EL0:64+32
(XEN)     Extensions: FloatingPoint AdvancedSIMD
(XEN)   Debug Features: 0000000010305106 0000000000000000
(XEN)   Auxiliary Features: 0000000000000000 0000000000000000
(XEN)   Memory Model Features: 0000000000001124 0000000000000000
(XEN)   ISA Features:  0000000000010000 0000000000000000
(XEN) 32-bit Execution:
(XEN)   Processor Features: 00000131:00011011
(XEN)     Instruction Sets: AArch32 A32 Thumb Thumb-2 Jazelle
(XEN)     Extensions: GenericTimer Security
(XEN)   Debug Features: 03010066
(XEN)   Auxiliary Features: 00000000
(XEN)   Memory Model Features: 10201105 40000000 01260000 02102211
(XEN)  ISA Features: 02101110 13112111 21232042 01112131 00011142 00010001
(XEN) SMP: Allowing 4 CPUs
(XEN) enabled workaround for: ARM erratum 1319537
(XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27 Freq: 54000 KHz
(XEN) GICv2 initialization:
(XEN)         gic_dist_addr=00000000ff841000
(XEN)         gic_cpu_addr=00000000ff842000
(XEN)         gic_hyp_addr=00000000ff844000
(XEN)         gic_vcpu_addr=00000000ff846000
(XEN)         gic_maintenance_irq=25
(XEN) GICv2: 256 lines, 4 cpus, secure (IID 0200143b).
(XEN) XSM Framework v1.0.0 initialized
(XEN) Initialising XSM SILO mode
(XEN) Using scheduler: SMP Credit Scheduler rev2 (credit2)
(XEN) Initializing Credit2 scheduler
(XEN)  load_precision_shift: 18
(XEN)  load_window_shift: 30
(XEN)  underload_balance_tolerance: 0
(XEN)  overload_balance_tolerance: -3
(XEN)  runqueues arrangement: socket
(XEN)  cap enforcement granularity: 10ms
(XEN) load tracking window length 1073741824 ns
(XEN) Allocated console ring of 32 KiB.
(XEN) CPU0: Guest atomics will try 6 times before pausing the domain
(XEN) Bringing up CPU1
(XEN) CPU1: Guest atomics will try 5 times before pausing the domain
(XEN) CPU 1 booted.
(XEN) Bringing up CPU2
(XEN) CPU2: Guest atomics will try 5 times before pausing the domain
(XEN) CPU 2 booted.
(XEN) Bringing up CPU3
(XEN) CPU3: Guest atomics will try 5 times before pausing the domain
(XEN) CPU 3 booted.
(XEN) Brought up 4 CPUs
(XEN) I/O virtualisation disabled
(XEN) P2M: 44-bit IPA with 44-bit PA and 8-bit VMID
(XEN) P2M: 4 levels with order-0 root, VTCR 0x80043594
(XEN) Adding cpu 0 to runqueue 0
(XEN)  First cpu on runqueue, activating
(XEN) Adding cpu 1 to runqueue 0
(XEN) Adding cpu 2 to runqueue 0
(XEN) Adding cpu 3 to runqueue 0
(XEN) alternatives: Patching with alt table 00000000002cc0b8 -> 00000000002cc7cc
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Loading d0 kernel from boot module @ 0000000000400000
(XEN) Allocating 1:1 mappings totalling 256MB for dom0:
(XEN) BANK[0] 0x00000010000000-0x00000020000000 (256MB)
(XEN) Grant table range: 0x00000000200000-0x00000000240000
(XEN) Allocating PPI 16 for event channel interrupt
(XEN) Loading zImage from 0000000000400000 to 0000000010080000-000000001106fa00
(XEN) Loading d0 DTB to 0x0000000018000000-0x000000001800b611
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) ***************************************************
(XEN) WARNING: CONSOLE OUTPUT IS SYNCHRONOUS
(XEN) This option is intended to aid debugging of Xen by ensuring
(XEN) that all output is synchronously delivered on the serial line.
(XEN) However it can introduce SIGNIFICANT latencies and affect
(XEN) timekeeping. It is NOT recommended for production use!
(XEN) ***************************************************
(XEN) No support for ARM_SMCCC_ARCH_WORKAROUND_1.
(XEN) Please update your firmware.
(XEN) ***************************************************
(XEN) No support for ARM_SMCCC_ARCH_WORKAROUND_1.
(XEN) Please update your firmware.
(XEN) ***************************************************
(XEN) No support for ARM_SMCCC_ARCH_WORKAROUND_1.
(XEN) Please update your firmware.
(XEN) ***************************************************
(XEN) 3... 2... 1... 
(XEN) *** Serial input to DOM0 (type 'CTRL-a' three times to switch input)
(XEN) Freed 336kB init memory.
(XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER4
(XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER8
(XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER12
(XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER16
(XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER20
(XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER24
(XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER28
(XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER0
[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd083]
[    0.000000] Linux version 5.4.47 (oe-user@oe-host) (gcc version 9.2.0 (GCC)) #1 SMP PREEMPT Wed Jun 17 16:38:40 UTC 2020
[    0.000000] Machine model: Raspberry Pi 4 Model B Rev 1.2
[    0.000000] Xen 4.13 support found
[    0.000000] efi: Getting EFI parameters from FDT:
[    0.000000] efi: UEFI not found.
[    0.000000] OF: reserved mem: failed to allocate memory for node 'linux,cma'
[    0.000000] cma: Reserved 8 MiB at 0x000000001f800000
[    0.000000] On node 0 totalpages: 65536
[    0.000000]   DMA zone: 1024 pages used for memmap
[    0.000000]   DMA zone: 0 pages reserved
[    0.000000]   DMA zone: 65536 pages, LIFO batch:15
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv1.1 detected in firmware.
[    0.000000] psci: Using standard PSCI v0.2 function IDs
[    0.000000] psci: Trusted OS migration not required
[    0.000000] psci: SMC Calling Convention v1.1
[    0.000000] percpu: Embedded 32 pages/cpu s91032 r8192 d31848 u131072
[    0.000000] pcpu-alloc: s91032 r8192 d31848 u131072 alloc=32*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[    0.000000] Detected PIPT I-cache on CPU0
[    0.000000] CPU features: detected: EL2 vector hardening
[    0.000000] CPU features: detected: Speculative Store Bypass Disable
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 64512
[    0.000000] Kernel command line: console=hvc0 earlyprintk=xen debug root=/dev/mmcblk0p2 rootwait
[    0.000000] Dentry cache hash table entries: 32768 (order: 6, 262144 bytes, linear)
[    0.000000] Inode-cache hash table entries: 16384 (order: 5, 131072 bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] Memory: 218336K/262144K available (10300K kernel code, 1150K rwdata, 3708K rodata, 1088K init, 1211K bss, 35616K reserved, 8192K cma-reserved)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] ftrace: allocating 35144 entries in 138 pages
[    0.000000] rcu: Preemptible hierarchical RCU implementation.
[    0.000000] rcu:     RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4.
[    0.000000]  Tasks RCU enabled.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[    0.000000] random: get_random_bytes called from start_kernel+0x31c/0x4a8 with crng_init=0
[    0.000000] arch_timer: cp15 timer(s) running at 54.00MHz (virt).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0xc743ce346, max_idle_ns: 440795203123 ns
[    0.000005] sched_clock: 56 bits at 54MHz, resolution 18ns, wraps every 4398046511102ns
[    0.000226] Console: colour dummy device 80x25
[    0.261328] printk: console [hvc0] enabled
[    0.265571] Calibrating delay loop (skipped), value calculated using timer frequency.. 108.00 BogoMIPS (lpj=216000)
[    0.276169] pid_max: default: 32768 minimum: 301
[    0.281183] Mount-cache hash table entries: 512 (order: 0, 4096 bytes, linear)
[    0.288292] Mountpoint-cache hash table entries: 512 (order: 0, 4096 bytes, linear)
[    0.297117] Disabling memory control group subsystem
[    0.325746] ASID allocator initialised with 32768 entries
[    0.331599] xen:grant_table: Grant tables using version 1 layout
[    0.337028] Grant table initialized
[    0.340617] xen:events: Using FIFO-based ABI
[    0.345043] Xen: initializing cpu0
[    0.353089] rcu: Hierarchical SRCU implementation.
[    0.365683] EFI services will not be available.
[    0.377695] smp: Bringing up secondary CPUs ...
(XEN) d0v1: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER0
(XEN) d0v2: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER0
(XEN) d0v3: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER0
[    0.406110] Detected PIPT I-cache on CPU1
[    0.411776] Xen: initializing cpu1
[    0.411813] CPU1: Booted secondary processor 0x0000000001 [0x410fd083]
[    0.442418] Detected PIPT I-cache on CPU2
[    0.448064] Xen: initializing cpu2
[    0.448098] CPU2: Booted secondary processor 0x0000000002 [0x410fd083]
[    0.478764] Detected PIPT I-cache on CPU3
[    0.484410] Xen: initializing cpu3
[    0.484444] CPU3: Booted secondary processor 0x0000000003 [0x410fd083]
[    0.484667] smp: Brought up 1 node, 4 CPUs
[    0.531543] SMP: Total of 4 processors activated.
[    0.536351] CPU features: detected: 32-bit EL0 Support
[    0.541661] CPU features: detected: CRC32 instructions
[    0.571914] CPU: All CPU(s) started at EL1
[    0.575473] alternatives: patching kernel code
[    0.581255] devtmpfs: initialized
[    0.593029] Enabled cp15_barrier support
[    0.596439] Enabled setend support
[    0.600486] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.609799] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[    0.617338] pinctrl core: initialized pinctrl subsystem
[    0.622753] DMI not present or invalid.
[    0.626414] NET: Registered protocol family 16
[    0.634101] DMA: preallocated 256 KiB pool for atomic allocations
[    0.640852] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.647621] xen:swiotlb_xen: Warning: only able to allocate 4 MB for software IO TLB
[    0.656862] software IO TLB: mapped [mem 0x1d800000-0x1dc00000] (4MB)
[    0.662798] Serial: AMBA PL011 UART driver
[    0.670092] bcm2835-mbox fe00b880.mailbox: mailbox enabled
[    0.687112] raspberrypi-firmware soc:firmware: Attached to firmware from 2020-06-01 13:23, variant start
[    0.700090] raspberrypi-firmware soc:firmware: Firmware hash is 6379679d1ec6a8c746d7e77e015f5b56b939976f
[    0.751087] bcm2835-dma fe007000.dma: DMA legacy API manager, dmachans=0x1
[    0.758866] xen:balloon: Initialising balloon driver
[    0.765261] vgaarb: loaded
[    0.767789] SCSI subsystem initialized
[    0.771395] usbcore: registered new interface driver usbfs
[    0.776897] usbcore: registered new interface driver hub
[    0.782396] usbcore: registered new device driver usb
[    0.788734] clocksource: Switched to clocksource arch_sys_counter
[    1.514272] VFS: Disk quotas dquot_6.6.0
[    1.517694] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    1.524852] FS-Cache: Loaded
[    1.527824] CacheFiles: Loaded
[    1.531476] simple-framebuffer: probe of 0.framebuffer failed with error -12
[    1.551727] thermal_sys: Registered thermal governor 'step_wise'
[    1.552039] NET: Registered protocol family 2
[    1.562651] tcp_listen_portaddr_hash hash table entries: 256 (order: 0, 4096 bytes, linear)
[    1.570487] TCP established hash table entries: 2048 (order: 2, 16384 bytes, linear)
[    1.578366] TCP bind hash table entries: 2048 (order: 3, 32768 bytes, linear)
[    1.585659] TCP: Hash tables configured (established 2048 bind 2048)
[    1.592263] UDP hash table entries: 256 (order: 1, 8192 bytes, linear)
[    1.598833] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear)
[    1.606140] NET: Registered protocol family 1
[    1.611347] RPC: Registered named UNIX socket transport module.
[    1.616697] RPC: Registered udp transport module.
[    1.621505] RPC: Registered tcp transport module.
[    1.626317] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    1.632940] PCI: CLS 0 bytes, default 64
[    1.638144] kvm [1]: HYP mode not available
[    1.643400] Initialise system trusted keyrings
[    1.647554] workingset: timestamp_bits=46 max_order=16 bucket_order=0
[    1.662255] FS-Cache: Netfs 'nfs' registered for caching
[    1.667751] NFS: Registering the id_resolver key type
[    1.672234] Key type id_resolver registered
[    1.676491] Key type id_legacy registered
[    1.680630] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    1.688816] Key type asymmetric registered
[    1.692269] Asymmetric key parser 'x509' registered
[    1.697330] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
[    1.705183] io scheduler mq-deadline registered
[    1.709521] io scheduler kyber registered
[    1.717313] brcm-pcie fd500000.pcie: host bridge /scb/pcie@7d500000 ranges:
[    1.723703] brcm-pcie fd500000.pcie:   No bus range found for /scb/pcie@7d500000, using [bus 00-ff]
[    1.732956] brcm-pcie fd500000.pcie:      MEM 0x0600000000..0x0603ffffff -> 0x00f8000000
[    1.741210] brcm-pcie fd500000.pcie:   IB MEM 0x0000000000..0x00bfffffff -> 0x0000000000
[    1.798869] brcm-pcie fd500000.pcie: link up, 5 GT/s x1 (SSC)
[    1.804333] brcm-pcie fd500000.pcie: PCI host bridge to bus 0000:00
[    1.810456] pci_bus 0000:00: root bus resource [bus 00-ff]
[    1.816049] pci_bus 0000:00: root bus resource [mem 0x600000000-0x603ffffff] (bus address [0xf8000000-0xfbffffff])
[    1.826624] pci 0000:00:00.0: [14e4:2711] type 01 class 0x060400
[    1.832933] pci 0000:00:00.0: PME# supported from D0 D3hot
(XEN) physdev.c:16:d0v0 PHYSDEVOP cmd=25: not implemented
(XEN) physdev.c:16:d0v0 PHYSDEVOP cmd=15: not implemented
[    1.848737] pci 0000:00:00.0: Failed to add - passthrough or MSI/MSI-X might fail!
[    1.859755] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    1.867358] pci 0000:01:00.0: [1106:3483] type 00 class 0x0c0330
[    1.873383] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x00000fff 64bit]
[    1.880459] pci 0000:01:00.0: PME# supported from D0 D3cold
(XEN) physdev.c:16:d0v0 PHYSDEVOP cmd=15: not implemented
[    1.891187] pci 0000:01:00.0: Failed to add - passthrough or MSI/MSI-X might fail!
[    1.902074] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    1.908118] pci 0000:00:00.0: BAR 8: assigned [mem 0x600000000-0x6000fffff]
[    1.915215] pci 0000:01:00.0: BAR 0: assigned [mem 0x600000000-0x600000fff 64bit]
[    1.922878] pci 0000:00:00.0: PCI bridge to [bus 01]
[    1.927943] pci 0000:00:00.0:   bridge window [mem 0x600000000-0x6000fffff]
[    1.935111] pci 0000:00:00.0: enabling device (0000 -> 0002)
[    1.940861] pci 0000:01:00.0: enabling device (0000 -> 0002)
[    1.946753] pci 0000:01:00.0: quirk_usb_early_handoff+0x0/0x940 took 11364 usecs
[    1.958495] xen:xen_evtchn: Event-channel device installed
[    1.967964] iproc-rng200 fe104000.rng: hwrng registered
[    1.972958] vc-mem: phys_addr:0x00000000 mem_base=0x00000000 mem_size:0x00000000(0 MiB)
[    1.981697] gpiomem-bcm2835 fe200000.gpiomem: Initialised: Registers at 0xfe200000
[    1.989118] cacheinfo: Unable to detect cache hierarchy for CPU 0
[    2.006509] brd: module loaded
[    2.021020] loop: module loaded
[    2.025063] Loading iSCSI transport class v2.0-870.
[    2.031256] libphy: Fixed MDIO Bus: probed
[    2.035309] bcmgenet fd580000.ethernet: failed to get enet clock
[    2.040937] bcmgenet fd580000.ethernet: GENET 5.0 EPHY: 0x0000
[    2.046874] bcmgenet fd580000.ethernet: failed to get enet-wol clock
[    2.053390] bcmgenet fd580000.ethernet: failed to get enet-eee clock
[    2.059856] bcmgenet: Skipping UMAC reset
[    2.072786] libphy: bcmgenet MII bus: probed
[    2.124871] unimac-mdio unimac-mdio.-19: Broadcom UniMAC MDIO bus
[    2.131236] xen_netfront: Initialising Xen virtual ethernet driver
[    2.136956] usbcore: registered new interface driver r8152
[    2.142508] usbcore: registered new interface driver lan78xx
[    2.148289] usbcore: registered new interface driver smsc95xx
[    2.154481] xhci_hcd 0000:01:00.0: xHCI Host Controller
[    2.159490] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 1
[    2.167730] xhci_hcd 0000:01:00.0: hcc params 0x002841eb hci version 0x100 quirks 0x0000001000000890
[    2.177166] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04
[    2.184884] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.192247] usb usb1: Product: xHCI Host Controller
[    2.197236] usb usb1: Manufacturer: Linux 5.4.47 xhci-hcd
[    2.202775] usb usb1: SerialNumber: 0000:01:00.0
[    2.208149] hub 1-0:1.0: USB hub found
[    2.211437] hub 1-0:1.0: 1 port detected
[    2.215932] xhci_hcd 0000:01:00.0: xHCI Host Controller
[    2.220781] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2
[    2.228329] xhci_hcd 0000:01:00.0: Host supports USB 3.0 SuperSpeed
[    2.235044] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.04
[    2.243193] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.250538] usb usb2: Product: xHCI Host Controller
[    2.255538] usb usb2: Manufacturer: Linux 5.4.47 xhci-hcd
[    2.261068] usb usb2: SerialNumber: 0000:01:00.0
[    2.266417] hub 2-0:1.0: USB hub found
[    2.269732] hub 2-0:1.0: 4 ports detected
[    2.275033] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[    2.280409] dwc_otg: FIQ enabled
[    2.283510] dwc_otg: NAK holdoff enabled
[    2.287544] dwc_otg: FIQ split-transaction FSM enabled
[    2.292828] Module dwc_common_port init
[    2.297428] usbcore: registered new interface driver uas
[    2.302314] usbcore: registered new interface driver usb-storage
[    2.308615] mousedev: PS/2 mouse device common for all mice
[    2.316291] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
[    2.323322] cpufreq-dt cpufreq-dt: failed register driver: -19
[    2.329174] sdhci: Secure Digital Host Controller Interface driver
[    2.334873] sdhci: Copyright(c) Pierre Ossman
[    2.339863] mmc-bcm2835 fe300000.mmcnr: could not get clk, deferring probe
[    2.346826] sdhci-pltfm: SDHCI platform and OF driver helper
[    2.355827] ledtrig-cpu: registered to indicate activity on CPUs
[    2.361393] hidraw: raw HID events driver (C) Jiri Kosina
[    2.366930] usbcore: registered new interface driver usbhid
[    2.372472] usbhid: USB HID core driver
[    2.378246] vchiq: vchiq_init_state: slot_zero = (____ptrval____)
[    2.387565] Initializing XFRM netlink socket
[    2.391430] NET: Registered protocol family 17
[    2.395920] Key type dns_resolver registered
[    2.400686] registered taskstats version 1
[    2.404405] Loading compiled-in X.509 certificates
[    2.409565] Key type ._fscrypt registered
[    2.413440] Key type .fscrypt registered
[    2.427249] uart-pl011 fe201000.serial: cts_event_workaround enabled
[    2.433100] fe201000.serial: ttyAMA0 at MMIO 0xfe201000 (irq = 13, base_baud = 0) is a PL011 rev2
[    2.447444] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
[    2.454914] mmc-bcm2835 fe300000.mmcnr: mmc_debug:0 mmc_debug2:0
[    2.460328] mmc-bcm2835 fe300000.mmcnr: DMA channel allocated
[    2.517411] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[    2.524155] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    2.529063] mmc0: SDHCI controller on fe340000.emmc2 [fe340000.emmc2] using ADMA
[    2.538575] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    2.539217] of_cfs_init
[    2.546129] of_cfs_init: OK
[    2.546797] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[    2.555237] Waiting for root device /dev/mmcblk0p2...
[    2.556488] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    2.568862] usb 1-1: new high-speed USB device number 2 using xhci_hcd
[    2.614746] random: fast init done
[    2.617982] mmc0: new high speed SD card at address e624
[    2.624023] mmcblk0: mmc0:e624 SU02G 1.84 GiB
[    2.635421]  mmcblk0: p1 p2
[    2.650234] EXT4-fs (mmcblk0p2): mounting ext3 file system using the ext4 subsystem
[    2.659055] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem
[    2.665529] mmc1: new high speed SDIO card at address 0001
[    2.665788] EXT4-fs (mmcblk0p2): write access will be enabled during recovery
[    2.723446] usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.20
[    2.731059] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    2.738347] usb 1-1: Product: USB2.0 Hub
[    2.743925] hub 1-1:1.0: USB hub found
[    2.747288] hub 1-1:1.0: 4 ports detected
[    2.827651] EXT4-fs (mmcblk0p2): recovery complete
[    2.835867] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    2.843446] VFS: Mounted root (ext3 filesystem) readonly on device 179:2.
[    2.850416] devtmpfs: mounted
[    2.857284] Freeing unused kernel memory: 1088K
[    2.861323] Run /sbin/init as init process
INIT: version  booting
Starting udev
[    3.368293] udevd[121]: starting version 3.2.9
[    3.381369] random: udevd: uninitialized urandom read (16 bytes read)
[    3.389248] random: udevd: uninitialized urandom read (16 bytes read)
[    3.395176] random: udevd: uninitialized urandom read (16 bytes read)
[    3.439822] udevd[122]: starting eudev-3.2.9
[    3.736600] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
Fri Mar  9 12:34:56 UTC 2018
INIT: Entering runlevel: 5
Configuring network interfaces... [    4.273595] bcmgenet: Skipping UMAC reset
[    4.279209] bcmgenet fd580000.ethernet: configuring instance for external RGMII
[    4.286336] bcmgenet fd580000.ethernet eth0: Link is Down
udhcpc: started, v1.31.1
udhcpc: sending discover
udhcpc: sending discover
[    9.393005] bcmgenet fd580000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
udhcpc: sending discover
udhcpc: no lease, forking to background
done.
Starting random number generator daemon.
[   16.832780] random: crng init done
[   16.835544] random: 4 urandom warning(s) missed due to ratelimiting
Starting OpenBSD Secure Shell server: sshd
[   17.026317] NET: Registered protocol family 10
[   17.037525] Segment Routing with IPv6
done.
Starting syslogd/klogd: done
Starting /usr/sbin/xenstored...
Setting domain 0 name, domid and JSON config...
Done setting up Dom0
Starting xenconsoled...
Starting QEMU as disk backend for dom0
Starting domain watchdog daemon: xenwatchdogd startup

[done]

Poky (Yocto Project Reference Distro) 3.0+snapshot raspberrypi4-64 /dev/hvc0

raspberrypi4-64 login: 
Poky (Yocto Project Reference Distro) 3.0+snapshot raspberrypi4-64 /dev/hvc0

raspberrypi4-64 login: root
Password: r
Login incorrect

raspberrypi4-64 login: root
roPassword: ro
Login incorrect

raspberrypi4-64 login: root
roPassword: r
Login incorrect

raspberrypi4-64 login: 

Password: 
raspberrypi4-64 login: 


raspberrypi4-64 login: 

raspberrypi4-64 login: 

raspberrypi4-64 login: root
root@raspberrypi4-64:~# Login incorrect

raspberrypi4-64 login: 
root@raspberrypi4-64:~# 
root@raspberrypi4-64:~# 
root@raspberrypi4-64:~# 
root@raspberrypi4-64:~# 
root@raspberrypi4-64:~# 
root@raspberrypi4-64:~# 
root@raspberrypi4-64:~# 
root@raspberrypi4-64:~# s^C
root@raspberrypi4-64:~# 
root@raspberrypi4-64:~# 
Login timed out after 60 seconds.

Poky (Yocto Project Reference Distro) 3.0+snapshot raspberrypi4-64 /dev/hvc0

raspberrypi4-64 login: 
Poky (Yocto Project Reference Distro) 3.0+snapshot raspberrypi4-64 /dev/hvc0

raspberrypi4-64 login: 
root@raspberrypi4-64:~# 
Poky (Yocto Project Reference Distro) 3.0+snapshot raspberrypi4-64 /dev/hvc0

raspberrypi4-64 login: 
root@raspberrypi4-64:~# 
Poky (Yocto Project Reference Distro) 3.0+snapshot raspberrypi4-64 /dev/hvc0

raspberrypi4-64 login: 
root@raspberrypi4-64:~# 
Poky (Yocto Project Reference Distro) 3.0+snapshot raspberrypi4-64 /dev/hvc0

raspberrypi4-64 login: 
root@raspberrypi4-64:~# 
Poky (Yocto Project Reference Distro) 3.0+snapshot raspberrypi4-64 /dev/hvc0

raspberrypi4-64 login: 
root@raspberrypi4-64:~# pwd
-sh: w: command not found
root@raspberrypi4-64:~# pwd
-sh: w: command not found
root@raspberrypi4-64:~# ls
Password: 
-sh: s: command not found
root@raspberrypi4-64:~# 
CTRL-A Z for help | 115200 8N1 | NOR | Minicom 2.7 | VT102 | Offline | ttyUSB0                                                                                  


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [meta-virtualization] [raspberry-pi4-xen-series] : Console login failure for xen-image-minimal
  2020-07-08  7:12 [raspberry-pi4-xen-series] : Console login failure for xen-image-minimal Ashishx88
@ 2020-07-08 13:56 ` Christopher Clark
       [not found] ` <161FCB8FD8858AB7.11266@lists.yoctoproject.org>
  1 sibling, 0 replies; 6+ messages in thread
From: Christopher Clark @ 2020-07-08 13:56 UTC (permalink / raw)
  To: Ashishx88; +Cc: meta-virtualization

On Wed, Jul 8, 2020 at 12:12 AM Ashishx88 <ashish.emailaddress@gmail.com> wrote:
>
> Hi Christopher ,
>
> - I have created an xen-image-minimal using the commit & repo mentioned
>    https://lists.yoctoproject.org/g/meta-virtualization/message/5464
>    I am able to compile both core-image-minimal & xen-image-minimal .
>
> - When the board boots with the compiled image , i am observing below mentioned issue
>    Can you provide any inputs or if same issue has been observed with other members :
>
>    1) At the login prompt , root credentials fails continuously for few time.
>        raspberrypi4-64 login: root
>        Password: root
>        ( I can assure you that there is no typo error )
>
>    2) After few attempt , i get the  root prompt root@raspberrypi4-64:~#
>        After the prompt within few seconds i get Login timed out after 60 seconds.
>        and behaviour starts again from point-1 mentioned above.
>        -> Attached along is the minicom log for your reference.
>
>    3) Similar login problem i have seen with core-image-minimal
>        Local.conf :
>                           DISTRO_FEATURES_append = " xen virtualization"
>                           MACHINE = "raspberrypi4-64"
>
> Hence can you please let me know if similar observation is being reported.
> and any pointers to look for the issue .

This looks like an unhappy serial device.
Please could you confirm: if you connect a local USB keyboard and HDMI
display, you do not have a similar problem logging in or using the
prompt?

thanks

Christopher


>
> Thanks ,
> Ashish

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [meta-virtualization] [raspberry-pi4-xen-series] : Console login failure for xen-image-minimal
       [not found] ` <161FCB8FD8858AB7.11266@lists.yoctoproject.org>
@ 2020-07-09  1:00   ` Christopher Clark
  2020-07-09  2:42     ` Bruce Ashfield
  0 siblings, 1 reply; 6+ messages in thread
From: Christopher Clark @ 2020-07-09  1:00 UTC (permalink / raw)
  To: Ashishx88; +Cc: meta-virtualization

On Wed, Jul 8, 2020 at 6:56 AM Christopher Clark via
lists.yoctoproject.org
<christopher.w.clark=gmail.com@lists.yoctoproject.org> wrote:
>
> On Wed, Jul 8, 2020 at 12:12 AM Ashishx88 <ashish.emailaddress@gmail.com> wrote:
> >
> > Hi Christopher ,
> >
> > - I have created an xen-image-minimal using the commit & repo mentioned
> >    https://lists.yoctoproject.org/g/meta-virtualization/message/5464
> >    I am able to compile both core-image-minimal & xen-image-minimal .
> >
> > - When the board boots with the compiled image , i am observing below mentioned issue
> >    Can you provide any inputs or if same issue has been observed with other members :
> >
> >    1) At the login prompt , root credentials fails continuously for few time.
> >        raspberrypi4-64 login: root
> >        Password: root
> >        ( I can assure you that there is no typo error )
> >
> >    2) After few attempt , i get the  root prompt root@raspberrypi4-64:~#
> >        After the prompt within few seconds i get Login timed out after 60 seconds.
> >        and behaviour starts again from point-1 mentioned above.
> >        -> Attached along is the minicom log for your reference.
> >
> >    3) Similar login problem i have seen with core-image-minimal
> >        Local.conf :
> >                           DISTRO_FEATURES_append = " xen virtualization"
> >                           MACHINE = "raspberrypi4-64"
> >
> > Hence can you please let me know if similar observation is being reported.
> > and any pointers to look for the issue .
>
> This looks like an unhappy serial device.
> Please could you confirm: if you connect a local USB keyboard and HDMI
> display, you do not have a similar problem logging in or using the
> prompt?

This turns out to be a simpler problem to fix than a device issue:
there are apparently two getty's running on the serial console device
(hvc0) and you only want one. If you're using the xen-image-minimal
image, the immediate workaround is to log in and edit the file
/etc/inittab to comment out or remove the last line beginning 'X0',
save it, and poweroff the device. When you start the device up again,
your serial console command prompt should now work correctly. It's
probably a similar fix for a core-image-minimal image (- I just don't
have one immediately to hand to check it).

I can also look into a patch for fixing this.

Christopher

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [meta-virtualization] [raspberry-pi4-xen-series] : Console login failure for xen-image-minimal
  2020-07-09  1:00   ` Christopher Clark
@ 2020-07-09  2:42     ` Bruce Ashfield
  2020-07-09  5:03       ` Ashishx88
  0 siblings, 1 reply; 6+ messages in thread
From: Bruce Ashfield @ 2020-07-09  2:42 UTC (permalink / raw)
  To: Christopher Clark; +Cc: Ashishx88, meta-virtualization

On Wed, Jul 8, 2020 at 9:00 PM Christopher Clark
<christopher.w.clark@gmail.com> wrote:
>
> On Wed, Jul 8, 2020 at 6:56 AM Christopher Clark via
> lists.yoctoproject.org
> <christopher.w.clark=gmail.com@lists.yoctoproject.org> wrote:
> >
> > On Wed, Jul 8, 2020 at 12:12 AM Ashishx88 <ashish.emailaddress@gmail.com> wrote:
> > >
> > > Hi Christopher ,
> > >
> > > - I have created an xen-image-minimal using the commit & repo mentioned
> > >    https://lists.yoctoproject.org/g/meta-virtualization/message/5464
> > >    I am able to compile both core-image-minimal & xen-image-minimal .
> > >
> > > - When the board boots with the compiled image , i am observing below mentioned issue
> > >    Can you provide any inputs or if same issue has been observed with other members :
> > >
> > >    1) At the login prompt , root credentials fails continuously for few time.
> > >        raspberrypi4-64 login: root
> > >        Password: root
> > >        ( I can assure you that there is no typo error )
> > >
> > >    2) After few attempt , i get the  root prompt root@raspberrypi4-64:~#
> > >        After the prompt within few seconds i get Login timed out after 60 seconds.
> > >        and behaviour starts again from point-1 mentioned above.
> > >        -> Attached along is the minicom log for your reference.
> > >
> > >    3) Similar login problem i have seen with core-image-minimal
> > >        Local.conf :
> > >                           DISTRO_FEATURES_append = " xen virtualization"
> > >                           MACHINE = "raspberrypi4-64"
> > >
> > > Hence can you please let me know if similar observation is being reported.
> > > and any pointers to look for the issue .
> >
> > This looks like an unhappy serial device.
> > Please could you confirm: if you connect a local USB keyboard and HDMI
> > display, you do not have a similar problem logging in or using the
> > prompt?
>
> This turns out to be a simpler problem to fix than a device issue:
> there are apparently two getty's running on the serial console device
> (hvc0) and you only want one. If you're using the xen-image-minimal
> image, the immediate workaround is to log in and edit the file
> /etc/inittab to comment out or remove the last line beginning 'X0',
> save it, and poweroff the device. When you start the device up again,
> your serial console command prompt should now work correctly. It's
> probably a similar fix for a core-image-minimal image (- I just don't
> have one immediately to hand to check it).

We've had quite a few hvc0 patches over the years .. we end up
fixing/breaking sysvinit/systemd and someone's use case everytime we
tweak it.

Checking the git history should let us know what to avoid :D

Bruce

>
> I can also look into a patch for fixing this.
>
> Christopher
> 



-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [raspberry-pi4-xen-series] : Console login failure for xen-image-minimal
  2020-07-09  2:42     ` Bruce Ashfield
@ 2020-07-09  5:03       ` Ashishx88
  2020-07-09  6:31         ` Ashishx88
  0 siblings, 1 reply; 6+ messages in thread
From: Ashishx88 @ 2020-07-09  5:03 UTC (permalink / raw)
  To: meta-virtualization

[-- Attachment #1: Type: text/plain, Size: 59 bytes --]

Thanks Chris & Bruce ,
Will try these.

Thanks
Ashish

[-- Attachment #2: Type: text/html, Size: 147 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [raspberry-pi4-xen-series] : Console login failure for xen-image-minimal
  2020-07-09  5:03       ` Ashishx88
@ 2020-07-09  6:31         ` Ashishx88
  0 siblings, 0 replies; 6+ messages in thread
From: Ashishx88 @ 2020-07-09  6:31 UTC (permalink / raw)
  To: meta-virtualization


[-- Attachment #1.1: Type: text/plain, Size: 170 bytes --]

I created an patch for this as per inputs shared above.
Can team please review and share feedback if any as this being my first patch for community.

Thanks
Ashish.

[-- Attachment #1.2: Type: text/html, Size: 210 bytes --]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Prevents-two-getty-running-on-single-serial-console-.patch --]
[-- Type: text/x-patch; name="0001-Prevents-two-getty-running-on-single-serial-console-.patch", Size: 1167 bytes --]

From ed91c3c83d471a8858fd77c395d41fd06198c3f0 Mon Sep 17 00:00:00 2001
From: Ashish <ashishm@mvista.com>
Date: Thu, 9 Jul 2020 11:39:00 +0530
Subject: [PATCH] Prevents two getty running on single serial console (hvc0)

When xen is enabled on raspberrypi4-64 machine user had
two getty's running on the serial console device (hvc0)
This led to root credentials failure continuously for few time
followed by user getting the root prompt.
But user would be unable to operate on serial console as
he gets "Login timed out after 60 seconds" within few seconds
and the control goes back again asking login credentials.
---
 recipes-core/sysvinit/sysvinit-inittab_xen.inc | 1 -
 1 file changed, 1 deletion(-)

diff --git a/recipes-core/sysvinit/sysvinit-inittab_xen.inc b/recipes-core/sysvinit/sysvinit-inittab_xen.inc
index de0af20..04fd8f9 100644
--- a/recipes-core/sysvinit/sysvinit-inittab_xen.inc
+++ b/recipes-core/sysvinit/sysvinit-inittab_xen.inc
@@ -1,4 +1,3 @@
 do_install_append() {
                 echo "" >> ${D}${sysconfdir}/inittab
-                echo "X0:12345:respawn:${base_sbindir}/getty-wrapper 115200 hvc0" >> ${D}${sysconfdir}/inittab
 }
-- 
2.7.4


^ permalink raw reply related	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2020-07-09  6:31 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-07-08  7:12 [raspberry-pi4-xen-series] : Console login failure for xen-image-minimal Ashishx88
2020-07-08 13:56 ` [meta-virtualization] " Christopher Clark
     [not found] ` <161FCB8FD8858AB7.11266@lists.yoctoproject.org>
2020-07-09  1:00   ` Christopher Clark
2020-07-09  2:42     ` Bruce Ashfield
2020-07-09  5:03       ` Ashishx88
2020-07-09  6:31         ` Ashishx88

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.