Hey, > So, the problem is the timing here exclusively, there is no failed QMI > protocol probing. This system you're running seems to be a bit slow, > and the events reported are taking a lot of time to complete before > the next one can be processed; we should definitely fix this in > ModemManager so that we can handle these type of systems as well. > > For a quick workaround in your case, can you try modifying > EXTRA_PROBING_TIME_MSECS in mm-plugin-manager.c and change it from > 1500 to something bigger like e.g. 3000 or 4000? > > There's one thing clear though; the longer timeout should not be > applied by default, as that would impose an extra wait time that is > not needed in most cases. I think we can make this more specific to > setups like yours, e.g. making the longer timeout happen only for > openwrt setups (when udev is not available) and also maybe applicable > only during MM daemon startup (e.g. if the port addition happened in > the first 10s of the MM daemon startup, allow a bigger extra probing > time). What do you think? >
I've opened a new issue for this: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/493 -- Aleksander https://aleksander.es
