From: Ingo Molnar <mingo@elte.hu>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
NetDev <netdev@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Dave Jones <davej@redhat.com>
Subject: Re: Oops/Warning report of the week of July 4th 2008
Date: Sat, 5 Jul 2008 08:39:18 +0200 [thread overview]
Message-ID: <20080705063917.GA11599@elte.hu> (raw)
In-Reply-To: <486EA0D6.2040504@linux.intel.com>
* Arjan van de Ven <arjan@linux.intel.com> wrote:
> Rank 8: tick_broadcast_oneshot_control (softlockup)
> Reported 91 times (634 total reports)
>
> Some interaction between tickless and systems with an AMD CPU
> and an ATI chipset (eg only seen on systems that both have an
> AMD cpu and an ATI chipset) Current suspicion is some kind of
> time-warp problem that causes the softlockup code to trigger
> incorrectly
>
> This softlockup was last seen in version 2.6.25.9,
> and first seen in 2.6.24-rc4. More info:
>
> http://www.kerneloops.org/searchweek.php?search=tick_broadcast_oneshot_control
ok, so it's a false positive due to bad timer readout, not a real
lockup. That probably also explains how it was able to show up in such
numbers - the system kept functioning just fine so every system that
produced this warning was able to report it to kerneloops.org.
i'll think about extending the softlockup code with time warp detection
and reporting - that would be a useful facility in itself as right now
there's nothing that warns about time warps in monotonic system time.
Ingo
prev parent reply other threads:[~2008-07-05 6:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-04 22:14 Oops/Warning report of the week of July 4th 2008 Arjan van de Ven
2008-07-04 22:23 ` Dave Jones
2008-07-07 15:55 ` John W. Linville
2008-07-05 6:39 ` Ingo Molnar [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=20080705063917.GA11599@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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 NNTP newsgroup(s).