Page 4 of 9
Re: Kernel 5.13
Posted: Sat May 08, 2021 11:56 pm
by xeno74
kilaueabart wrote: Sat May 08, 2021 11:05 pm
A4 seems to work OK here,
Great! Thanks a lot for testing!
Re: Kernel 5.13
Posted: Sun May 09, 2021 11:05 am
by xeno74
Hi All,
I downloaded and compiled the latest git kernel for the X5000 today. Unfortunately the Xorg issue still exists.
I will revert the PowerPC updates
5.13-1 and
5.13-2 for the
alpha5 with the following commands:
Code: Select all
git revert ab159ac569fddf812c0a217d6dbffaa5d93ef88f -m 1
(PowerPC updates 5.13-2)
----------------
Code: Select all
git revert c70a4be130de333ea079c59da41cc959712bb01c -m 1
(PowerPC updates 5.13-1)
Cheers,
Christian
Re: Kernel 5.13
Posted: Mon May 10, 2021 12:19 am
by xeno74
Hi All,
The
alpha5 of kernel
5.13 is available for testing.
New:
Download:
linux-image-5.13-alpha5-X1000_X5000.tar.gz
Please test the kernels.
Thanks,
Christian
Re: Kernel 5.13
Posted: Mon May 10, 2021 8:14 am
by Skateman
Kernel 5.13 Alpha5 is running fine on the AmigaOne X5000
Big picture
http://www.skateman.nl/wp-content/uploa ... 081222.png
Re: Kernel 5.13
Posted: Mon May 10, 2021 9:23 am
by xeno74
Skateman wrote: Mon May 10, 2021 8:14 am
Kernel 5.13 Alpha5 is running fine on the AmigaOne X5000
Thank you for testing the alpha5!

Re: Kernel 5.13
Posted: Mon May 10, 2021 2:43 pm
by xeno74
Hi All,
I compiled the RC1 today. Unfortunately the Xorg issue still exists and it doesn't boot in a virtual e5500 QEMU machine anymore.
Cheers,
Christian
Re: Kernel 5.13
Posted: Tue May 11, 2021 11:44 am
by xeno74
Hi All,
The kernel 5.13 has some unsolved issues and some not integrated patches. Currently it is not possible to release 5.13 kernels because of these issues. The kernel developers haven’t figured out where the problematic code is. We have bisected a lot but the Xorg issue overlaps with a boot issue. We can’t figure out the first bad commit for the Xorg issue if the kernel doesn’t boot in this time where the first bad commit is. Additionally the kernel doesn’t boot in a virtual e5500 QEMU machine anymore since the RC1 of kernel 5.13.
I will skip the kernel 5.13 test time until the RC1 of kernel 5.14.
I can‘t release these unreliable 5.13 kernels for the X1000 and X5000.
In the meantime I will release some stable 5.10 LTS kernels.
They are very stable and there weren’t any issues in the test time. The kernel 5.10 is very modern and offers the same features as the 5.11, 5.12, and 5.13 kernels and is more stable. If you have a new hardware and the kernel 5.10 doesn’t offer a driver for it then you can try the 5.11, 5.12, 5.13 kernels. Additionally I can try to backport the new driver.
Cheers,
Christian
Re: Kernel 5.13
Posted: Tue May 11, 2021 6:39 pm
by kilaueabart
Downloaded and installed 5.13 alpha 5 yesterday morning, but didn't get around to rebooting until today. It works.
I also downloaded the final 5.10 today. I'm a bit confused about it. Is it something to keep on hand in case a newer one I'm using for testing fails? I was keeping 5.12 for that,. Is 5.10 missing a lot of newer features? I suppose I should study the git logs and see if I can figure out what's going on.
Re: Kernel 5.13
Posted: Wed May 12, 2021 9:42 am
by xeno74
kilaueabart wrote: Tue May 11, 2021 6:39 pm
Downloaded and installed 5.13 alpha 5 yesterday morning, but didn't get around to rebooting until today. It works.
Thanks a lot for testing!

Re: Kernel 5.13
Posted: Thu May 13, 2021 4:35 pm
by xeno74
Christophe wrote:
Please fetch
https://github.com/chleroy/linux.git and try the branch for_christian.
This is a revert of approx a dozen of commits around the changes to 64e on top of v5.13-rc1.
If the top of the branch works for you, it would be great if you can find out which one of the reverts fixes the problem for real.
Link:
[FSL P50x0] Xorg always restarts again and again after the the PowerPC updates 5.13-1
I checked out the branch
for_christian from his git:
Code: Select all
git clone https://github.com/chleroy/linux.git -b for_christian a
Edit: It's working! Great! I can use the RC1 on my X5000. The issue is
definitely somewhere in the interrupt code.