public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "mhiramat at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug runtime/6487] kernel.function("internal_add_timer") freezes system.
Date: Wed, 07 May 2008 18:48:00 -0000	[thread overview]
Message-ID: <20080507154539.30424.qmail@sourceware.org> (raw)
In-Reply-To: <20080507143402.6487.mhiramat@redhat.com>


------- Additional Comments From mhiramat at redhat dot com  2008-05-07 15:45 -------
(In reply to comment #1)
> By the way, curiously, below command did not freeze system.
> 
> $ stap -e 'probe kernel.function("internal_add_timer") {}'
> 

Oops, when I tried to stop it, it caused a soft lockup.
---
stap_9017fb37783d59da64aa2cc1999ac78d_247: systemtap: 0.7/0.131, base: f8b03000,
memory: 496426+25746+376+13600 data+text+ctx+net, probes: 1
BUG: soft lockup - CPU#1 stuck for 61s! [staprun:7749]

Pid: 7749, comm: staprun Not tainted (2.6.25 #4)
EIP: 0060:[<c0127259>] EFLAGS: 00000246 CPU: 1
EIP is at lock_timer_base+0x34/0x3e
EAX: f72b1634 EBX: 00000000 ECX: f5e4f600 EDX: f469bf1c
ESI: 00000000 EDI: f72b1634 EBP: f469bf14 ESP: f469bf04
 DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
CR0: 8005003b CR2: bfd26e38 CR3: 338e4000 CR4: 000006d0
DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
DR6: ffff4ff0 DR7: 00000400
 [<c0127278>] try_to_del_timer_sync+0x15/0x4f
 [<f8b066eb>] ? _stp_kfree+0x8/0xa [stap_9017fb37783d59da64aa2cc1999ac78d_247]
 [<c01272bf>] del_timer_sync+0xd/0x18
 [<f8b05017>] _stp_kill_time+0x35/0x6c [stap_9017fb37783d59da64aa2cc1999ac78d_247]
 [<f8b07277>] _stp_transport_close+0x31/0x38
[stap_9017fb37783d59da64aa2cc1999ac78d_247]
 [<f8b07286>] cleanup_module+0x8/0xa [stap_9017fb37783d59da64aa2cc1999ac78d_247]
 [<c0141f35>] sys_delete_module+0x195/0x1d0
 [<c010487e>] sysenter_past_esp+0x5f/0xa5
 =======================
---

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=6487

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

  parent reply	other threads:[~2008-05-07 15:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-07 18:37 [Bug runtime/6487] New: " mhiramat at redhat dot com
2008-05-07 18:45 ` [Bug runtime/6487] " mhiramat at redhat dot com
2008-05-07 18:48 ` mhiramat at redhat dot com [this message]
2008-05-07 18:55 ` mhiramat at redhat dot com
2008-05-07 20:22 ` joshua dot i dot stone at intel dot com
2008-05-07 20:52 ` fche at redhat dot com
2008-05-07 21:28 ` fche at redhat dot com
2008-05-07 22:50 ` mhiramat at redhat dot com
2008-05-07 23:37 ` mhiramat at redhat dot com
2008-05-10 14:27 ` fche at redhat dot com
2008-05-12 13:11 ` fche at redhat dot com
2008-05-13  6:08 ` fche at redhat dot com
2008-05-16 18:57 ` mhiramat at redhat dot com
2008-09-17 19:21 ` fche at redhat dot com
2008-09-17 19:22 ` fche at redhat dot com

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=20080507154539.30424.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@sources.redhat.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).