segfault #267
Comments
|
FYI. I am running the same version of ticker on the same O/S on a rPi 4 and it works well |
|
This probably a bug with 16K pages. If you use the kernel=kernel8.img in the /boot/firmware/config.txt (the one that is actually used on the RPI4) it willl work because this is a 4K page kernel. I've tested this solution myself. To the developer: This bug is related to the ability in newer kernels to work with 16K memory pages. It means that something in your components is probably not happy with this king of configuration. I hope it can shed some light on what's happening. |
|
Thanks for reporting the issue and the suggestion on the root cause. I'll take a look into fixing it in the next week or two |
|
Thank you for taking the time to respond to this problem.Been using ticker for years on rPi. It's regrettable it no longer runs.
Do you know if i change the kernel page size in config.txt will result in any performance issues on the rPi5 ?
On Thursday, May 30, 2024 at 04:31:02 AM CDT, thaihugo ***@***.***> wrote:
This probably a bug with 16K pages. If you use the kernel=kernel8.img in the /boot/firmware/config.txt (the one that is actually used on the RPI4) it willl work because this is a 4K page kernel. I've tested this solution myself.
To the developer: This bug is related to the ability in newer kernels to work with 16K memory pages. It means that something in your components is probably not happy with this king of configuration. I hope it can shed some light on what's happening.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
Officially, it would be around 10% performance lost approximately. But from my experience, you can't really fell the difference if you are not maxing a CPU with an heavyweight app or an emulation. For desktop work, you will probably forget the speed from 16k pages kernel after a few minutes.
Le 2 juin 2024 11:47:21 UTC, herby-popnecker ***@***.***> a écrit :
… Thank you for taking the time to respond to this problem.Been using ticker for years on rPi. It's regrettable it no longer runs.
Do you know if i change the kernel page size in config.txt will result in any performance issues on the rPi5 ?
On Thursday, May 30, 2024 at 04:31:02 AM CDT, thaihugo ***@***.***> wrote:
This probably a bug with 16K pages. If you use the kernel=kernel8.img in the /boot/firmware/config.txt (the one that is actually used on the RPI4) it willl work because this is a 4K page kernel. I've tested this solution myself.
To the developer: This bug is related to the ability in newer kernels to work with 16K memory pages. It means that something in your components is probably not happy with this king of configuration. I hope it can shed some light on what's happening.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
--
Reply to this email directly or view it on GitHub:
#267 (comment)
You are receiving this because you commented.
Message ID: ***@***.***>
|
|
Good to know.Appreciate the reply.Hopefully, the author will update the app.Sent from my iPadOn Jun 2, 2024, at 8:16 AM, thaihugo ***@***.***> wrote:
Officially, it would be around 10% performance lost approximately. But from my experience, you can't really fell the difference if you are not maxing a CPU with an heavyweight app or an emulation. For desktop work, you will probably forget the speed from 16k pages kernel after a few minutes.
Le 2 juin 2024 11:47:21 UTC, herby-popnecker ***@***.***> a écrit :
Thank you for taking the time to respond to this problem.Been using ticker for years on rPi. It's regrettable it no longer runs.
Do you know if i change the kernel page size in config.txt will result in any performance issues on the rPi5 ?
On Thursday, May 30, 2024 at 04:31:02 AM CDT, thaihugo ***@***.***> wrote:
This probably a bug with 16K pages. If you use the kernel=kernel8.img in the /boot/firmware/config.txt (the one that is actually used on the RPI4) it willl work because this is a 4K page kernel. I've tested this solution myself.
To the developer: This bug is related to the ability in newer kernels to work with 16K memory pages. It means that something in your components is probably not happy with this king of configuration. I hope it can shed some light on what's happening.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
--
Reply to this email directly or view it on GitHub:
#267 (comment)
You are receiving this because you commented.
Message ID: ***@***.***>
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
I don't have access to a system to replicate confirm the fix / replicate this issue but I believe it is related to |
The new v4.6.3 indeed solves the problem. The build runs perfectly on a 16K page kernel. Thanks for solving this so fast! |
|
Glad to hear it fixed the issue! |
Describe the bug
A clear and concise description of what the bug is.
segmentation fault when launching on rPi 5
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Normally, ticker would just launch
Screenshots
If applicable, add screenshots to help explain your problem
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: