Thorsten Leemhuis <regressi...@leemhuis.info> writes: > [Note: this mail is primarily send for documentation purposes and/or for > regzbot, my Linux kernel regression tracking bot. That's why I removed > most or all folks from the list of recipients, but left any that looked > like a mailing lists. These mails usually contain '#forregzbot' in the > subject, to make them easy to spot and filter out.] > > [TLDR: I'm adding this regression report to the list of tracked > regressions; all text from me you find below is based on a few templates > paragraphs you might have encountered already already in similar form.] > > Hi, this is your Linux kernel regression tracker. > > On 12.10.22 08:51, Christian Zigotzky wrote: >> 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. > > Thanks for the report. To be sure below issue doesn't fall through the > cracks unnoticed, I'm adding it to regzbot, my Linux kernel regression > tracking bot: > > #regzbot ^introduced c2e7a19827eec443a7cb > #regzbot title ppc: PASemi PA6T CPU: Network Manager and LightDM and > fill volume with data > #regzbot ignore-activity > > This isn't a regression? This issue or a fix for it are already > discussed somewhere else? It was fixed already? You want to clarify when > the regression started to happen? Or point out I got the title or > something else totally wrong? Then just reply -- ideally with also > telling regzbot about it, as explained here: > https://linux-regtracking.leemhuis.info/tracked-regression/
#regzbot fixed-by: 40ff21432883 cheers
