Hey Cyril, thanks for trying! Get that one too : https://openpower.xyz/job/openpower/job/openpower-op-build/label=slave,target=witherspoon/lastSuccessfulBuild/artifact/images/skiboot.lid and give it to qemu-system-ppc64 by adding "-bios skiboot.lid" to the qemu line (got the same issue. Last components build may require a newer skiboot.lid than the one coming in qemu package). F. On Mon, 24 May 2021 04:48:00 +0200, Cyril Brulebois <kibi@debian.org> wrote: > Hi Frédéric, > > Frédéric Bonnard <frediz@debian.org> (2021-04-26): > > Thanks for willing to investigate ! > > Thanks for the detailed steps! > > > LPAR setup in PowerVM can not be reproduced to my knowledge with qemu; > > this a partitioning configuration with PHYP proprietary firmware by > > IBM. Using a ppc64el vm, I never had the issue, since I think, hvc0 > > does not exist and thus does not create race condition with tty0. The > > last possible configuration providing hvc0 is the baremetal mode > > (PowerNV), installating a physical Power machine with linux on top of > > it. > > Hopefully, qemu is able to emulate a baremetal machine (PowerNV) as > > skiboot firmware is opensource (compared to PHYP). > > I tried and could reproduce the bug after 3 tries. > > > > For this, on your amd64 machine : > > - install qemu-system-ppc 5.2 (in my case, using stable, I used 1:5.2+dfsg-9~bpo10+1 ) > > - get those : > > * https://openpower.xyz/job/openpower/job/openpower-op-build/label=slave,target=witherspoon/lastSuccessfulBuild/artifact/images/rootfs.cpio.xz > > * https://openpower.xyz/job/openpower/job/openpower-op-build/label=slave,target=witherspoon/lastSuccessfulBuild/artifact/images/zImage.epapr > > - use the following to emulate the P9 PowerNV Witherspoon machine : > > qemu-system-ppc64 -m 2G -machine powernv9 -smp 8,cores=8,threads=1 \ > > -accel tcg,thread=single \ > > -device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0 \ > > -netdev user,id=net0,hostfwd=::20022-:22,hostname=pnv \ > > -kernel ./zImage.epapr \ > > -initrd ./rootfs.cpio.xz \ > > -nographic > > - Once you get into the petitboot menu, "Exit to shell" > > Using a rather similar qemu package, but on bullseye (1:5.2+dfsg-10), > I'm not able to get to the petitboot menu: > > kibi@tokyo:~/downloads$ qemu-system-ppc64 -m 2G -machine powernv9 -smp 8,cores=8,threads=1 \ > -accel tcg,thread=single \ > -device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0 \ > -netdev user,id=net0,hostfwd=::20022-:22,hostname=pnv \ > -kernel ./zImage.epapr \ > -initrd ./rootfs.cpio.xz \ > -nographic > [ 0.015788836,5] OPAL v6.4 starting... > [ 0.016283111,7] initial console log level: memory 7, driver 5 > [ 0.016319531,6] CPU: P9 generation processor (max 4 threads/core) > [ 0.016335507,7] CPU: Boot CPU PIR is 0x0000 PVR is 0x004e1200 > [ 0.016452461,7] OPAL table: 0x30110530 .. 0x30110aa0, branch table: 0x30002000 > [ 0.016622304,7] Assigning physical memory map table for nimbus > [ 0.016979537,7] FDT: Parsing fdt @0x1000000 > [ 0.019592646,5] CHIP: Detected Qemu simulator > [ 0.019757972,6] CHIP: Initialised chip 0 from xscom@603fc00000000 > [ 0.020117574,6] P9 DD2.00 detected > [ 0.020142490,5] CHIP: Chip ID 0000 type: P9N DD2.00 > [ 0.020155985,7] XSCOM: Base address: 0x603fc00000000 > [ 0.020192159,7] XSTOP: ibm,sw-checkstop-fir prop not found > [ 0.020301881,6] MFSI 0:0: Initialized > [ 0.020313870,6] MFSI 0:2: Initialized > [ 0.020323201,6] MFSI 0:1: Initialized > [ 0.020848585,6] LPC: LPC[000]: Initialized > [ 0.020858725,7] LPC: access via MMIO @0x6030000000000 > [ 0.020894150,7] LPC: Default bus on chip 0x0 > [ 0.020998003,7] CPU: New max PIR set to 0x1f > [ 0.021512680,7] MEM: parsing reserved memory from reserved-names/-ranges properties > [ 0.021609903,7] CPU: decrementer bits 56 > [ 0.021668231,6] CPU: CPU from DT PIR=0x0000 Server#=0x0 State=3 > [ 0.021750145,6] CPU: 1 secondary threads > [ 0.021766340,6] CPU: CPU from DT PIR=0x0004 Server#=0x4 State=3 > [ 0.021788849,6] CPU: 1 secondary threads > [ 0.021797000,6] CPU: CPU from DT PIR=0x0008 Server#=0x8 State=3 > [ 0.021807120,6] CPU: 1 secondary threads > [ 0.021814202,6] CPU: CPU from DT PIR=0x000c Server#=0xc State=3 > [ 0.021823785,6] CPU: 1 secondary threads > [ 0.021834496,6] CPU: CPU from DT PIR=0x0010 Server#=0x10 State=3 > [ 0.021846219,6] CPU: 1 secondary threads > [ 0.021858600,6] CPU: CPU from DT PIR=0x0014 Server#=0x14 State=3 > [ 0.021870856,6] CPU: 1 secondary threads > [ 0.021878195,6] CPU: CPU from DT PIR=0x0018 Server#=0x18 State=3 > [ 0.021887826,6] CPU: 1 secondary threads > [ 0.021894705,6] CPU: CPU from DT PIR=0x001c Server#=0x1c State=3 > [ 0.021904113,6] CPU: 1 secondary threads > [ 0.023185494,5] PLAT: Using SuperIO UART > [ 0.023483354,7] UART: Using LPC IRQ 4 > [ 0.028248102,5] PLAT: Detected QEMU POWER9 platform > [ 0.028385817,5] PLAT: Detected BMC platform ast2500:openbmc > [ 0.059238262,5] CPU: All 8 processors called in... > [ 0.059731948,3] SBE: Master chip ID not found. > [ 0.060360004,7] LPC: Routing irq 10, policy: 0 (r=1) > [ 0.060430008,7] LPC: SerIRQ 10 using route 0 targetted at OPAL > [ 0.082669345,5] HIOMAP: Negotiated hiomap protocol v2 > [ 0.082815227,5] HIOMAP: Block size is 4KiB > [ 0.082931096,5] HIOMAP: BMC suggested flash timeout of 0s > [ 0.083083386,5] HIOMAP: Flash size is 128MiB > [ 0.083208145,5] HIOMAP: Erase granule size is 4KiB > [ 0.101598300,3] FFS: Reading the flash has returned all 0xFF. > [ 0.102380169,3] Are you reading erased flash? > [ 0.102989778,3] Is something else using the flash controller? > [ 0.104256269,4] FLASH: No ffs info; using raw device only > [ 0.111351131,3] FFS: Reading the flash has returned all 0xFF. > [ 0.111956298,3] Are you reading erased flash? > [ 0.112298116,3] Is something else using the flash controller? > [ 0.112769608,3] FLASH: Can't open ffs handle > [ 0.118534935,3] FFS: Reading the flash has returned all 0xFF. > [ 0.118727529,3] Are you reading erased flash? > [ 0.118901877,3] Is something else using the flash controller? > [ 0.119122596,3] FLASH: Can't open ffs handle > [ 0.124552393,3] FFS: Reading the flash has returned all 0xFF. > [ 0.124754268,3] Are you reading erased flash? > [ 0.124929350,3] Is something else using the flash controller? > [ 0.125161706,3] FLASH: Can't open ffs handle > [ 0.130843022,3] FFS: Reading the flash has returned all 0xFF. > [ 0.131573998,3] Are you reading erased flash? > [ 0.132222914,3] Is something else using the flash controller? > [ 0.133019649,3] FLASH: Can't open ffs handle > [ 0.139311960,3] FFS: Reading the flash has returned all 0xFF. > [ 0.140161437,3] Are you reading erased flash? > [ 0.140758194,3] Is something else using the flash controller? > [ 0.141563127,3] FLASH: Can't open ffs handle > [ 0.147577961,3] FFS: Reading the flash has returned all 0xFF. > [ 0.147826006,3] Are you reading erased flash? > [ 0.148010033,3] Is something else using the flash controller? > [ 0.148235992,3] FLASH: Can't open ffs handle > [ 0.164159120,2] NVRAM: Failed to load > [ 0.164919948,2] NVRAM: Failed to load > [ 0.165660815,5] STB: secure boot not supported > [ 0.166186999,5] STB: trusted boot not supported > [ 0.167713518,2] NVRAM: Failed to load > [ 0.168396572,7] LPC: Routing irq 4, policy: 0 (r=1) > [ 0.168483704,7] LPC: SerIRQ 4 using route 1 targetted at OPAL > [ 0.170096776,3] SLW: HOMER base not set 0 > [ 0.170727301,5] Unable to log error > [ 0.171176441,2] NVRAM: Failed to load > [ 0.171794002,3] OCC: No HOMER detected, assuming no pstates > [ 0.172042505,5] Unable to log error > [ 0.172258661,2] NVRAM: Failed to load > [ 0.172450441,2] NVRAM: Failed to load > [ 0.173371461,4] FLASH: Can't load resource id:4. No system flash found > [ 0.173665124,4] FLASH: Can't load resource id:3. No system flash found > [ 0.173909805,4] FLASH: Can't load resource id:2. No system flash found > [ 0.174203921,4] FLASH: Can't load resource id:0. No system flash found > [ 0.174435488,4] FLASH: Can't load resource id:1. No system flash found > [ 0.176006253,3] IMC: IMC Catalog load failed > [ 0.176868893,2] NVRAM: Failed to load > [ 0.177017819,2] NVRAM: Failed to load > [ 0.177147089,2] NVRAM: Failed to load > [ 0.177288524,2] NVRAM: Failed to load > [ 0.201502496,3] CAPP: Error loading ucode lid. index=200d1 > [ 0.237179637,2] NVRAM: Failed to load > [ 0.247717144,5] PCI: Resetting PHBs and training links... > [ 1.258824876,5] PCI: Probing slots... > [ 1.283504033,3] PHB#0000:01:00.0 pci_find_ecap hit a loop ! > [ 1.287503079,5] PCI Summary: > [ 1.287929661,5] PHB#0000:00:00.0 [ROOT] 1014 04c1 R:00 C:060400 B:01..01 > [ 1.288290952,5] PHB#0000:01:00.0 [EP ] 8086 10d3 R:00 C:020000 ( ethernet) > [ 1.288658004,5] PHB#0001:00:00.0 [ROOT] 1014 04c1 R:00 C:060400 B:01..01 > [ 1.288913280,5] PHB#0002:00:00.0 [ROOT] 1014 04c1 R:00 C:060400 B:01..01 > [ 1.289159735,5] PHB#0003:00:00.0 [ROOT] 1014 04c1 R:00 C:060400 B:01..01 > [ 1.289426025,5] PHB#0004:00:00.0 [ROOT] 1014 04c1 R:00 C:060400 B:01..01 > [ 1.289786894,5] PHB#0005:00:00.0 [ROOT] 1014 04c1 R:00 C:060400 B:01..01 > [ 1.290355197,4] FLASH: Failed to load VERSION data > [ 1.476340800,5] INIT: Waiting for kernel... > [ 1.476473489,5] INIT: platform wait for kernel load failed > [ 1.476626963,5] INIT: Assuming kernel at 0x20000000 > [ 1.476781225,5] INIT: 64-bit LE kernel discovered > [ 1.477063732,3] OCC: Unassigned OCC Common Area. No sensors found > [ 1.477398857,2] NVRAM: Failed to load > > I'm happy to take more suggestions. :) > > > Cheers, > -- > Cyril Brulebois (kibi@debian.org) <https://debamax.com/> > D-I release manager -- Release team member -- Freelance Consultant
Attachment:
signature.asc
Description: PGP signature