From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Darren Stevens <darren@stevens-zone.net>,
Andrew Donnellan <ajd@linux.ibm.com>,
npiggin@gmail.com, rmclure@linux.ibm.com,
mad skateman <madskateman@gmail.com>,
Olof Johansson <olof@lixom.net>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Trevor Dickinson <rtd2@xtra.co.nz>,
Christian Zigotzky <info@xenosoft.de>
Subject: Re: Issues with the first PowerPC updates for the kernel 6.1
Date: Sat, 29 Oct 2022 15:52:22 +0200 [thread overview]
Message-ID: <b2d2af43-f5e4-dc3e-d57b-a33c942c964f@xenosoft.de> (raw)
In-Reply-To: <fe06590f-6db6-f5cc-72ec-e635f66f3d3b@xenosoft.de>
On 29 October 2022 at 01:44 pm, Christian Zigotzky wrote:
> On 17 October 2022 at 09:53 am, Christian Zigotzky wrote:
>>> On 17. Oct 2022, at 02:43, Michael Ellerman <mpe@ellerman.id.au> wrote:
>>> Previously BIG_ENDIAN && GENERIC_CPU would use -mcpu=power5, now it
>>> uses
>>> -mcpu=power4.
>> Maybe this is the issue. We will wait and not release the RC1 for
>> testing because it is a risk for our testers to test these new
>> kernels because of this issue.
>>
>>>
>>> cheers
>>>
>>>
> I compiled the RC2 of kernel 6.0 today.
Typo: I mean the RC2 of kernel 6.1.
>
> After the first boot of the RC2, the file system was immediately to
> 100% used. This is the same issue we have seen with the git kernel 3
> weeks ago.
>
> The Cyrus+ and Nemo boards are affected.
>
> I wrote 3 weeks ago:
>
> Hi All,
>
> I successfully compiled the latest git kernel with the first PowerPC
> updates yesterday.
>
> 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.
>
> Cheers,
> Christian
>
> ---
>
> Maybe there is an issue in my kernel configs. Could you please check
> the configs? Please find attached the configs. Could you please test
> the RC2 on your FSL and pasemi machines?
>
> Thanks,
> Christian
>
next prev parent reply other threads:[~2022-10-29 13:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 6:51 Issues with the first PowerPC updates for the kernel 6.1 Christian Zigotzky
2022-10-12 7:56 ` Andrew Donnellan
2022-10-13 7:03 ` Christian Zigotzky
2022-10-13 7:28 ` Christophe Leroy
2022-10-13 9:42 ` Christian Zigotzky
2022-10-13 9:46 ` Christian Zigotzky
2022-10-14 16:11 ` Christian Zigotzky
2022-10-14 18:47 ` Olof Johansson
2022-10-17 0:17 ` Michael Ellerman
2022-10-16 16:46 ` Segher Boessenkool
2022-10-16 17:32 ` Christian Zigotzky
2022-10-17 0:42 ` Michael Ellerman
2022-10-17 7:53 ` Christian Zigotzky
[not found] ` <fe06590f-6db6-f5cc-72ec-e635f66f3d3b@xenosoft.de>
2022-10-29 13:52 ` Christian Zigotzky [this message]
2022-10-30 13:30 ` Christian Zigotzky
2022-11-01 16:46 ` Christian Zigotzky
2022-10-29 15:33 ` Segher Boessenkool
2022-10-30 7:57 ` Christian Zigotzky
2022-10-15 9:50 ` Andrew Donnellan
2022-10-15 21:05 ` Christian Zigotzky
2022-10-30 16:46 ` Issues with the first PowerPC updates for the kernel 6.1 #forregzbot Thorsten Leemhuis
2022-11-03 0:08 ` 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=b2d2af43-f5e4-dc3e-d57b-a33c942c964f@xenosoft.de \
--to=chzigotzky@xenosoft.de \
--cc=ajd@linux.ibm.com \
--cc=darren@stevens-zone.net \
--cc=info@xenosoft.de \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madskateman@gmail.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=olof@lixom.net \
--cc=rmclure@linux.ibm.com \
--cc=rtd2@xtra.co.nz \
/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).