Skip to content
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

procfs3.ko used by -1 #195

Open
tclee060219sat opened this issue Apr 4, 2023 · 2 comments
Open

procfs3.ko used by -1 #195

tclee060219sat opened this issue Apr 4, 2023 · 2 comments
Assignees

Comments

@tclee060219sat
Copy link

tclee060219sat commented Apr 4, 2023

The sudo insmod procfs3.ko command hangs the Ubuntu 5.19.0-38-generic laptop. In another terminal, the lsmod|egrep procfs3 execution shows:

$ lsmod|egrep procfs3
procfs3                16384  -1
$ sudo rmmod procfs3

I discovered the solution to this problem is the power-cycle of this laptop. I am seeking a more efficient solution.

@linD026
Copy link
Collaborator

linD026 commented Apr 27, 2023

It seems like when the lsmod calls to the procfs_open and procfs_close, it doesn't increase but decreases the counter.
Currently, I don't have the v5.19 environment, so I cannot figure out why this happened.

@tclee060219sat
Copy link
Author

A module reference count of -1, visible both in /sys/module//refcnt and in lsmod’s output, means that the module is currently unloading.

If a module’s reference count stays at -1, that indicates a problem — dmesg should tell you more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants