From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 62751] INFO: rcu_sched detected stalls on CPUs/tasks: { 3} (detected by 2, t=15107 jiffies, g=270766, c=270765, q=0)
Date: Mon, 04 Nov 2013 11:53:01 +0000 [thread overview]
Message-ID: <bug-62751-13602-v8iI8NrTkb@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-62751-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=62751
Alan <alan@lxorguk.ukuu.org.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alan@lxorguk.ukuu.org.uk
Kernel Version|3.11.6-031106-generic |3.11.6
--- Comment #7 from Alan <alan@lxorguk.ukuu.org.uk> ---
Jan - its on a vmware virtual platform so it could just be that vmware ran off
with the CPU. Can you duplicate this on a native platform, and if you disable
the NMI watchdog does the kernel hang or merely stall for a moment in this
situation ?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2013-11-04 11:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 13:55 [Bug 62751] New: INFO: rcu_sched detected stalls on CPUs/tasks: { 3} (detected by 2, t=15107 jiffies, g=270766, c=270765, q=0) bugzilla-daemon
2013-10-09 13:59 ` [Bug 62751] " bugzilla-daemon
2013-10-09 15:10 ` bugzilla-daemon
2013-10-09 20:53 ` bugzilla-daemon
2013-10-10 6:49 ` bugzilla-daemon
2013-10-10 6:56 ` bugzilla-daemon
2013-10-24 8:18 ` bugzilla-daemon
2013-10-24 10:18 ` bugzilla-daemon
2013-11-04 11:53 ` bugzilla-daemon [this message]
2013-11-13 13:44 ` bugzilla-daemon
2013-11-18 7:51 ` bugzilla-daemon
2013-11-18 7:53 ` bugzilla-daemon
2013-11-18 7:54 ` bugzilla-daemon
2013-12-07 10:08 ` bugzilla-daemon
2013-12-20 15:45 ` bugzilla-daemon
2013-12-20 16:16 ` bugzilla-daemon
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=bug-62751-13602-v8iI8NrTkb@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).