Skip to content

Instantly share code, notes, and snippets.

View akarasulu's full-sized avatar

Alex Karasulu akarasulu

View GitHub Profile
High CPU from kworker/0:x-kacpi_notify
Ubuntu 20.04 LTS
Update: this problem is fixed after I did "apt dist-upgrade" on 9/21/2020
Update again: Acutally not fixed. It happened again after unplug/plug the usb-c hub.
I recently got a USB-C Hub (Targus ACA958USZ). When it's plugged in, the laptop gives high cpu from process
I've found a few USB-C hubs from various manufactures with the same problem. I think they are of the same chipset.
List of common exit codes for GNU/Linux
Exit Code Description
0 Success
1 Operation not permitted
2 No such file or directory
3 No such process
4 Interrupted system call
5 Input/output error
6 No such device or address
7 Argument list too long
@akarasulu
akarasulu / DebOps_ifupdown.md
Last active November 6, 2021 20:44
DebOps ifupdown Role

Experiences

You might be surprised to see ifupdown creating a staging area for interfaces in /etc/network/interfaces.config.d. The interface definitions there following the Debian interfaces file format are then carried into the sourced /etc/network/interfaces.d/ directory. It even creates a dpkg diversion on the /etc/network/interfaces file to prevent changes on updates.

I venture to guess this approach is necessary to override existing configurations providing the connectivity. It's a delicate matter changing interfaces while connected to then reset networking without staging configurations.

Anyway this can get confusing for new users. Understanding how it works helps. Here's an issue post that explains the process a bit.

Mind the Playbooks and Roles

INFO global: Vagrant version: 2.2.18
INFO global: Ruby version: 2.7.4
INFO global: RubyGems version: 3.1.6
INFO global: VAGRANT_INSTALLER_EMBEDDED_DIR="/opt/vagrant/embedded"
INFO global: VAGRANT_INSTALLER_ENV="1"
INFO global: VAGRANT_EXECUTABLE="/opt/vagrant/embedded/gems/2.2.18/gems/vagrant-2.2.18/bin/vagrant"
INFO global: VAGRANT_INSTALLER_VERSION="2"
INFO global: VAGRANT_LOG="debug"
WARN global: resolv replacement has not been enabled!
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.18/gems/vagrant-2.2.18/plugins/synced_folders/nfs/plugin.rb
INFO global: Vagrant version: 2.2.18
INFO global: Ruby version: 2.7.4
INFO global: RubyGems version: 3.1.6
INFO global: VAGRANT_INSTALLER_ENV="1"
INFO global: VAGRANT_EXECUTABLE="/opt/vagrant/embedded/gems/2.2.18/gems/vagrant-2.2.18/bin/vagrant"
INFO global: VAGRANT_INSTALLER_EMBEDDED_DIR="/opt/vagrant/embedded"
INFO global: VAGRANT_INSTALLER_VERSION="2"
INFO global: VAGRANT_LOG="debug"
WARN global: resolv replacement has not been enabled!
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.18/gems/vagrant-2.2.18/plugins/synced_folders/nfs/plugin.rb
@akarasulu
akarasulu / gist:57a1d214ef3b1e78047dc45f9c6cacfa
Created April 26, 2020 02:09
Setting config.ssh.verify_installed to false has no effect
DEBUG host: Searching for cap: nfs_installed
DEBUG host: Checking in: linux
DEBUG host: Found cap: nfs_installed in linux
INFO host: Execute capability: nfs_installed [#<Vagrant::Environment: /home/aok/Vms/local/ansible/libvirt/folders/ganesha-wsl>] (linux)
INFO subprocess: Starting process: ["/bin/ps", "-o", "comm=", "1"]
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: init
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
### Keybase proof
I hereby claim:
* I am akarasulu on github.
* I am akarasulu (https://keybase.io/akarasulu) on keybase.
* I have a public key ASAovua09pay8GjlETvUhyIuxRZmGYacFFq80R6aI_gdvgo
To claim this, I am signing this object: