On Di, 22.09.20 10:06, Alan Perry ([email protected]) 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
Hi,
On Wed, Sep 23, 2020 at 04:58:57PM +0800, ZhouPeng wrote:
> I find that boot with the 'rescue' option, then exit 'rescue' mode, then
> I can login to the ttyPS0, as below
You're using a custom kernel, right? Please check the README in the systemd
source tree. Specifically the kernel config op
Hi,
I ran into an issue (v239 custom yocto based distro, though the code is the
same with latest releases) where a portable service ends up with a broken file
bind mount since the file is deleted and recreated on the host. This behaviour
is expected for a file based bind mount, the issue is that
I find that boot with the 'rescue' option, then exit 'rescue' mode, then I can
login to the ttyPS0, as below
bash-4.4# exit // *here exit rescue mode*
exit
Reloading system manager configuration
Starting default target
[ 1708.91] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1712.080
Thank you very much. ' udevadm info -a /dev/ttyPS0' output:
bash-4.4# udevadm info -a /dev/ttyPS0
Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A
On Wed, Sep 23, 2020, 09:21 ZhouPeng wrote:
>
> Thank you very much for you great suggestions.
>
> I chroot the rootfs and tried to the 3 methods in '/usr/lib/udev/rules.d'
> respectively:
>
> try 1) add a line of ACTION!="remove", KERNEL=="ttyPS0", TAG+="systemd"
> below the line of "ACTION=
