| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <8abd1bfd0802221508i373d37e7hd6ad7702bde25330@mail.gmail.com> Date: Fri, 22 Feb 2008 18:08:34 -0500 From: "Stephen Oberholtzer" <oliverklozoff@...il.com> To: linux-kernel@...r.kernel.org Cc: oliverklozoff@...il.com Subject: How to diagnose a process stuck in D state? First off: I'm not subscribed to the list (I don't think I could handle the volume), so please make sure you CC me if you reply. I run an application on one of my machines; it often hangs, with the process stuck D state. When this happens, the process sticks around until I reboot the machine. I have tried the following to start diagnosing the problem: * Running 'ps -axl' shows "-" in the wchan column. * The contents of /proc/pid/wchan say "_stext". * 'strace -p pid' says "Process pid attached - interrupt to quit" and stops responding. Sending SIGINT and SIGTERM have no effect on the strace process, although kill -11 (SIGSEGV, my personal favorite) does work. This is very confusing. I would greatly appreciate it if someone could tell me how a process can enter D state without being in a syscall, and what I can do to start tracking down the cause. (By the way: This is on amd64, 2.6.23. I'm updating to 2.6.24.2 right now, on the off chance that whatever was causing the problem has been fixed.) -- -- Stevie-O Real programmers use COPY CON PROGRAM.EXE -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists