Timeline for How to stop a non-killable process on a Ubuntu VM running on windows 10?
Current License: CC BY-SA 4.0
29 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Jan 27, 2023 at 11:00 | history | bounty ended | CommunityBot | ||
| S Jan 27, 2023 at 11:00 | history | notice removed | CommunityBot | ||
| Jan 25, 2023 at 17:16 | answer | added | harrymc | timeline score: 0 | |
| Jan 22, 2023 at 14:16 | comment | added | user10489 | Unkillable processes in I/O wait are usually caused by either stuck hardware or a buggy device driver. If unplugging the device (virtually or physically) doesn't reset the connection and release the process, I'd go with buggy device driver. | |
| Jan 20, 2023 at 12:02 | comment | added | Alex | @harrymc Ok thanks, I will check it out next time this happens | |
| Jan 20, 2023 at 11:52 | comment | added | harrymc |
The D status means that the process is in Uninterruptible sleep, and this name does mean what it says. I think that the link in my previous comment is sort of your last chance.
|
|
| Jan 20, 2023 at 11:46 | comment | added | Alex | @harrymc Question updated with more details. | |
| Jan 20, 2023 at 11:46 | history | edited | Alex | CC BY-SA 4.0 |
added 248 characters in body
|
| Jan 20, 2023 at 9:41 | comment | added | harrymc |
Please include the output of ps -Al. Try kill -hup and kill -15. Try also this answer.
|
|
| Jan 20, 2023 at 8:08 | comment | added | Alex | @pbies Disconnecting the device also does not help. Process still not killable. | |
| Jan 20, 2023 at 8:07 | history | edited | Alex | CC BY-SA 4.0 |
added 10 characters in body
|
| Jan 19, 2023 at 22:15 | comment | added | pbies | Seems like it is hanged up by a interrupt related to device. Not much possible to do in that case but removing connection to the device (unplug). | |
| Jan 19, 2023 at 12:00 | history | tweeted | twitter.com/super_user/status/1616042796896423937 | ||
| S Jan 19, 2023 at 9:46 | history | bounty started | Alex | ||
| S Jan 19, 2023 at 9:46 | history | notice added | Alex | Draw attention | |
| Jan 18, 2023 at 13:16 | history | edited | Alex | CC BY-SA 4.0 |
added 190 characters in body
|
| Jan 18, 2023 at 10:28 | history | edited | Alex | CC BY-SA 4.0 |
added 412 characters in body
|
| Jan 17, 2023 at 13:05 | comment | added | Alex | @Bib Yes I would prefer to be able to kill that process without shutting down the VM. | |
| Jan 17, 2023 at 12:24 | comment | added | Bodo | @Alex stopping the VM is like pulling the plug of a real PC. (Depending on how exactly you do this.) | |
| Jan 17, 2023 at 11:09 | comment | added | Bob Goddard | We are talking about not being able to kill it from within the vm, not killing it by bringing the vm down. | |
| Jan 17, 2023 at 10:38 | comment | added | Alex | Of course it can. I just stop the VM which is just software, and it is being killed. I do not need to reboot the host machine. But my question is: Can I kill this possible I/O wait without restarting the VM all the time? | |
| Jan 17, 2023 at 10:30 | comment | added | Daniel B |
Unfortunately, your ps output does not indicate the process state (Running, Waiting, I/O Wait, …). To clarify what Bib means: If a process is waiting for an I/O system call, it cannot be killed.
|
|
| Jan 17, 2023 at 10:30 | comment | added | Saaru Lindestøkke | @Alex, thanks for providing details. Could you also please include what you've looked into so far? Any research you've done? Please include anything you've tried so far (and which didn't work) as then others won't spend time suggesting it as a solution. | |
| Jan 17, 2023 at 10:22 | comment | added | Alex | The application is used to write firmware to a microcontroller using CAN. The first two times or so when using the application just works fine, then when running a third time it hangs. Also see updated question. | |
| Jan 17, 2023 at 10:20 | history | edited | Alex | CC BY-SA 4.0 |
added 259 characters in body
|
| Jan 17, 2023 at 10:19 | comment | added | Bob Goddard |
How about output from ps, how about which devices are connected and what are expected to be connected. How about what the process is actually trying to achieve. How about info on the host as to whether it is using network shares.
|
|
| Jan 17, 2023 at 10:15 | comment | added | Alex | What additional information do you need? | |
| Jan 17, 2023 at 10:12 | comment | added | Bob Goddard | Any process waiting in device will usually be unkillable. This is a poor question though as you are giving us no info on which process is failing. Do not drip feed info. | |
| Jan 17, 2023 at 9:37 | history | asked | Alex | CC BY-SA 4.0 |