Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at

Bug 1808698

Summary: udevadm is segfaulting in initrd on rk3399 SBC
Product: [Fedora] Fedora Reporter: billiboy
Component: systemdAssignee: systemd-maint
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 32CC: dominik, lnykryn, msekleta, pbrobinson, s, systemd-maint, themuso, watanabe.yu, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: aarch64   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-25 15:44:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 245418    
Description Flags
rdsosreport.txt with udev.log_priority=debug applied none

Description billiboy 2020-02-29 13:39:47 UTC
Created attachment 1666594 [details]

udevadm is segfaulting in initrd on rk3399 SBC

Version-Release number of selected component (if applicable):

current Fedora aach64 image

How reproducible:

Always with Fedora-Minimal-32-20200227.n.0.aarch64.raw.xz

Steps to Reproduce:

Boot rk3399 SBC with Fedora aarch64 image

Actual results:
boot up does not succeed

Expected results:
proper system boot up

Additional info:

Comment 1 Yu Watanabe 2020-03-02 16:56:42 UTC
Could you boot the system with udev.log_priority=debug kernel command line option?

Comment 2 Zbigniew Jędrzejewski-Szmek 2020-03-02 20:54:38 UTC
I have no idea what rk3399 is exactly, but this looks more likely to be some compiler mismatch rather then a specific systemd problem. Everything seems to be segfaulting.

Comment 3 billiboy 2020-03-03 19:42:42 UTC
Created attachment 1667290 [details]
rdsosreport.txt with udev.log_priority=debug applied

RK3399 is a System on Chip (SoC) [1] equipped on e.g. several Single Bord Computer (SBC).


Comment 4 Zbigniew Jędrzejewski-Szmek 2020-03-03 20:16:53 UTC
udevd starts, parses config, starts one worker, and immediately segfaults:
[    8.742891] localhost system\00d-udevd[510]: /etc/udev/rules.d/65-md-incremental-imsm.rules:23 PROGRAM key takes '==' or '!=' operator, assuming '=='.
[    8.743097] localhost systemd-udevd[510]: Reading rules file: /usr/lib/udev/rules.d/66-kpartx.rules
[    8.743317] localhost systemocalhost systemd-udevd[510]: Successfully forked off 'n/a' as PID 576.
[    8.756743] localhost systemd-udevd[510]: clockevents: Worker [576] is forked for processing SEQNUM=1244.
[    8.756913] localhost systemd-udevd[575]: amba: Device (SEQNUM=1239, ACTION=add) processed
[    8.757069] localhost systemd-udevd[575]: amba: sd-device-monitor: Passed 133 byte to netlink monitor
[    8.757226] localhost systemd-udevd[510]: clocksource: Device (SEQNUM=1245, ACTION=add) is queued
[    8.757990] localhost audit[576]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 subj=kernel pid=576 comm="systemd-udevd" exe="/usr/lib/systemd/systemd-udevd" sig=11 res=1
[    8.758395] localhost systemd-udevd[510]: Successfully forked off 'n/a' as PID 578.
[    8.758700] localhost systemd-udevd[510]: clocksource: Worker [578] is forked for processing SEQNUM=1245.

I think then systemd restarted udevd and the whole process repeats.
This seems very predictable. Maybe you could try to run udev by hand:
stop systemd-udevd.service, and invoke 'valgrind  'gdb /usr/lib/systemd/systemd-udevd'
or 'gdb /usr/lib/systemd/systemd-udevd' manually,
and possibly trigger events with 'udevadm trigger'. We should get a backtrace then.

Comment 5 billiboy 2020-03-04 11:04:26 UTC
I doubt that I am able to fulfill your request. The initramfs probably does not include gdb. I do not spot any sdhci traces in the log (the entire system code resides on the micro-SD-card). I don't know how to get access to the persistent rootfs at this stage.

Comment 6 Peter Robinson 2020-12-02 09:20:03 UTC
I have Fedora running on a number of rk3399 devices with no issues, can you provide more details of the hardware. Also I suggest running Fedora 33 GA [1], the Feb f-32 nightly is a little out of date.


Comment 7 billiboy 2021-01-03 19:38:38 UTC
My NanoPC-T4 is running a fully featured Fedora desktop for a long time now, and with alc5651 audio jack and Typec USB support (Fedora lacks the required configuration therefor).
After [1] and renaming the bug summary, so my comment looks stupid, I lost any motivation to report my findings back. I had only followed the advice to look for open bugs before opening a new one. In the end systemd was not the culprit and this report can be closed.


Comment 8 Fedora Program Management 2021-04-29 16:13:14 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 9 Ben Cotton 2021-05-25 15:44:23 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.