public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Coelho, Luciano" <luciano.coelho@intel.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: rcu_sched self-detected stall on 4.2-rc6
Date: Thu, 20 Aug 2015 10:51:14 +0000	[thread overview]
Message-ID: <1440067870.3793.12.camel@intel.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 3172 bytes --]

Hi,

Yesterday I suddenly got an RCU stall on my machine.  I don't know what
really led to it, I just started getting "BUG: soft lockup" messages on
all my terminals.

Here's a small extract of what the logs show:

[88989.550488] INFO: rcu_sched self-detected stall on CPU { 0}  (t=5250 jiffies g=2697311 c=2697310 q=12358)
[88989.550496] Task dump for CPU 0:
[88989.550499] chrome          R  running task        0  2311   2241 0x00000108
[88989.550502]  0000000000000001 ffffffff81854ac0 ffffffff810c33a0 000000000029285f
[88989.550505]  ffff88031ea16500 ffffffff81854ac0 0000000000000000 ffffffff81907580
[88989.550508]  ffffffff810c6501 ffff88030c7b9140 ffffffff81088d05 ffffffff81ac14c0
[88989.550510] Call Trace:
[88989.550512]  <IRQ>  [<ffffffff810c33a0>] ? rcu_dump_cpu_stacks+0x80/0xb0
[88989.550522]  [<ffffffff810c6501>] ? rcu_check_callbacks+0x421/0x6e0
[88989.550525]  [<ffffffff81088d05>] ? notifier_call_chain+0x45/0x70
[88989.550528]  [<ffffffff810d02e1>] ? timekeeping_update+0xf1/0x150
[88989.550531]  [<ffffffff810d9290>] ? tick_sched_handle.isra.15+0x60/0x60
[88989.550534]  [<ffffffff810caf66>] ? update_process_times+0x36/0x60
[88989.550537]  [<ffffffff810d9290>] ? tick_sched_handle.isra.15+0x60/0x60
[88989.550539]  [<ffffffff810d9254>] ? tick_sched_handle.isra.15+0x24/0x60
[88989.550542]  [<ffffffff810d9290>] ? tick_sched_handle.isra.15+0x60/0x60
[88989.550545]  [<ffffffff810d92cb>] ? tick_sched_timer+0x3b/0x70
[88989.550547]  [<ffffffff810cba66>] ? __hrtimer_run_queues+0xd6/0x200
[88989.550551]  [<ffffffff8101c2e5>] ? read_tsc+0x5/0x10
[88989.550554]  [<ffffffff810cbe7a>] ? hrtimer_interrupt+0x9a/0x180
[88989.550558]  [<ffffffff815692b9>] ? smp_apic_timer_interrupt+0x39/0x50
[88989.550560]  [<ffffffff8156749b>] ? apic_timer_interrupt+0x6b/0x70
[88989.550563]  [<ffffffff810c9770>] ? del_timer+0x60/0x60
[88989.550565]  [<ffffffff810c9814>] ? del_timer_sync+0x44/0x50
[88989.550569]  [<ffffffff814b6ea0>] ? inet_csk_reqsk_queue_drop+0x60/0x1b0
[88989.550572]  [<ffffffff814b70df>] ? reqsk_timer_handler+0xef/0x280
[88989.550574]  [<ffffffff814b6ff0>] ? inet_csk_reqsk_queue_drop+0x1b0/0x1b0
[88989.550576]  [<ffffffff810c9020>] ? call_timer_fn+0x30/0xe0
[88989.550578]  [<ffffffff814b6ff0>] ? inet_csk_reqsk_queue_drop+0x1b0/0x1b0
[88989.550581]  [<ffffffff810c9513>] ? run_timer_softirq+0x163/0x280
[88989.550583]  [<ffffffff8101c2e5>] ? read_tsc+0x5/0x10
[88989.550586]  [<ffffffff8106fbfe>] ? __do_softirq+0xfe/0x250
[88989.550589]  [<ffffffff8106fec2>] ? irq_exit+0x92/0xa0
[88989.550592]  [<ffffffff815692be>] ? smp_apic_timer_interrupt+0x3e/0x50
[88989.550594]  [<ffffffff8156749b>] ? apic_timer_interrupt+0x6b/0x70
[88989.550595]  <EOI> 
[89008.593604] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [swapper/2:0]

The full log can be found here (there are lots of drm/i915 warnings
too, but I think they're unrelated): 

http://pastebin.coelho.fi/265ebd1dcd443446.txt 

Has anyone else seen this? Or does anyone have a clue of what it might be?

--
Cheers,
Luca.ÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥

                 reply	other threads:[~2015-08-20 10:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1440067870.3793.12.camel@intel.com \
    --to=luciano.coelho@intel.com \
    --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