From: "Marcelo \"Marc\" Ranolfi" <marc.2377@gmail.com>
To: Chao Yu <chao@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: Userspace locks at f2fs_issue_flush kernel call, hard reset necessary
Date: Wed, 23 Aug 2017 14:26:32 -0300 [thread overview]
Message-ID: <CAETC-g_vr_JcB6eTdFzyga9EyV799wKOpeYYnYGExThsvS+NgQ@mail.gmail.com> (raw)
In-Reply-To: <CAETC-g9CJ_vzzD7a53QuXxYD8wX6oLPENq7nZTo-8PK6UANf-A@mail.gmail.com>
Chao,
I just had the same problem, with kernel 4.12.8 with patch _f2fs: fix
out-of-order execution in f2fs_issue_flush_.
On Tue, Aug 22, 2017 at 2:00 PM, Marcelo "Marc" Ranolfi
<marc.2377@gmail.com> wrote:
> Hi Chao
>
> I'm testing the kernel with your patch since last night. Will give new
> feedback a couple of days/weeks about how it goes.
>
>
> Thank you.
>
>
>
> On Mon, Aug 21, 2017 at 11:58 AM, Chao Yu <chao@kernel.org> wrote:
>> Hi Marcelo,
>>
>> Thanks for the report!
>>
>> Would you have a try with below patch?
>>
>> f2fs: fix out-of-order execution in f2fs_issue_flush
>>
>> Thanks,
>>
>> On 2017/8/16 15:24, Marcelo "Marc" Ranolfi wrote:
>>> Just wanted to let you all know that this is still an issue, even with
>>> the 4.12.7 kernel.
>>>
>>> The two most affected applications are qemu-system-x86_64 and totem.
>>>
>>> On Wed, Aug 9, 2017 at 3:04 AM, Marcelo "Marc" Ranolfi
>>> <marc.2377@gmail.com> wrote:
>>>> What follows is a bug report.
>>>>
>>>> I've been experiencing system lockups somewhat randomly. Sometimes an
>>>> application freezes, and when I go check its properties, it says the
>>>> process' Wait Channel is _f2fs_issue_flush_.
>>>>
>>>> Sometimes it's the qemu process (which I use via libvirt), other times
>>>> it's Firefox, or Gnome Videos (totem) and it happened to Nemo once as
>>>> well. I have screenshots if necessary.
>>>>
>>>> I've been tracking this with screenshots, and it's happenning every 4
>>>> days - on average.
>>>>
>>>> When this happens, the process stays unresponsive no matter what. I tried:
>>>>
>>>> - Restarting swap
>>>> - Restarting the Display Manager
>>>> - Graceful shutdown / reboot - takes forever, doesn't work
>>>> - Shutdown -k and unmounting filesystems from command line - root
>>>> can't be unmounted unless -l used, no solution
>>>>
>>>> The only working solution is to reset the machine via power button or
>>>> #reboot -f.
>>>>
>>>> I have:
>>>>
>>>> - Kingston SV300S37A120G - hardware is fine, I have other OS / filesystems on it
>>>> - f2fs filesystem in a 40 GB partition, GPT
>>>> - kernel 4.12.4 with systemd 234.11 - typical up-to-date Arch Linux setup.
>>>>
>>>> You gentlemen let me know if I provide more help.
>>>>
>>>> Best,
>>>> Marc
>>>
>>> ------------------------------------------------------------------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> _______________________________________________
>>> Linux-f2fs-devel mailing list
>>> Linux-f2fs-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
>>>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
next prev parent reply other threads:[~2017-08-23 17:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAETC-g9+HJXSL4mqgzdTBoaOyoXU5OwL9TsFxUURNRQQ2tryxA@mail.gmail.com>
2017-08-16 7:24 ` Userspace locks at f2fs_issue_flush kernel call, hard reset necessary Marcelo "Marc" Ranolfi
2017-08-21 14:58 ` Chao Yu
2017-08-22 17:00 ` Marcelo "Marc" Ranolfi
2017-08-23 17:26 ` Marcelo "Marc" Ranolfi [this message]
2017-08-30 17:02 ` Marcelo "Marc" Ranolfi
2017-08-31 11:01 ` Chao Yu
2017-09-01 4:54 ` Marcelo "Marc" Ranolfi
2017-09-14 2:22 ` Chao Yu
2017-10-13 4:19 ` Marcelo "Marc" Ranolfi
2017-10-13 11:13 ` Chao Yu
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=CAETC-g_vr_JcB6eTdFzyga9EyV799wKOpeYYnYGExThsvS+NgQ@mail.gmail.com \
--to=marc.2377@gmail.com \
--cc=chao@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).