[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] target/ppc: Fix e6500 boot
From: |
address@hidden |
Subject: |
Re: [PATCH] target/ppc: Fix e6500 boot |
Date: |
Tue, 28 Dec 2021 12:32:20 +0100 |
>From: "Fabiano Rosas" farosas@linux.ibm.com
>To: "mario@locati.it" mario@locati.it, clg@kaod.org
>Cc: danielhb413@gmail.com, qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
>balaton@eik.bme.hu
>Date: Mon, 27 Dec 2021 17:05:46 -0300
>Subject: Re: [PATCH] target/ppc: Fix e6500 boot
>
>"mario@locati.it" <mario@locati.it> writes:
>
>> I have updated the guest VM but I get exactly the same result except that
>> now I have libc-2.33.so installed.
>>
>> [...]
>> VFS: Mounted root (ext4 filesystem) on device 254:0.
>> devtmpfs: mounted
>> Freeing unused kernel image (initmem) memory: 468K
>> This architecture does not have kernel memory protection.
>> Run /sbin/init as init process
>> random: fast init done
>> systemd[1]: illegal instruction (4) at 3fff8b7e615c nip 3fff8b7e615c lr
>> 3fff8b7e613c code 1 in libc-2.33.so[3fff8b799000+1fe000]
>> systemd[1]: code: 60000000 38600006 9122b7d0 4801bf19 60000000 60000000
>> 8122b7d0 2c090004
>> systemd[1]: code: 40820014 39200005 60000000 9122b7d0 <00000000> 60000000
>> 8122b7d0 2c090005
>> Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004
>> Rebooting in 180 seconds..
>
>Can you make the hdd_debian_ppc64_new.img available? We won't be able to
>reproduce the exact same scenario because we can't run KVM, but if it
>boots with TCG we can at least look around the code that is failing to
>see if it gives us any clues.
Sure, you may download the hdd of the VM I am using on the NXP T2080RDB from
https://repo.powerprogress.org/t2080rdb/qemu/hdd_debian_sid_ppc64.qcow2
I have compressed the original raw disk (18.8GB) into a smaller qcow2 (3.8GB),
I cannot get a smaller image sorry.
Use the following kernel to launch it
https://repo.powerprogress.org/t2080rdb/qemu/uImage_5.16-rc6
No matter which video output I try, but on my ubuntu 20.04 x86_64 I cannot get
X11 working, so to launch qemu I use
qemu-system-ppc64 -accel tcg -M ppce500 -cpu e6500 -smp 4 -m 2G -vga none
-nographic -net nic -net user -drive
format=qcow2,file=hdd_debian_sid_ppc64.qcow2,index=0,if=virtio -kernel
uImage_5.16-rc6 -append "root=/dev/vda rw"
that do now work
qemu-system-ppc64 -accel tcg -M ppce500 -cpu e5500 -smp 4 -m 2G -vga none
-nographic -net nic -net user -drive
format=qcow2,file=hdd_debian_sid_ppc64.qcow2,index=0,if=virtio -kernel
uImage_5.16-rc6 -append "root=/dev/vda rw"
that works, the system sees e5500 cores, whereas running it on the devkit, the
system see the host e6500 cores
- [PATCH] target/ppc: Fix e6500 boot, Fabiano Rosas, 2021/12/13
- Re: [PATCH] target/ppc: Fix e6500 boot, Cédric Le Goater, 2021/12/13
- Re: [PATCH] target/ppc: Fix e6500 boot, BALATON Zoltan, 2021/12/13
- Re: [PATCH] target/ppc: Fix e6500 boot, address@hidden, 2021/12/25
- Re: [PATCH] target/ppc: Fix e6500 boot, BALATON Zoltan, 2021/12/25
- Re: [PATCH] target/ppc: Fix e6500 boot, Cédric Le Goater, 2021/12/26
- Re: [PATCH] target/ppc: Fix e6500 boot, address@hidden, 2021/12/27
- Re: [PATCH] target/ppc: Fix e6500 boot, Fabiano Rosas, 2021/12/27
- Re: [PATCH] target/ppc: Fix e6500 boot, BALATON Zoltan, 2021/12/27
- Re: [PATCH] target/ppc: Fix e6500 boot,
address@hidden <=
- Re: [PATCH] target/ppc: Fix e6500 boot, BALATON Zoltan, 2021/12/27
Re: [PATCH] target/ppc: Fix e6500 boot, Cédric Le Goater, 2021/12/15