public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
* Re: Machine reboot upon probing
  2008-04-21 15:43 Machine reboot upon probing Peter Teoh
@ 2008-04-21 15:43 ` Frank Ch. Eigler
  2008-04-21 16:27   ` Peter Teoh
  0 siblings, 1 reply; 3+ messages in thread
From: Frank Ch. Eigler @ 2008-04-21 15:43 UTC (permalink / raw)
  To: Peter Teoh; +Cc: systemtap

"Peter Teoh" <htmldeveloper@gmail.com> writes:

> Running the following scripts:
> probe kernel.function("*@kernel/softirq.c").call {
> [...]
> probe kernel.function("*@kernel/softirq.c").return {
> [...]
> will reboot the kernel (2.6.25-rc9, FC7) in just a short time. [...]

This could well be an area of the kernel that needs more probing
blacklist entries.


- FChE

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Machine reboot upon probing
@ 2008-04-21 15:43 Peter Teoh
  2008-04-21 15:43 ` Frank Ch. Eigler
  0 siblings, 1 reply; 3+ messages in thread
From: Peter Teoh @ 2008-04-21 15:43 UTC (permalink / raw)
  To: systemtap

Running the following scripts:

probe kernel.function("*@kernel/softirq.c").call {
        printf ("%s -> %s\n", thread_indent(1), probefunc())
        print_backtrace();
        printf("\n");
}
probe kernel.function("*@kernel/softirq.c").return {
        printf ("%s <- %s\n", thread_indent(-1), probefunc())
        printf("\n");
}

will reboot the kernel (2.6.25-rc9, FC7) in just a short time.   User
applications are just firefox switching randomly among different
screens.

The last few lines before the reboot are:

    16 swapper(0): <- irq_exit

     0 gnome-terminal(3974): -> irq_enter
 0xc04289aa : irq_enter+0x1/0x4e
 0xc0405394 : apic_timer_interrupt+0x28/0x30

     5 gnome-terminal(3974): <- irq_enter

     0 gnome-terminal(3974): -> irq_exit
 0xc0428872 : irq_exit+0x1/0x6b
 0xc0405394 : apic_timer_interrupt+0x28/0x30

     5 gnome-terminal(3974):  -> _local_bh_enable
 0xc0428592 : _local_bh_enable+0x1/0x6e
 0xc04068c4 : do_softirq+0x55/0x88

    10 gnome-terminal(3974):  <- _local_bh_enable

    14 gnome-terminal(3974): <- irq_exit

     0 swapper(0): -> irq_enter
 0xc04289aa : irq_enter+0x1/0x4e
 0xc0405394 : apic_timer_interrupt+0x28/0x30
 0xc04031c5 : mwait_idle+0xd/0xf
 0xc0403588 : cpu_idle+0x8f/0xab
 0xc0627fc9 : rest_init+0x49/0x4b
 0xc07638ba : start_kernel+0x2e5/0x2ed

     9 swapper(0): <- irq_enter

     0 swapper(0): -> irq_exit
 0xc0428872 : irq_exit+0x1/0x6b
 0xc0405394 : apic_timer_interrupt+0x28/0x30
 0xc04031c5 : mwait_idle+0xd/0xf
 0xc0403588 : cpu_idle+0x8f

Any hints/clue why it crashes?


-- 
Regards,
Peter Teoh

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Machine reboot upon probing
  2008-04-21 15:43 ` Frank Ch. Eigler
@ 2008-04-21 16:27   ` Peter Teoh
  0 siblings, 0 replies; 3+ messages in thread
From: Peter Teoh @ 2008-04-21 16:27 UTC (permalink / raw)
  To: Frank Ch. Eigler; +Cc: systemtap

I attempted the script after reboot, and after 800MB of output, there
is still no crashes.     Now I am at a loss at the possible reason for
these????

On Mon, Apr 21, 2008 at 11:30 PM, Frank Ch. Eigler <fche@redhat.com> wrote:
> "Peter Teoh" <htmldeveloper@gmail.com> writes:
>
>  > Running the following scripts:
>  > probe kernel.function("*@kernel/softirq.c").call {
>  > [...]
>
> > probe kernel.function("*@kernel/softirq.c").return {
>  > [...]
>  > will reboot the kernel (2.6.25-rc9, FC7) in just a short time. [...]
>
>  This could well be an area of the kernel that needs more probing
>  blacklist entries.
>
>
>  - FChE
>



-- 
Regards,
Peter Teoh

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2008-04-21 16:03 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-04-21 15:43 Machine reboot upon probing Peter Teoh
2008-04-21 15:43 ` Frank Ch. Eigler
2008-04-21 16:27   ` Peter Teoh

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).