From: Russell Coker <russell@coker.com.au>
To: linux-btrfs@vger.kernel.org
Subject: NMI from btrfs cron jobs in 3.11.6
Date: Thu, 14 Nov 2013 01:45:29 +1100 [thread overview]
Message-ID: <201311140145.29255.russell@coker.com.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 3029 bytes --]
Nov 14 00:00:01 workstation /USR/SBIN/CRON[30993]: (root) CMD
(/usr/local/sbin/btrfs-make-snapshot minutes /home >> /var/log/snapshot.log)
Nov 14 00:00:01 workstation /USR/SBIN/CRON[30994]: (root) CMD
(/usr/local/sbin/btrfs-make-snapshot days /home >> /var/log/snapshot.log)
Nov 14 00:00:01 workstation /USR/SBIN/CRON[30995]: (root) CMD
(/usr/local/sbin/btrfs-remove-snapshots 100 100 /home/ / >>
/var/log/snapshot.log)
Below is a grep for NMI in my kernel message log. I'm running Debian kernel
3.11.6-2 on a quad-core AMD64 system. Above is the relevant section of the
cron log. It appears that running two scripts that create snapshots at the
same time as a script that removes maybe 97 snapshots causes an NMI. I've
attached the kernel message log from today, I can give you logs from other
days if they are useful.
Nov 11 00:00:58 workstation kernel: [896466.616001] sending NMI to all CPUs:
Nov 11 00:00:58 workstation kernel: [896466.616016] NMI backtrace for cpu 0
Nov 11 00:00:58 workstation kernel: [896466.616001] NMI backtrace for cpu 2
Nov 11 00:00:58 workstation kernel: [896466.616479] NMI backtrace for cpu 3
Nov 11 00:00:58 workstation kernel: [896466.616637] NMI backtrace for cpu 1
Nov 12 00:00:58 workstation kernel: [982863.428000] sending NMI to all CPUs:
Nov 12 00:00:58 workstation kernel: [982863.428000] NMI backtrace for cpu 1
Nov 12 00:00:58 workstation kernel: [982863.428340] NMI backtrace for cpu 0
Nov 12 00:00:58 workstation kernel: [982863.428647] NMI backtrace for cpu 2
Nov 12 00:00:58 workstation kernel: [982863.428725] NMI backtrace for cpu 3
Nov 13 00:00:57 workstation kernel: [1069265.036001] sending NMI to all CPUs:
Nov 13 00:00:57 workstation kernel: [1069265.036018] NMI backtrace for cpu 1
Nov 13 00:00:57 workstation kernel: [1069265.036341] NMI backtrace for cpu 0
Nov 13 00:00:57 workstation kernel: [1069265.036001] NMI backtrace for cpu 2
Nov 13 00:00:57 workstation kernel: [1069265.036723] NMI backtrace for cpu 3
Nov 13 22:21:04 workstation kernel: [1149672.214144] INFO: NMI handler
(perf_event_nmi_handler) took too long to run: 6.060 msecs
Nov 14 00:00:56 workstation kernel: [1155663.796001] sending NMI to all CPUs:
Nov 14 00:00:56 workstation kernel: [1155663.796001] NMI backtrace for cpu 2
Nov 14 00:00:56 workstation kernel: [1155663.796269] NMI backtrace for cpu 3
Nov 14 00:00:56 workstation kernel: [1155663.796007] NMI backtrace for cpu 1
Nov 14 00:00:56 workstation kernel: [1155663.796581] NMI backtrace for cpu 0
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
[-- Attachment #2: oops.gz --]
[-- Type: application/x-gzip, Size: 2761 bytes --]
next reply other threads:[~2013-11-13 14:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 14:45 Russell Coker [this message]
2013-11-13 15:15 ` NMI from btrfs cron jobs in 3.11.6 Duncan
2013-11-17 14:43 ` Russell Coker
2013-11-17 15:16 ` Marc MERLIN
2013-11-28 17:10 ` David Sterba
2013-11-28 17:37 ` David Sterba
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=201311140145.29255.russell@coker.com.au \
--to=russell@coker.com.au \
--cc=linux-btrfs@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.