From: Chris Samuel <chris@csamuel.org>
To: linux-btrfs@vger.kernel.org
Cc: Marc MERLIN <marc@merlins.org>,
Chris Murphy <lists@colorremedies.com>,
bo.li.liu@oracle.com, jbacik@fb.com, hugo@carfax.org.uk,
dsterba@suse.cz, clm@fb.com
Subject: Re: btrfs cleaner failure - fs/btrfs/extent-tree.c:5748 (3.14.0)
Date: Sat, 10 May 2014 10:13:43 +1000 [thread overview]
Message-ID: <2678329.EOSaIZaHNO@quad> (raw)
In-Reply-To: <20140509223659.GW11401@merlins.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Marc,
On Fri, 9 May 2014 03:36:59 PM Marc MERLIN wrote:
> Oh, I missed that.
> May 2 14:23:06 legolas kernel: [283268.319035] CPU: 0 PID: 25726 Comm:
> watchdog/0 Tainted: G W 3.14.0-amd64-i915-preempt-20140216 #2
> This is weird because I don't use any 3rd party binary modules.
There's actually a bunch of reasons a kernel can be tainted.
> Right now, I do see:
> legolas:~# cat /proc/sys/kernel/tainted
> 512
IIUC that's an array of bit flags, and that value means you've had a previous
kernel warning at that point according to:
https://www.kernel.org/doc/Documentation/sysctl/kernel.txt
# tainted:
#
# Non-zero if the kernel has been tainted. Numeric values,
# which can be ORed together:
#
[...]
# 512 - A kernel warning has occurred.
Best of luck!
Chris
- --
Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQEVAwUBU21vOo1yjaOTJg85AQLJDwf/QOxRt0f5KqPbhknn8x0XyUQ5upC8PbzD
FoDHAkKV7tCUGQ6ZmCufBUKi0beNHNE3YKXlld8zLjlYpyV5lCZIgP3XvjQ/A4pZ
Vq+XKiqddaZHOFnjQuk9kseqXJaeH7Vr90xz2D92lcRb3NY6yoD2sdFMhAeN43vh
23stzC2Ybr79NFELWPCL3MTFL4qZrAY/4KFFKDQEZsNHMEJW2zJXX841lFsTXJwO
1Ggsi3WzNCJMo+GHRqH+9Gyb4ICk7u7FABHo+y/dShTGnxAh5/8zMnKidlSfCdzd
APKPMrydKEX+O+Fm3zDcKg8gER3FJtWKCyHXfW+zyORTMbxiH5QK5Q==
=q69d
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-05-10 0:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 23:39 URGENT: my laptop's boot ssd btrfs crashed, what do you need off it? Marc MERLIN
2014-05-08 0:38 ` Chris Mason
2014-05-08 0:43 ` Marc MERLIN
2014-05-08 1:34 ` Marc MERLIN
2014-05-08 17:40 ` Justin Maggard
2014-05-08 22:02 ` Marc MERLIN
2014-05-09 10:35 ` Fwd: " Marc MERLIN
2014-05-09 16:19 ` Chris Murphy
2014-05-09 22:36 ` btrfs cleaner failure - fs/btrfs/extent-tree.c:5748 (3.14.0) Marc MERLIN
2014-05-10 0:00 ` Chris Murphy
2014-05-10 0:42 ` Marc MERLIN
2014-05-10 1:05 ` Hugo Mills
2014-05-10 1:54 ` Chris Murphy
2014-05-10 13:51 ` Marc MERLIN
2014-05-10 16:34 ` Chris Murphy
2014-05-10 1:09 ` Hugo Mills
2014-05-10 2:02 ` Duncan
2014-05-10 3:40 ` Marc MERLIN
2014-05-11 2:28 ` Duncan
2014-05-11 12:34 ` Marc MERLIN
2014-05-10 0:13 ` Chris Samuel [this message]
2014-05-10 9:26 ` URGENT: my laptop's boot ssd btrfs crashed, what do you need off it? Tom Kuther
2014-05-10 11:42 ` Chris Samuel
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=2678329.EOSaIZaHNO@quad \
--to=chris@csamuel.org \
--cc=bo.li.liu@oracle.com \
--cc=clm@fb.com \
--cc=dsterba@suse.cz \
--cc=hugo@carfax.org.uk \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=marc@merlins.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.