From: Michael Ellerman <mpe@ellerman.id.au>
To: Christophe Leroy <christophe.leroy@csgroup.eu>,
Eddie James <eajames@linux.ibm.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Cc: "paulus@samba.org" <paulus@samba.org>
Subject: Re: KUEP broken on FSP2?
Date: Tue, 10 Oct 2023 22:03:18 +1100 [thread overview]
Message-ID: <87wmvurb7t.fsf@mail.lhotse> (raw)
In-Reply-To: <75905aa0-5c25-bff0-8ef9-4792b57f5f1a@csgroup.eu>
Christophe Leroy <christophe.leroy@csgroup.eu> writes:
> Le 09/10/2023 à 17:12, Eddie James a écrit :
>>
>> On 10/9/23 08:14, Michael Ellerman wrote:
>>> Eddie James <eajames@linux.ibm.com> writes:
>>>> Hi,
>>>>
>>>> I'm attempting to run linux 6.1 on my FSP2, but my kernel crashes
>>>> attempting to get into userspace. The init script works, but the first
>>>> binary (mount) I run results in oops. Can anyone help me to debug this
>>>> further or suggest anything?
>>> Hi Eddie,
>>>
>>> It looks like breakage in syscall_exit_finish.
>>> Can you test this? Patch is against v6.1.
>>
>>
>> That worked! Perfect. Thank you very much! Will you send it upstream?
>
> Well spotted Michael. Looks like I messed it up with commit 6f76a01173cc
> ("powerpc/syscall: implement system call entry/exit logic in C for PPC32")
I should have spotted it when applying ;)
That old asm code with all those unnamed labels was super fragile.
> Thanks for fixing.
No worries.
cheers
next prev parent reply other threads:[~2023-10-10 11:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 19:06 KUEP broken on FSP2? Eddie James
2023-10-06 5:21 ` Christophe Leroy
2023-10-06 15:43 ` Eddie James
2023-10-06 15:55 ` Christophe Leroy
2023-10-06 16:16 ` Eddie James
2023-10-09 13:14 ` Michael Ellerman
2023-10-09 15:12 ` Eddie James
2023-10-09 16:02 ` Christophe Leroy
2023-10-10 11:03 ` Michael Ellerman [this message]
2023-10-10 10:59 ` Michael Ellerman
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=87wmvurb7t.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=christophe.leroy@csgroup.eu \
--cc=eajames@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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).