Hi Christophe,

Thanks a lot for your answer. OK, now, I know, that I don’t need to test it. After the boot of the latest git kernel, my system was extremely damaged. Some config files has a size of several gigabytes for example the resolv.conf. I tried to repair this Debian system but without any success.
I copied with dd and Netcat via network another rootfs from another computer to the damaged partition.
I don’t have the time to do it always again and again after a bad bisect result.
I will wait some weeks and try it again.

Cheers,
Christian

On 13. Oct 2022, at 09:28, Christophe Leroy [off-list ref] wrote:



quoted

Le 13/10/2022 à 09:03, Christian Zigotzky a écrit :
Hi Andrew,

Does this patch also affect 64-bit kernels?

We use often 32-bit userlands with 64-bit kernels.

As far as I understand, it was already correct for 32-bit userlands with 
64 bit kernels, aka compat.

The patch applies the same approach for 32 bit kernels, as explained in 
the commit message : "Fix this by having 32-bit kernels share those 
syscall definitions with compat."

Christophe

quoted

Cheers,
Christian

quoted

quoted

On 12. Oct 2022, at 09:56, Andrew Donnellan [off-list ref] wrote:

On Wed, 2022-10-12 at 08:51 +0200, Christian Zigotzky wrote:

quoted

Hi All,

I use the Nemo board with a PASemi PA6T CPU and have some issues
since the first PowerPC updates for the kernel 6.1.

I successfully compiled the git kernel with the first PowerPC updates
two days ago.

Unfortunately this kernel is really dangerous. Many things for
example Network Manager and LightDM don't work anymore and produced
several gigabyte of config files till the partition has been filled.

I deleted some files like the resolv.conf that had a size over 200
GB!

Unfortunately, MintPPC was still damaged. For example LightDM doesn't
work anymore and the MATE desktop doesn't display any icons anymore
because Caja wasn't able to reserve memory anymore.

In this case, bisecting isn't an option and I have to wait some
weeks. It is really difficult to find the issue if the userland will
damaged again and again.

Could you try with
https://patchwork.ozlabs.org/project/linuxppc-dev/patch/20221012035335.866440-1-npiggin@gmail.com/
to see if your issues are related to that?

Andrew

-- 
Andrew Donnellan    OzLabs, ADL Canberra
ajd@linux.ibm.com   IBM Australia Limited