<html>
    <head>
      <base href="https://bugs.freedesktop.org/">
    </head>
    <body>
      <p>
        <div>
            <b><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - [BAT][ELK] The machine fails to resume after 4.13-rc1"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=101838#c9">Comment # 9</a>
              on <a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - [BAT][ELK] The machine fails to resume after 4.13-rc1"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=101838">bug 101838</a>
              from <span class="vcard"><a class="email" href="mailto:martin.peres@free.fr" title="Martin Peres <martin.peres@free.fr>"> <span class="fn">Martin Peres</span></a>
</span></b>
        <pre>(In reply to latalante from <a href="show_bug.cgi?id=101838#c8">comment #8</a>)
<span class="quote">> (In reply to Martin Peres from <a href="show_bug.cgi?id=101838#c7">comment #7</a>)
> > Thanks, I communicated that to the developers. I hope it helps.

> Sorry for the unnecessary misleading.
> In my case, hanging out after sleep is related to - mq-deadline/ext4 IO
> hangs.
> <a href="https://lkml.org/lkml/2017/6/25/248">https://lkml.org/lkml/2017/6/25/248</a>

> I have no idea why he disappeared default CFQ scheduler, though in the
> configuration it is:
> CONFIG_IOSCHED_CFQ=y
> CONFIG_DEFAULT_CFQ=y
> CONFIG_DEFAULT_IOSCHED="cfq"

> 4.12.3
> cat /sys/block/sda/queue/scheduler
> [cfq]

> 4.13-rc2
> cat /sys/block/sda/queue/scheduler
> [mq-deadline] bfq none

> After
> echo none > /sys/block/sda/queue/scheduler
> I did not noticed any hang on the kernel 4.13-rc2 (out after sleep).</span >

Thanks for the info!

The following patch fixes the issue for us: <a href="https://lkml.org/lkml/2017/7/27/653">https://lkml.org/lkml/2017/7/27/653</a></pre>
        </div>
      </p>


      <hr>
      <span>You are receiving this mail because:</span>

      <ul>
          <li>You are the assignee for the bug.</li>
          <li>You are on the CC list for the bug.</li>
          <li>You are the QA Contact for the bug.</li>
      </ul>
    </body>
</html>