Re: [systemd-devel] Waiting udev jobs

2021-03-27 Thread Alan Perry
On 3/27/21 5:38 AM, Lennart Poettering wrote: On Fr, 26.03.21 23:24, Alan Perry (al...@snowmoose.com) wrote: I occasionally see a problem where systemd-analyze reports that boot did not complete and it is suggested that I use systemctl list-jobs to find out more. That shows a .device service

Re: [systemd-devel] Waiting udev jobs

2021-03-27 Thread Alan Perry
> On Mar 27, 2021, at 05:46, Lennart Poettering wrote: > > On Fr, 26.03.21 23:24, Alan Perry (al...@snowmoose.com) wrote: > >> I occasionally see a problem where systemd-analyze reports that boot >> did not complete and it is suggested that I use systemctl list-jobs &

[systemd-devel] Waiting udev jobs

2021-03-26 Thread Alan Perry
I occasionally see a problem where systemd-analyze reports that boot did not complete and it is suggested that I use systemctl list-jobs to find out more. That shows a .device service job and some sub-jobs (associated with udev rules) all waiting. They will wait for literal days in this state. W

Re: [systemd-devel] udev blkid check on mmcblk0boot0 and boot1

2021-02-02 Thread Alan Perry
On 2/2/21 2:13 PM, Jeremy Linton wrote: Hi, On 2/2/21 1:46 PM, Alan Perry wrote: On 2/2/21 1:55 AM, Lennart Poettering wrote: On Mo, 01.02.21 16:36, Alan Perry (al...@snowmoose.com) wrote: Hi, Per the udev rules, the blkid builtin is run on mmcblk*boot* devices to look for partition and

Re: [systemd-devel] udev blkid check on mmcblk0boot0 and boot1

2021-02-02 Thread Alan Perry
On 2/2/21 1:55 AM, Lennart Poettering wrote: On Mo, 01.02.21 16:36, Alan Perry (al...@snowmoose.com) wrote: Hi, Per the udev rules, the blkid builtin is run on mmcblk*boot* devices to look for partition and filesystem. Those devices contain hardware-specific boot information and are unlikely

[systemd-devel] udev blkid check on mmcblk0boot0 and boot1

2021-02-01 Thread Alan Perry
Hi, Per the udev rules, the blkid builtin is run on mmcblk*boot* devices to look for partition and filesystem. Those devices contain hardware-specific boot information and are unlikely to have anything on them that blkid would identify. Why isn't there a rule to exclude them from blkid? Is

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

2020-09-30 Thread Alan Perry
On 9/23/20 9:29 AM, Lennart Poettering wrote: On Di, 22.09.20 10:06, Alan Perry (al...@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?

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

2020-09-22 Thread Alan Perry
On 9/22/20 7:44 AM, Lennart Poettering wrote: On Mo, 21.09.20 19:03, Alan Perry (al...@snowmoose.com) wrote: Hi, I am trying to understand behavior that I am seeing with udev and eMMC partition devices and was hoping that someone here could help. The system that I am running has an eMMC

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

2020-09-21 Thread Alan Perry
n the same system? Thanks, alan perry Microsoft ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel