From: Filipe Manana <fdmanana@suse.com>
To: Bastien ROUCARIES <roucaries.bastien@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: bo.li.liu@oracle.com, clm@fb.com
Subject: Re: S2ram + btrfs with recent kernel => soft lockup warning and hard hang
Date: Mon, 13 Feb 2017 10:43:32 +0000 [thread overview]
Message-ID: <a8ce83ef-efa6-e8b2-e61d-b03cd82b6c86@suse.com> (raw)
In-Reply-To: <CAE2SPAarz6+Oeu1K5BECSaD_FxiSErjx=FC9sspg2p1sotD0vw@mail.gmail.com>
On 02/12/2017 03:45 PM, Bastien ROUCARIES wrote:
> Hi,
>
> Since 3.8 s2ram on btrfs system lead to hang.
>
> Could not save a trace will try to get a few picture but trace are similar to :
> https://github.com/docker/docker/issues/15654
> and
> https://patchwork.kernel.org/patch/8352811/
>
> It is 100% reproducible.
3.8 is very old, and so is 3.19 (which is what you're running as shown
in the github issue). Many fixes landed after 3.19. Just try a recent
kernel.
>
> mount table
> /dev/mapper/portable2015--bastien--vg-HOME on /var/cache/pbuilder type
> btrfs (rw,relatime,lazytime,compress=zlib,space_cache,subvolid=934,subvol=/pbuilder)
> /dev/mapper/portable2015--bastien--vg-HOME on /home type btrfs
> (rw,nosuid,nodev,relatime,lazytime,compress=zlib,space_cache,subvolid=933,subvol=/home)
>
> btrfs is over dm-crypt
>
> Bastien
>
next prev parent reply other threads:[~2017-02-13 10:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-12 15:45 S2ram + btrfs with recent kernel => soft lockup warning and hard hang Bastien ROUCARIES
2017-02-13 10:43 ` Filipe Manana [this message]
2017-02-13 11:05 ` Bastien ROUCARIES
2017-02-13 11:06 ` Bastien ROUCARIES
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=a8ce83ef-efa6-e8b2-e61d-b03cd82b6c86@suse.com \
--to=fdmanana@suse.com \
--cc=bo.li.liu@oracle.com \
--cc=clm@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roucaries.bastien@gmail.com \
/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