From: Andi Kleen <ak@muc.de>
To: linux-kernel@vger.kernel.org
Subject: deadlock in group_send_sig_info
Date: Mon, 24 Nov 2003 08:59:19 +0100 [thread overview]
Message-ID: <20031124075919.GA29874@averell> (raw)
I had my ipsec daemon deadlock on me in 2.6.0test9/x86-64.
It became unkillable. Apparently it deadlocked while sending
a signal:
pluto T 0000010002417450 16 20769 20656 20841 (NOTLB)
ffffffff80499dc8 0000010034a3ed70 ffffffff80499e08 0000010034a3ed70
0000010002426400 ffffffff8013247d 0000000000000002 000001003fa72000
0000000000000001 ffffffff8025ff78
Call Trace:<IRQ> <ffffffff8013247d>{show_state+93} <ffffffff8025ff78>{k_spec+56}
<ffffffff80260ac5>{kbd_keycode+693} <ffffffff80260b10>{kbd_event+32}
<ffffffff802c1809>{input_event+905} <ffffffff802c3ccf>{atkbd_interrupt+719}
<ffffffff802c6f6b>{serio_interrupt+27} <ffffffff802c77cc>{i8042_interrupt+300}
<ffffffffa006d473>{:pppoe:pppoe_rcv_core+163} <ffffffff8013d64c>{update_wall_time+12}
<ffffffffa006d071>{:pppoe:__get_item+17} <ffffffff8012f5de>{recalc_task_prio+382}
<ffffffff801104ef>{reschedule_interrupt+99} <ffffffff8013d64c>{update_wall_time+12}
<ffffffff8013d9c1>{do_timer+49} <ffffffff80116113>{timer_interrupt+515}
<ffffffff8011281f>{handle_IRQ_event+47} <ffffffff80112a62>{do_IRQ+194}
<ffffffff80110385>{ret_from_intr+0} <EOI> <ffffffff80181797>{do_select+855}
<ffffffff8013f4d2>{group_send_sig_info+1074} <ffffffff8013f6a2>{kill_proc_info+66}
<ffffffff801418ac>{sys_kill+76} <ffffffff80124299>{sys32_kill+9}
<ffffffff801211fe>{ia32_do_syscall+30}
I unfortunately don't have the vmlinux for this kernel anymore
and cannot decode it further.
-Andi
reply other threads:[~2003-11-24 7:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031124075919.GA29874@averell \
--to=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox