[systemd-devel] udev and probing of eMMC partition devices

Lennart Poettering lennart at poettering.net
Wed Sep 23 16:29:51 UTC 2020


On Di, 22.09.20 10:06, Alan Perry (alanp at snowmoose.com) wrote:

> > > device add events will get stuck at the probe step.
> > "Get stuck"? What does that mean? What is it actually doing? What does
> > a stack trace say? Anything in the logs?
>
> When this happens, the last thing seen in the log for those devices is the
> probe ("probe /dev/mmcblk0<part> raid offset=0").

This debug log message is generated by udev-builtin-blkid.c, right
after opening the block device, and right before issuing the probe,
i.e. reading the fs label/partition table signatures off disk. If
things hang there, and the blkid prober worker process freezes then
this really looks like a hw/driver problem, i.e. IO access from the
block device just hangs.

Lennart

--
Lennart Poettering, Berlin


More information about the systemd-devel mailing list