From: "Paweł Sikora" <pluto@pld-linux.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, arekm@pld-linux.org, baggins@pld-linux.org
Subject: Re: [3.5.4] rcu_sched self-detected stall on CPU { 1} (t=54862991 jiffies)
Date: Tue, 25 Sep 2012 18:31:36 +0200 [thread overview]
Message-ID: <2429639.puuGestFgj@localhost> (raw)
In-Reply-To: <20120924173633.GA2451@kroah.com>
On Monday 24 of September 2012 10:36:33 Greg KH wrote:
> On Mon, Sep 24, 2012 at 10:05:23AM +0200, Paweł Sikora wrote:
> > Hi,
> >
> > with the new stable line i'm observing strange locks on my old amd-phenom-II mini-server.
> > here's a dmesg:
>
> Did this show up in 3.5.3? If not, can you run 'git bisect' to find the
> problem patch?
heh, the old good kernel put some light on this issue.
Sep 25 08:50:24 nexus kernel: [60330.301639] Clocksource tsc unstable (delta = -474690884 ns)
Sep 25 08:50:24 nexus kernel: [60330.325477] ------------[ cut here ]------------
Sep 25 08:50:24 nexus kernel: [60330.325484] WARNING: at /home/users/builder/rpm/BUILD/kernel-2.6.37.6/linux-2.6.37/net/sched/sch_generic.c:258 dev_watchdog+0x25d/0x270()
Sep 25 08:50:24 nexus kernel: [60330.325486] Hardware name: GA-MA785GMT-UD2H
Sep 25 08:50:24 nexus kernel: [60330.325487] NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
(...)
Sep 25 08:50:25 nexus kernel: [60330.851093] Switching to clocksource acpi_pm
afaics, this amd-phenom cpu does the cpu frequency scaling and causes plain 'tsc' timer
instability which leads to network card watchdog timeout (i can login via local console
while any network traffic is dead). on the recent 3.5.x kernel the 'clocksource unstable'
message appears *after* 'task blocked' flood and there's no clear info about watchog timeout.
currently i'm testing hpet clocksource becasue better tsc modes (constant_tsc, nonstop_tsc)
aren't present in /sys/devices/system/clocksource/clocksource0/available_clocksource while
cpu supports them.
next prev parent reply other threads:[~2012-09-25 16:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 8:05 [3.5.4] rcu_sched self-detected stall on CPU { 1} (t=54862991 jiffies) Paweł Sikora
2012-09-24 17:36 ` Greg KH
2012-09-25 16:31 ` Paweł Sikora [this message]
2012-09-25 16:44 ` Greg KH
2012-09-25 17:04 ` Paweł Sikora
2012-09-25 19:42 ` Greg KH
2012-10-03 18:03 ` Paul E. McKenney
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=2429639.puuGestFgj@localhost \
--to=pluto@pld-linux.org \
--cc=arekm@pld-linux.org \
--cc=baggins@pld-linux.org \
--cc=gregkh@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox