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
Subject: Re: [PATCH] target/ppc: Fix e6500 boot
Date: Mon, 27 Dec 2021 17:05:46 -0300 [thread overview]
Message-ID: <87tuetrexx.fsf@linux.ibm.com> (raw)
In-Reply-To: <R4SG07$EE0184281B6DB251884FD0A5E86E2438@locati.it>
"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.
next prev parent reply other threads:[~2021-12-27 20:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 13:35 [PATCH] target/ppc: Fix e6500 boot Fabiano Rosas
2021-12-13 14:03 ` Cédric Le Goater
2021-12-13 14:59 ` Fabiano Rosas
2021-12-13 19:51 ` BALATON Zoltan
2021-12-25 18:46 ` mario
2021-12-25 21:53 ` BALATON Zoltan
2021-12-26 17:57 ` Cédric Le Goater
2021-12-27 19:12 ` mario
2021-12-27 20:05 ` Fabiano Rosas [this message]
2021-12-27 20:33 ` BALATON Zoltan
2021-12-28 11:32 ` mario
2021-12-27 20:31 ` BALATON Zoltan
2022-01-10 8:04 ` Cédric Le Goater
2022-01-11 9:04 ` mario
2021-12-15 16:52 ` Cédric Le Goater
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=87tuetrexx.fsf@linux.ibm.com \
--to=farosas@linux.ibm.com \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=mario@locati.it \
--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).