From: Martin Steigerwald <martin@lichtvoll.de>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: linux-bcachefs@vger.kernel.org
Subject: Re: Questions related to BCacheFS
Date: Sun, 03 Dec 2023 17:58:36 +0100 [thread overview]
Message-ID: <2272887.iZASKD2KPV@lichtvoll.de> (raw)
In-Reply-To: <20231119231001.tb3teva5j4azqp7i@moria.home.lan>
Kent Overstreet - 20.11.23, 00:10:01 CET:
> > I got two setbacks regarding trying BCacheFS on my laptop yesterday
> > and
> > today:
> >
> > 1) Linux 6.7-rc1, as mentioned almost rc2, did not hibernate on
> > ThinkPad T14 AMD Gen 1. It just blanked screen and nothing happened.
> > So I went back to 6.6.1 temporarily. I do not really intend to do a
> > git bisect between rc1 and 6.6 on a production laptop. It would be
> > very time-consuming and possibly be dangerous. I may go back to 6.7
> > even without hibernation, just using standby over night for a while.
> > I bet BCacheFS is compatible with hibernation (as in writing memory
> > contents to encrypted swap and resuming from it)?
>
> I believe so - I have not tested hibernation specifically.
Today I tried with 6.7-rc4 and the issue of non working hibernation does
not seem to be related to BCacheFS, cause the module was not loaded and it
again did not hibernate.
--
Martin
next prev parent reply other threads:[~2023-12-03 16:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-18 19:15 Questions related to BCacheFS Martin Steigerwald
2023-11-18 19:50 ` Kent Overstreet
2023-11-18 20:57 ` Martin Steigerwald
2023-11-18 21:07 ` Kent Overstreet
2023-11-18 23:15 ` Martin Steigerwald
2023-11-18 23:42 ` Kent Overstreet
2023-11-19 11:13 ` Martin Steigerwald
2023-11-19 16:43 ` Martin Steigerwald
2023-11-19 23:10 ` Kent Overstreet
2023-11-20 17:34 ` Martin Steigerwald
2023-12-03 16:58 ` Martin Steigerwald [this message]
2023-12-18 16:50 ` Martin Steigerwald
2023-12-28 22:29 ` deletion time of big files (was: Re: Questions related to BCacheFS) Martin Steigerwald
2023-12-29 18:48 ` Kent Overstreet
2023-12-30 10:51 ` Martin Steigerwald
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=2272887.iZASKD2KPV@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@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).