About one time in 5, when I plug in a USB drive, mount, copy something off, de-mount, and unplug, I get a surge of activity, with all 8 cores reporting 100% in htop -- multiple instances of:
/sbin/udevd --daemon -- resolve-names=early
At first, I thought this was USB3, but I got it with a USB2 device, plugged in a USB2 socket.
Hardware is a new build, Intel i7 4770, 16GB; software Tahr64 Puppy 6.0.5 plus latest upgrades.
One of the side effects of this (maybe) is losing ALSA configuration. I haven't worked out for sure if it's definitely linked.
Meanwhile, copying back the last known good save directory is a good workaround, and this hardware plus Tahr64 Puppy is faster than a scared impala.
Any Ideas? I tried editing /lib/udev/rules.d/69-libmtp.rules, as suggested at
https://unix.stackexchange.com/question ... ing-my-cpu
but the effect came back.
Remove unmounted USB --> 100% Busy CPU, in Tahr64 Puppy
Remove unmounted USB --> 100% Busy CPU, in Tahr64 Puppy
Xenial Puppy 64, Gigabyte motherboard, Intel i7 4770.
That's a good question -- I don't think it happens unless I unplug it.
As usual with these intermittent problems, I'm going through a spell of it not happening tonight, even if I try to get it.
I'm starting to think ALSA getting deconfigured might be a different problem that's just showing up at the same time.
(After not seeing a CPU surge, I restarted and got the no-sound symptoms.)
As usual with these intermittent problems, I'm going through a spell of it not happening tonight, even if I try to get it.
I'm starting to think ALSA getting deconfigured might be a different problem that's just showing up at the same time.
(After not seeing a CPU surge, I restarted and got the no-sound symptoms.)
Xenial Puppy 64, Gigabyte motherboard, Intel i7 4770.
Got a definite and severe "8 cores mostly 100% busy" example today, after pulling out a de-mounted USB2 MP3 player.
Clicked on the "mount" desktop icon, and it went away!
If this always works, I'd call it a good "pragmatic fix". The effect doesn't show up that often, with the adjustment to the config file, but unless you can make it go away, you have to reboot.
I'm going to try running the "mount" GUI program all the time, and see if it's prevention, as well as cure.
Clicked on the "mount" desktop icon, and it went away!
If this always works, I'd call it a good "pragmatic fix". The effect doesn't show up that often, with the adjustment to the config file, but unless you can make it go away, you have to reboot.
I'm going to try running the "mount" GUI program all the time, and see if it's prevention, as well as cure.
Xenial Puppy 64, Gigabyte motherboard, Intel i7 4770.