-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Segmentation fault with Gitea on a Raspi 4 #3271
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
To save others following the link:
|
Thanks for tracking this this issue. Have the same problem with gitea 1.9.2 to 1.9.4 (arm v6) on my RaspberryPI 4
|
I can confirm that this also affects my |
Another interesting stuff , when I execute gitea under dbg , it works and it can deploy its webserver. At least on archlinux for raspi 4. But outside dbg I got segfault . Why? |
I have the same on my Raspberry Pi 3 B+. Describe the bug To reproduce Expected behaviour Actual behaviour System
|
Even under raspbian running gitea under gdb gitea it works and I can connect to gitea webserver. For someone like me that doesn't understand this stuff it's pretty crazy :) here the screenshots : https://postimg.cc/gallery/2ba368sw2/ |
I haven't started looking at this yet, but you might be able to speed up the investigation if you can run Gitea under strace and capture the output. |
Hi pelwell, this is when I execute
this is when I execute
I suppose you want I run gitea under gdb and run "strace" but I have no idea how to do. Thanks! |
Same here after the upgrade to kernel 4.19.75-v7l+ (SMP) armv7l. Before the upgrade I am running kernel 4.19.66 and gitea was working fine. After the upgrade with no other changes gitea won't start. |
I can reproduce this - it's on the list to look at. |
Is #3279 [raspberrypi-kernel-headers (1.20190925-2): Wrong exec format in scripts in buster] perhaps related? |
Is there a way to temporarily downgrade the kernel again so Gitea can be run again? It seems the old kernel was removed from the repository |
We never delete firmware builds - you can install the 4.19.66 kernel using |
This reverts commit c0ccb4d ("binfmt_elf: move brk out of mmap when doing direct loader exec") See: #3271 Signed-off-by: Phil Elwell <[email protected]>
I'm experiencing the same issue on 4.19.75-v7l+ with a statically compiled comskip binary. Same binary works on 4.19.71-v7l+ I was able to get a backtrace by forcing core dump (
|
Latest rpi-update kernel may have a fix for this. |
FYI the Gitea and Kiwix segmentation faults (kiwix/kiwix-tools#341) are NOT solved for me when I do CLARIF: the regression persists on (both) RPi 3 and RPi 4. |
You need to run |
Why is that specifically? |
Because the fix was made a few hours ago and is not contained in package from 9/25? |
Ok then I was mistaken in assuming #3279 (comment) was the fix. Apologies. Certainly applying kernel (1.20190925+1-1) over (1.20190925-2) is insufficient. |
I can confirm that running FYI kernel goes from...
To...
|
Question: how many days is likely, until regular users get their kernel fixed here? (via |
I just run apt-get update && apt-get dist-upgrade, then rpi-update I am now on 4.19.79-v7+ #1273 SMP Fri Oct 11 18:13:16 BST 2019 armv7l GNU/Linux. Now gitea is starting successfully with https://dl.gitea.io/gitea/1.9.4/gitea-1.9.4-linux-arm-6 |
Welp, it's resolved. |
Thank you all so much for this. I've been wrestling with the issue on and off for almost a month before finding this. |
@XECDesign When are we likely to next bump the kernel package? |
@pelwell @popcornmix I'm waiting for something new to show up on https://github.com/raspberrypi/firmware/commits/stable/ |
Looks like something new has since shown up? Anything else blocking a release? It's now been a few weeks. raspberrypi/firmware@878d27e I'm hesitant to reach beyond the stable apt channel as the last In my case I am seeing this same segfault/stack with a build of Drone CI on an RPi4/4GB running 4.19.75-v7l+, specifically the build provided within this image: https://hub.docker.com/layers/drone/drone/latest/images/sha256-722f8062c3b683005ca1a1f96216b65bf0df1cc4a3a3aa0f2911d71307ce98ce . |
I gave up waiting for a kernel release to finally be cut and tried an Now off to see if I can successfully |
Please, can you release the new firmware, so that the fix will be available without The month has passed since the bug has been fixed, but new kernel has not yet been released:( |
It will be released early in the new year. The guy who does it is on holiday. If you need it urgently, AFAIK there are not any major issues with the code in rpi-update so that should be safe. |
@JamesH65 We're now half-way through January, any chance we'll get an update soon? |
Should be sometime next week. Been slightly delayed for various reasons (Xmas, holidays, illness etc). |
@JamesH65 Good to know, thanks 👍 |
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
When I launch gitea I got "segmentation fault"
To reproduce
gitea web
Expected behaviour
Gitea should executed and deploy his webserver.
Actual behaviour
I get segmentation fault
System
Copy and paste the results of the raspinfo command in to this section. Alternatively, copy and paste a pastebin link, or add answers to the following questions:
cat /etc/rpi-issue
)?vcgencmd version
)?uname -a
)?Linux raspberrypi 4.19.75-v7l+ #1270 SMP Tue Sep 24 18:51:41 BST 2019 armv7l GNU/Linux
Logs
The only log I have is from his stack trace using dbg
Additional context
This answer from the ticket I opened at gitea github say if you use an older version of raspi kernel it works without problem:
go-gitea/gitea#8373 (comment)
EDIT : https://github.molgen.mpg.de/git-mirror/glibc/blob/20003c49884422da7ffbc459cdeee768a6fee07b/csu/libc-tls.c#L105
This is the function where the segfault happens.
The text was updated successfully, but these errors were encountered: