All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antoine Martin <antoine@nagafix.co.uk>
To: Andi Kleen <ak@muc.de>, linux-kernel@vger.kernel.org
Subject: reporting lost ticks
Date: Sun, 11 Feb 2007 03:28:52 +0000	[thread overview]
Message-ID: <45CE8D74.6030700@nagafix.co.uk> (raw)
In-Reply-To: <20070205130807.GA46862@muc.de>

Andi Kleen wrote:
> [Snip]
> You run with report_lost_ticks and report the results to linux-kernel

Doing as I am told, here we go:
This is 100% reproducible, ie: just doing a big rsync between 2 disks 
and burning a DVD at the same time. Note: the system isn't very 
responsive when this happens, most notably: audio seems to jump every 
~1second.
Hardware is an ASUS K8N-DL with a pair of Opteron 270s, 4GB PC3200, SATA 
  disks, software raid.

time.c: Lost 6 timer tick(s)! rip __do_softirq+0x44/0xc0)
time.c: Lost 6 timer tick(s)! rip __do_softirq+0x44/0xc0)
time.c: Lost 6 timer tick(s)! rip __do_softirq+0x44/0xc0)
time.c: Lost 6 timer tick(s)! rip __do_softirq+0x44/0xc0)
time.c: Lost 6 timer tick(s)! rip __do_softirq+0x44/0xc0)
time.c: Lost 6 timer tick(s)! rip __do_softirq+0x44/0xc0)
time.c: Lost 6 timer tick(s)! rip __do_softirq+0x44/0xc0)
time.c: Lost 6 timer tick(s)! rip __do_softirq+0x44/0xc0)
time.c: Lost 6 timer tick(s)! rip __do_softirq+0x44/0xc0)
time.c: Lost 6 timer tick(s)! rip __do_softirq+0x44/0xc0)
time.c: Lost 6 timer tick(s)! rip __do_softirq+0x44/0xc0)
time.c: Lost 6 timer tick(s)! rip _spin_unlock_irq+0x10/0x40)

You can find a much longer version of the kernel output here:
http://194.145.196.85/ticks
http://194.145.196.85/ticks2
If you need anything else just let me know.

Antoine

           reply	other threads:[~2007-02-11  3:34 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20070205130807.GA46862@muc.de>]

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=45CE8D74.6030700@nagafix.co.uk \
    --to=antoine@nagafix.co.uk \
    --cc=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 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.