This started yesterday and is in the latest r3194-e5a0eb2
WRT1900AC V1
The below is a short sample of the errors. Everything seems to work. Just log spam?
Sat Jan 28 17:30:08 2017 daemon.err modprobe: failed to find a module named netdev-phy0
Sat Jan 28 17:30:08 2017 daemon.err modprobe: failed to find a module named netdev-phy1
Sat Jan 28 17:30:08 2017 daemon.err modprobe: failed to find a module named netdev-reg
Sat Jan 28 17:30:08 2017 daemon.err modprobe: failed to find a module named netdev-reg
Sat Jan 28 17:30:08 2017 daemon.err modprobe: failed to find a module named netdev-reg
Sat Jan 28 17:30:08 2017 daemon.err modprobe: failed to find a module named netdev-reg
Sat Jan 28 17:30:11 2017 daemon.err modprobe: failed to find a module named crypto-mv-cbc-des
Sat Jan 28 17:30:11 2017 daemon.err modprobe: failed to find a module named fs-ntfs-3g
Sat Jan 28 17:30:11 2017 daemon.err modprobe: failed to find a module named crypto-mv-cbc-des-all
Sat Jan 28 17:30:12 2017 daemon.err modprobe: failed to find a module named crypto-hmac(sha256)
Sat Jan 28 17:30:12 2017 daemon.err modprobe: failed to find a module named crypto-hmac(sha256)-all
Sat Jan 28 17:30:12 2017 user.notice firewall: Reloading firewall due to ifup of vpn0 (tun0)
Sat Jan 28 17:30:12 2017 daemon.err modprobe: failed to find a module named crypto-mv-cbc-des3-ede
Sat Jan 28 17:30:12 2017 kern.debug kernel: [ 25.330498] ieee80211 phy1: change: 0x100
Sat Jan 28 17:30:12 2017 daemon.err modprobe: failed to find a module named crypto-mv-cbc-des3-ede-all
Sat Jan 28 17:30:12 2017 kern.debug kernel: [ 25.359101] ieee80211 phy1: change: 0x62
As far as I can tell everything works as expected.
Since it is not really a bug and just log spam I really do not want to add it as a bug report..
Hopefully the right person sees this thread. If I get time later I will try to find the commit that caused it.
Edit: Removed stupid comment.
I am wondering if it has to do with the prep for 4.9?
try "iw aaaaaa" and logread.
modprobe process is called directly by kernel and only if "iw" was run under root. I replaced kmodloader (modprobe is linked to it) with bash script to print $PPID and it was kworker process
It looks like dirty kernel hack or misbehaving feature in openwrt environment
I switched over to the 17.01 branch, and since then it is gone. So agree it is likely one of the patches to prepare for 4.9. My guess is it will be fixed once we switch the kernel to 4.9.
Jow did not fix root of the problem. He changed ubox so that kmodloader insmods silently.
But modprobe is still called and "iw " causes abnormal delay which was not present in recent versions.
If change was introduced in original kernel tree we need kernel patch to remove this function