public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Juergen Quade <quade@hs-niederrhein.de>
To: Prasanna S Panchamukhi <prasanna@in.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: system-freeze: kprobe and do_gettimeofday
Date: Fri, 29 Apr 2005 19:27:59 +0200	[thread overview]
Message-ID: <20050429172759.GA27647@hsnr.de> (raw)
In-Reply-To: <20050429111849.GA5185@in.ibm.com>

> > ...
> Thanks for providing the information, we are not able to reproduce this
> problem here. Can you pls write a similar fault handler for kprobes as shown
> below and get us the log messages.
> 
> int fault_probe(struct kprobe *p, struct pt_regs *regs, int trapnr) {
>         printk("fault_handler:p->addr=0x%p, eflags=0x%lx\n", p->addr, regs->eflags);
>         return 0;

I tried it a few time, system freezes but the fault handler
has not been called. First time the system rebooted completly,
second time I got no output at all.

I added the proposed line into the pre-handler. Here is the
output:

	kprobe registered address c0107bd0
	pre_handler:p->addr=0xc0107bd0, eflags=0x282
	root@esz-mobil:/tmp/kprobes# double fault, gdt
	at c049bd00 ...

The first line is the output of "init_module". The second
line is the output of the pre_handler. As you can see,
before the "double fault" message I get one prompt. Could
there be a problem with the timer interrupt?

         Juergen.

      reply	other threads:[~2005-04-29 17:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-23 10:12 system-freeze: kprobe and do_gettimeofday Juergen Quade
2005-04-25 15:56 ` Prasanna S Panchamukhi
2005-04-25 16:08   ` Juergen Quade
2005-04-26 14:52     ` Prasanna S Panchamukhi
2005-04-26 19:34       ` Juergen Quade
2005-04-29 11:18         ` Prasanna S Panchamukhi
2005-04-29 17:27           ` Juergen Quade [this message]

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=20050429172759.GA27647@hsnr.de \
    --to=quade@hs-niederrhein.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prasanna@in.ibm.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