From: Corentin Labbe <clabbe.montjoie@gmail.com>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: sparclinux@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] sparc: crash when using initrd > 5M
Date: Wed, 06 Feb 2019 09:06:39 +0000 [thread overview]
Message-ID: <20190206090639.GA32428@Red> (raw)
In-Reply-To: <8da59b77-eef2-4897-5254-0f6fb22539a6@ilande.co.uk>
On Wed, Feb 06, 2019 at 07:37:29AM +0000, Mark Cave-Ayland wrote:
> On 06/02/2019 07:28, Corentin Labbe wrote:
>
> >>> Hello
> >>>
> >>> Sorry even with the patch I still hit the issue.
> >>>
> >>> I have added some debug and at least qemu set initrd_size correctly now.
> >>>
> >>> I have tried to compile openbios-sparc32 for debugging but fail with
> >>> arch/sparc32/context.c:116:5: error: PIC register clobbered by 'l7' in 'asm'
> >>> asm __volatile__ ("\n\tcall __switch_context"
> >>> ^~~
> >>> make[1]: *** [rules.mak:219: target/arch/sparc32/context.o] Error 1
> >>> (gcc 7.2 and gc 6.4 with binutils 2.30)
> >>
> >> Hmmm. One other thing I've noticed is that newer kernels tend need a minimum of 256M
> >> RAM to start up - does it work if you add -m 256 to your command line?
> >>
> >>
> >
> > I have already set 256M of RAM. (and tried 512)
>
> I wonder then if this is being triggered by a recent kernel change? I tend to test
> using the latest Debian ports ISOs which are currently running 4.9 and that booted
> fine when I was testing the patches above.
>
> Can you try with a few older kernels to see if this is the case?
>
>
Hello
Good catch, it boot fine with 4.9.99.
A start a long git bisect...
Regards
WARNING: multiple messages have this Message-ID (diff)
From: Corentin Labbe <clabbe.montjoie@gmail.com>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: sparclinux@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] sparc: crash when using initrd > 5M
Date: Wed, 6 Feb 2019 10:06:39 +0100 [thread overview]
Message-ID: <20190206090639.GA32428@Red> (raw)
In-Reply-To: <8da59b77-eef2-4897-5254-0f6fb22539a6@ilande.co.uk>
On Wed, Feb 06, 2019 at 07:37:29AM +0000, Mark Cave-Ayland wrote:
> On 06/02/2019 07:28, Corentin Labbe wrote:
>
> >>> Hello
> >>>
> >>> Sorry even with the patch I still hit the issue.
> >>>
> >>> I have added some debug and at least qemu set initrd_size correctly now.
> >>>
> >>> I have tried to compile openbios-sparc32 for debugging but fail with
> >>> arch/sparc32/context.c:116:5: error: PIC register clobbered by 'l7' in 'asm'
> >>> asm __volatile__ ("\n\tcall __switch_context"
> >>> ^~~
> >>> make[1]: *** [rules.mak:219: target/arch/sparc32/context.o] Error 1
> >>> (gcc 7.2 and gc 6.4 with binutils 2.30)
> >>
> >> Hmmm. One other thing I've noticed is that newer kernels tend need a minimum of 256M
> >> RAM to start up - does it work if you add -m 256 to your command line?
> >>
> >>
> >
> > I have already set 256M of RAM. (and tried 512)
>
> I wonder then if this is being triggered by a recent kernel change? I tend to test
> using the latest Debian ports ISOs which are currently running 4.9 and that booted
> fine when I was testing the patches above.
>
> Can you try with a few older kernels to see if this is the case?
>
>
Hello
Good catch, it boot fine with 4.9.99.
A start a long git bisect...
Regards
next prev parent reply other threads:[~2019-02-06 9:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 15:48 sparc: crash when using initrd > 5M Corentin Labbe
2019-01-03 15:48 ` [Qemu-devel] " Corentin Labbe
2019-01-18 13:33 ` Mark Cave-Ayland
2019-02-01 14:15 ` Mark Cave-Ayland
2019-02-01 14:15 ` Mark Cave-Ayland
2019-02-05 9:11 ` Corentin Labbe
2019-02-05 9:11 ` Corentin Labbe
2019-02-05 16:45 ` Mark Cave-Ayland
2019-02-05 16:45 ` Mark Cave-Ayland
2019-02-06 7:28 ` Corentin Labbe
2019-02-06 7:28 ` Corentin Labbe
2019-02-06 7:37 ` Mark Cave-Ayland
2019-02-06 7:37 ` Mark Cave-Ayland
2019-02-06 9:06 ` Corentin Labbe [this message]
2019-02-06 9:06 ` Corentin Labbe
2019-02-06 19:38 ` Corentin Labbe
2019-02-06 19:38 ` Corentin Labbe
2019-02-08 16:09 ` Mark Cave-Ayland
2019-02-08 16:09 ` Mark Cave-Ayland
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=20190206090639.GA32428@Red \
--to=clabbe.montjoie@gmail.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=qemu-devel@nongnu.org \
--cc=sparclinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.