linux-kernel - Re: proc_stack for x86

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87myo4pp66.fsf@basil.nowhere.org>
Date:	Tue, 08 Apr 2008 13:21:53 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Nuno Pais Fernandes <npf@...otux.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: proc_stack for x86_64 (spinning process)

Nuno Pais Fernandes <npf@...otux.com> writes:

> Hi,
>
> I have a spinning process that it's locking my server (eating 100% CPU). I 
> can't kill it even with kill -9
>
> I'm trying to use proc_stack to check what's the problem, compiling the kernel 
> with
>
> http://linuxhacker.ru/~nikita/patches/2.6.12-rc6/2005.06.11/vm_07-proc-stack.patch
>
> But this patch is only for x86 as my arch is x86_64. Does anyone know if 
> there's a patch for x86_64?

The standard way to handle that is to just do 

echo 1 > /proc/sys/kernel/sysrq 
echo t > /proc/sysrq-trigger

and then look for the process backtrace in the kernel log.

Another alternative is to use crash to take a live dump and then analyse that
using crash.

-Andi
--
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/