From: Andi Kleen <andi@firstfloor.org>
To: Michel Lespinasse <walken@zoy.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 24 lost ticks with 2.6.20.10 kernel
Date: 02 May 2007 14:54:29 +0200 [thread overview]
Message-ID: <p73irbbxu62.fsf@bingen.suse.de> (raw)
In-Reply-To: <20070501130715.GB29131@zoy.org>
Michel Lespinasse <walken@zoy.org> writes:
>
> running with report_lost_ticks, I see the following:
>
> May 1 12:58:57 server kernel: time.c: Lost 24 timer tick(s)! rip _spin_unlock_irqrestore+0x8/0x9)
> May 1 12:58:59 server kernel: time.c: Lost 24 timer tick(s)! rip _spin_unlock_irqrestore+0x8/0x9)
> May 1 12:59:01 server kernel: time.c: Lost 25 timer tick(s)! rip _spin_unlock_irqrestore+0x8/0x9)
> May 1 12:59:03 server kernel: time.c: Lost 24 timer tick(s)! rip _spin_unlock_irqrestore+0x8/0x9)
This means some code disabled interrupts using a spinlock for far too long.
Can you add a dump_stack() in arch/x86_64/kernel/time.c:handle_lost_ticks()? That should
tell the culprit
-Andi
prev parent reply other threads:[~2007-05-02 11:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 13:07 24 lost ticks with 2.6.20.10 kernel Michel Lespinasse
2007-05-01 15:34 ` Chuck Ebbert
2007-05-01 21:49 ` Michel Lespinasse
2007-05-01 22:08 ` Kok, Auke
2007-05-01 22:41 ` Chuck Ebbert
2007-05-01 22:45 ` Kok, Auke
2007-05-02 0:06 ` Lee Revell
2007-05-02 8:41 ` Michel Lespinasse
2007-05-02 16:07 ` Kok, Auke
2007-05-02 18:14 ` Kok, Auke
2007-05-03 6:27 ` e1000 issue on DQ965GF board (was 24 lost ticks with 2.6.20.10 kernel) Michel Lespinasse
2007-05-03 15:36 ` Kok, Auke
2007-05-03 15:56 ` Allan, Bruce W
2007-05-04 18:25 ` Kok, Auke
2007-05-04 21:15 ` Michel Lespinasse
2007-05-02 12:54 ` Andi Kleen [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=p73irbbxu62.fsf@bingen.suse.de \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=walken@zoy.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.