From: BALATON Zoltan <balaton@eik.bme.hu>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: Looking for advise on debugging a non-boot kernel on qemu-system-sh4
Date: Fri, 22 Oct 2021 23:06:48 +0200 (CEST) [thread overview]
Message-ID: <d2553511-b83c-d4f1-5a88-b661bc97eb@eik.bme.hu> (raw)
In-Reply-To: <f0933be1-75ee-b053-1f53-f96258d41163@physik.fu-berlin.de>
On Thu, 21 Oct 2021, John Paul Adrian Glaubitz wrote:
> On 10/21/21 15:49, BALATON Zoltan wrote:
>> So somthing seems to overwrite it. Maybe you can try building an uncompressed
>> kernel or one using a different compression and see if that does the same, at
>> least that way we can see if it's in the decompressing or later. I think it's
>> past linux/arch/sh/boot/compressed/head32.S and maybe somewhere in decompress_kernel
>> but not sure which decompression it uses. Kernel config is also missing to check
>> but I probably give up at this point and let you experiment some more.
>
> I think I've seen problems with compressed kernel images and QEMU before. I will switch
> to an uncompressed kernel and try again.
How did you compile the kernel that does not boot? What config have you
used? I've tried to reproduce it by compiling a kernel with
rts7751r2d1_defconfig and different compression methods but it did start
and never got the problem seen with your kernel. Maybe it's the gcc
version? My cross compiler is 8.4.0 and you seem to use 10.x. Maybe newer
gcc uses something that's not emulated correctly? It would be interesting
to identify what's causing the problem.
Regards,
BALATON Zoltan
next prev parent reply other threads:[~2021-10-22 21:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 9:49 Looking for advise on debugging a non-boot kernel on qemu-system-sh4 John Paul Adrian Glaubitz
2021-10-21 12:12 ` BALATON Zoltan
2021-10-21 12:40 ` John Paul Adrian Glaubitz
2021-10-21 13:49 ` BALATON Zoltan
2021-10-21 15:07 ` John Paul Adrian Glaubitz
2021-10-22 21:06 ` BALATON Zoltan [this message]
2021-10-22 21:49 ` John Paul Adrian Glaubitz
2021-10-22 23:08 ` John Paul Adrian Glaubitz
2021-10-23 1:07 ` BALATON Zoltan
2021-10-23 1:12 ` John Paul Adrian Glaubitz
2021-10-23 13:22 ` BALATON Zoltan
2021-10-25 22:10 ` John Paul Adrian Glaubitz
2021-10-25 22:40 ` BALATON Zoltan
2022-01-12 11:27 ` John Paul Adrian Glaubitz
2022-01-12 14:44 ` BALATON Zoltan
2021-10-21 13:10 ` Thomas Huth
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=d2553511-b83c-d4f1-5a88-b661bc97eb@eik.bme.hu \
--to=balaton@eik.bme.hu \
--cc=glaubitz@physik.fu-berlin.de \
--cc=qemu-devel@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).