On Mi, 30.09.20 13:57, Alan Perry (al...@snowmoose.com) wrote:
>
>
> 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
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?
When this happens
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?
>
> When this happens, the last thing seen in the log for
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 de
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 device with something like 7-8
> partition
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 device with something like 7-8
partitions. The kernel does add block events for the device and each of
it parti
