Systemd on Fedora ARM bails with caught ABRT

asked 2018-10-09 10:00:05 -0600

goldilocks gravatar image

For years I've been using Fedora ARM with Raspberry Pis by simply copying the root fs to a partition, then using a stock Pi kernel (and copying in the corresponding /lib/modules/...). I realize there are official Fedora images for the Pi, but these use the mainstream kernel, I'd prefer to stick with the forked one.

Unfortunately, I tried this with the most recent F28 image (1.1), and during boot systemd fails like this:

Detected architecture arm
Caught <ABRT>, dumped core as pid 72.
Freezing execution.

This makes me think it has thrown an exception or something similar (i.e., SIGABRT). That, or it has something to do with the ABRT service. I did try removing the abrtd link in /etc/systemd/..., but I am pretty sure it ends up getting started anyway for other reasons.

I'd also have hoped that if this were the cause a more informative error message would have been displayed. Before I try digging into that (or make a more serious attempt to disable the service), can anyone confirm or deny that it is the ABRT system, and not a reference to a genuine SIGABRT (in which case I suspect I am really out of luck).

edit retag flag offensive close merge delete

Comments

What is the version of abrt installed?

You may use a different Fedora system (probably also another architecture allowed) and chroot into your Fedora/ARM image. In chroot environment, run coredumpctl and have a look on whether it helps.

You should also be able to boot without abrt, but I do not know why it does not.

Have you also tried the original kernel?

genodeftest gravatar imagegenodeftest ( 2018-10-09 15:10:26 -0600 )edit

I tried the original kernel (in fact the whole original image, unaltered, intended for the Pi) for aarch64 (the problem occurs for both that and armv7) and it does not suffer from this, but about 5-10 seconds into booting it spontaneously reboots. I'm not super motivated to solve the issue as using fedora is just a matter of preference and not an actual necessity. I'm also still not convinced that it is abrt, the "Caught <abrt>" thing says exception-esque to me. I may ask the systemd folks on a mail list or IRC.

goldilocks gravatar imagegoldilocks ( 2018-10-10 18:24:55 -0600 )edit

Caught <abrt>, dumped core as pid 72.

That looks more like it is catching an SIGABRT. Within system logs, the ABRT service is usually written as abrt or abrtd.

genodeftest gravatar imagegenodeftest ( 2018-10-11 04:45:44 -0600 )edit