From: Maciej Piechotka <uzytkownik2@gmail.com>
To: linux-bcache@vger.kernel.org
Subject: Re: bcache hangs on suspend when cache device is attached
Date: Fri, 22 Apr 2016 01:33:40 +0000 (UTC) [thread overview]
Message-ID: <loom.20160422T033159-792@post.gmane.org> (raw)
In-Reply-To: loom.20160419T225909-455@post.gmane.org
Maciej Piechotka <uzytkownik2 <at> gmail.com> writes:
>
> Eric Wheeler <bcache <at> lists.ewheeler.net> writes:
>
> >
> > Interesting. Can you collect the dmesg output as it suspends/resumes via
> > serial or something other means?
> >
>
> I'll try to capture the output today.
>
>
The USB-to-serial I was using requires firmware which for some reasons in my
setup (luks + lvm + dracut) prevents the whole thing from working - I'm able
to set up serial connection between 2 computers (including getty) but not
loging. I'll try netconsole later on - maybe with better result.
prev parent reply other threads:[~2016-04-22 1:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 15:45 bcache hangs on suspend when cache device is attached Maciej Piechotka
2016-04-17 18:08 ` Eric Wheeler
2016-04-19 21:00 ` Maciej Piechotka
2016-04-22 1:33 ` Maciej Piechotka [this message]
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=loom.20160422T033159-792@post.gmane.org \
--to=uzytkownik2@gmail.com \
--cc=linux-bcache@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).