[SOLVED] Kill a hung task when kill -9 doesn't help
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I try this command: 'cat /proc/bus/usb/001/001' It shoudn't do any harm to my system... But, 'cat' process hangs forever, and can't be killed by 'killall -9 cat' command. How can i stop such processes?
I can't even enter hibernation state because of kernel's inability to stop all tasks such as this one.
Your request is inside a kernel call and the kernel has locked the calling stack as unkillable. The SIGKILL is held pending return from the call. Reboot. Sorry.
request is inside a kernel call and the kernel has locked the calling stack as unkillable
Maybe there is some way to force interruption of a kernel call, making it return an error to the process and unlock the process by writing a kernel module, or something... or such a module already exists?
If you look at the process in top, it will be in state "D", or uninterruptible sleep. It is off in a driver call and is actually uninterruptible. Reboot, sorry.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.