-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
udev: downgrade message when we cannot apply ACLs on a device due to EOENT #875
Comments
Any idea what device this is on USB bus 3, device 4? Most likely this is simply a race, where a usb device pops up and is removed quickly (for example due to a modem mode changing thing), while we try to fix the device perms... Most likely we should really just downgrade the message to LOG_DEBUG if we see ENOENT, and this is all purely cosmetic. |
It doesn't seem to show up when using lsusb.
If I run lsusb, there's no device that matches, but there's one device whose no. keeps incrementing after resuming. |
Can you paste the full "lusb -v" output for that one device, so that we can see what kind of device that is? |
Yep, it's the wwan module |
ah, ok, then it's modeswitching fallout: the modem pops up as one device and has then be switched to a different mode which causes it to disappear and reapper as a different devices. Which means the issue is cosmetic and we should just downgrade the message. |
Hello
I'm getting errors like:
systemd-udevd[XXX]: Failed to apply ACL on /dev/bus/usb/003/004: No such file or directory
when suspending/resuming.
It only seems to happen on 224, no problems on 223, 222
Arch, Kernel 4.1.4
The text was updated successfully, but these errors were encountered: