Re: [PATCH v3 00/13] Pegasos2 clean up and pegasos1 emulation

[BALATON Zoltan <balaton@eik.bme.hu>]

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

On Mon, 3 Nov 2025, BALATON Zoltan wrote:
> On Sun, 2 Nov 2025, Yogesh Vyas wrote:
>> On 10/28/25 1:48 AM, BALATON Zoltan wrote:
>>> Trying to read invalid spr 1012 (0x3f4) at 00000000c0013f48
>>> [    0.000000] Using CHRP machine description
>>> [    0.000000] Total memory = 512MB; using 1024kB for hash table (at 
>>> cff00000)
>>> [    0.000000] Initializing cgroup subsys cpuset
>>> [    0.000000] Initializing cgroup subsys cpu
>>> [    0.000000] Initializing cgroup subsys cpuacct
>>> [    0.000000] Linux version 3.16.0-6-powerpc (debian- 
>>> kernel@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 Debian 
>>> 3.16.56-1+deb8u1 (2018-05-08)
>>> [    0.000000] Found initrd at 0xc15a2000:0xc1b0b90d
>>> [    0.000000] chrp type = 6 [Genesi Pegasos]
>>> 
>>> Are you using this same vmlinuz-chrp.initrd?
>>> 
>>> $ md5sum vmlinuz-chrp.initrd
>>> a440d76c1d2ccfa86bdff6dba017cf39  vmlinuz-chrp.initrd
>> 
>> Yes, md5sum is same as you mentioned:
>> yogi@fedora:~/work/images$ md5sum vmlinuz-chrp.initrd
>> a440d76c1d2ccfa86bdff6dba017cf39  vmlinuz-chrp.initrd
>> 
>> Could you please share your Qemu configure command line?
>> I can try one more time if that's different than mine.
>> I used below configure command line:
>> '../configure' '--target-list=ppc64-softmmu,ppc-softmmu' '--enable-virtfs'
>
> I don't see how configure options could have anyhing to do with that but I've 
> tested that this works on my machine:
>
> configure --disable-download --disable-tools --target-list=ppc64-softmmu
> qemu-system-ppc64 -M pegasos2 -serial stdio -kernel vmlinuz-chrp.initrd 
> -append "---" -cdrom debian-8.11.0-powerpc-netinst.iso
>
> The configure options are just to only compile what's needed but it should 
> work anyway with your or any options too as long as qemu-system-ppc or 
> qemu-system-ppc64 is compiled. Can you test on a different machine?

Someone else reported a possible regression maybe related to this patch 
too but I could not reproduce that either. Can you check what configure 
says about FDT and if you're using some external FDT library? I've tested 
with the internal fdt included with QEMU which works and also with libfdt 
1.6.1 from my distro that also had no problems. I have no better idea what 
else could cause it than maybe some issue with some external libfdt 
version.

Regards,
BALATON Zoltan