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
FS#4118 - logread crashes sometimes #9100
Comments
bittorf: the same with r18106 (after GCC11 fix). relevant config settings are: and no memory pressure: |
This still happens with r20187
Output in ssh-session1:
and dmesg shows e.g.:
|
This is reproducible on x86_64 OpenWRT, with a snapshot bringup the system, e.g. "OpenWrt SNAPSHOT, r20337-a66f843971"
Session1, "Segfault" will happen here:
Session2, it works reliable while sending strings with changing length to log-system:
leads to:
|
same here unfortunately :( |
still the same issue with r23293 on ath79
|
bittorf:
logread is dying several times a day here.
This is with r17950 and at least ath79 and mpc85xx and ramips.
Tue Nov 2 17:12:05 2021 kern.info kernel: [ 3745.330244] do_page_fault(): sending SIGSEGV to logread for invalid write access to 00000000 Tue Nov 2 17:12:05 2021 kern.info kernel: [ 3745.338789] epc = 77de87ac in libc.so[77d60000+a5000] Tue Nov 2 17:12:05 2021 kern.info kernel: [ 3745.343833] ra = 004017b3 in logread[400000+3000]
for checking if the log-service is healthy, we do regularly:
ubus call network.device status ubus call log read logread >/dev/null
The last call has (when failing) always RC = 139 with above message in log.
The text was updated successfully, but these errors were encountered: