It honestly was the thing that pushed me to Linux. Once I could no longer kill programs at-will I couldn’t handle it. xkill ftw.
Comment on Choosing violence
wesker@lemmy.sdf.org 2 months agoAll the damn time. I typically use Linux, so having a process I can’t even force kill is severely annoying.
laranis@lemmy.zip 2 months ago
nickwitha_k@lemmy.sdf.org 2 months ago
Yeah… It doesn’t happen often and when it does, it’s usually a driver and/or hw issue that is likely to leak memory and/or hold file descriptors but procs in
D
(uninterruptible_sleep) state do happen. It’s really obnoxious that murdering them withSIGKILL
does nothing.
henfredemars@infosec.pub 2 months ago
This has happened to me only once on Linux. I still tell stories about it.
It was a CD burning program stuck in uninterruptible sleep! Trapped in a system call into the kernel that can never be interrupted by a signal, it was truly unkillable.
Lost_My_Mind@lemmy.world 2 months ago
THIS is your big “You won’t believe what happened to me…” story???
sigh
When I was 14, I took the power cord for the original PS1 and shaved the rubber off the end until metal prongs were sticking out. Then I noticed if the outlet end was plugged in, and you touched the metal prongs on the other end, you couldn’t drop it. It would electricute you, but it would also stick to your skin for 5-10 seconds as it electricuted you.
So being a 14 year old male, I did the only logical thing. I put it on my penis.
It was quite shocking!
henfredemars@infosec.pub 2 months ago
I used to stick forks in the electrical outlets.
Now I post Linux memes.
Lost_My_Mind@lemmy.world 2 months ago
That tracks.
Honytawk@lemmy.zip 2 months ago
I can’t believe what happened next
lolrightythen@lemmy.world 2 months ago
Image
Lost_My_Mind@lemmy.world 2 months ago
I…can’t tell what is happening here. Is he having an orgasm? Is he supposed to be a priest, or a slave?
photonic_sorcerer@lemmy.dbzer0.com 2 months ago
That’s Frodo Baggins on the verge of death thou fool!
lolrightythen@lemmy.world 2 months ago
I don’t recall. Just having fun. Be well!
Ziglin@lemmy.world 2 months ago
I would assume that was a kernel issue.
henfredemars@infosec.pub 2 months ago
In this case it was a driver holding that thread captive and making an assumption about the hardware eventually responding to a request which never completes.
So yes indeed it was the kernel, and ideally the driver could be written better, but the reality is that’s probably easier said than done when the hardware can do weird things.