From: Yogesh Vyas <yvyas1991@gmail.com>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
Nicholas Piggin <npiggin@gmail.com>,
Markus Armbruster <armbru@redhat.com>,
Harsh Prateek Bora <harshpb@linux.ibm.com>
Subject: Re: [PATCH v3 00/13] Pegasos2 clean up and pegasos1 emulation
Date: Sun, 2 Nov 2025 21:47:24 +0530 [thread overview]
Message-ID: <5250e103-4dd1-44e4-9dcf-7c2df033ae10@gmail.com> (raw)
In-Reply-To: <fd804cb4-d987-5e3d-24e8-0a4fb88e092e@eik.bme.hu>
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'
Regards,
Yogesh Vyas
>
> If so then probably there's something with your QEMU installation.
next prev parent reply other threads:[~2025-11-02 16:18 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-18 15:11 [PATCH v3 00/13] Pegasos2 clean up and pegasos1 emulation BALATON Zoltan
2025-10-18 15:11 ` [PATCH v3 01/13] ppc/vof: Make nextprop behave more like Open Firmware BALATON Zoltan
2025-10-18 15:11 ` [PATCH v3 02/13] hw/ppc/pegasos2: Remove explicit name properties from device tree BALATON Zoltan
2025-10-18 15:11 ` [PATCH v3 03/13] hw/ppc/pegasos2: Change device tree generation BALATON Zoltan
2025-10-20 8:47 ` Philippe Mathieu-Daudé
2025-10-20 13:06 ` BALATON Zoltan
2025-10-20 15:04 ` Philippe Mathieu-Daudé
2025-10-20 8:54 ` Philippe Mathieu-Daudé
2025-10-20 13:02 ` BALATON Zoltan
2025-10-18 15:11 ` [PATCH v3 04/13] hw/ppc/pegasos2: Remove fdt pointer from machine state BALATON Zoltan
2025-10-20 8:48 ` Philippe Mathieu-Daudé
2025-10-18 15:11 ` [PATCH v3 05/13] hw/ppc/pegasos2: Rename mv field in " BALATON Zoltan
2025-10-18 15:11 ` [PATCH v3 06/13] hw/ppc/pegasos2: Add south bridge pointer in the " BALATON Zoltan
2025-10-18 15:11 ` [PATCH v3 07/13] hw/ppc/pegasos2: Move PCI IRQ routing setup to a function BALATON Zoltan
2025-10-18 15:11 ` [PATCH v3 08/13] hw/ppc/pegasos2: Move hardware specific parts out of machine reset BALATON Zoltan
2025-10-18 15:11 ` [PATCH v3 09/13] hw/ppc/pegasos2: Introduce abstract superclass BALATON Zoltan
2025-10-20 8:49 ` Philippe Mathieu-Daudé
2025-10-18 15:11 ` [PATCH v3 10/13] hw/ppc/pegasos2: Add bus frequency to machine state BALATON Zoltan
2025-10-20 8:53 ` Philippe Mathieu-Daudé
2025-10-20 13:26 ` BALATON Zoltan
2025-10-18 15:11 ` [PATCH v3 11/13] hw/boards: Extend DEFINE_MACHINE macro to cover more use cases BALATON Zoltan
2025-10-20 15:05 ` Philippe Mathieu-Daudé
2025-10-20 15:11 ` Philippe Mathieu-Daudé
2025-10-20 15:32 ` Philippe Mathieu-Daudé
2025-10-20 15:40 ` BALATON Zoltan
2025-10-20 15:35 ` BALATON Zoltan
2025-10-21 4:47 ` Harsh Prateek Bora
2025-10-18 15:11 ` [PATCH v3 12/13] hw/ppc/pegasos2: Add Pegasos I emulation BALATON Zoltan
2025-10-18 15:11 ` [PATCH v3 13/13] hw/ppc/pegasos2: Add VOF support for pegasos1 BALATON Zoltan
2025-10-19 6:56 ` [PATCH v3 00/13] Pegasos2 clean up and pegasos1 emulation Yogesh Vyas
2025-10-19 12:07 ` BALATON Zoltan
2025-10-26 5:49 ` Yogesh Vyas
2025-10-26 11:09 ` BALATON Zoltan
2025-10-26 13:18 ` Yogesh Vyas
2025-10-26 16:44 ` BALATON Zoltan
2025-10-26 16:45 ` BALATON Zoltan
2025-10-27 14:24 ` Yogesh Vyas
2025-10-27 20:18 ` BALATON Zoltan
2025-11-02 16:17 ` Yogesh Vyas [this message]
2025-11-03 20:27 ` BALATON Zoltan
2025-11-06 22:20 ` BALATON Zoltan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5250e103-4dd1-44e4-9dcf-7c2df033ae10@gmail.com \
--to=yvyas1991@gmail.com \
--cc=armbru@redhat.com \
--cc=balaton@eik.bme.hu \
--cc=harshpb@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).