Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759927AbdLRX6s (ORCPT ); Mon, 18 Dec 2017 18:58:48 -0500 Received: from phil.doycomm.com ([66.219.128.249]:52828 "EHLO phil.doycomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759637AbdLRX6r (ORCPT ); Mon, 18 Dec 2017 18:58:47 -0500 X-Greylist: delayed 2059 seconds by postgrey-1.27 at vger.kernel.org; Mon, 18 Dec 2017 18:58:46 EST Message-ID: <1513639460.2649.23.camel@brightdsl.net> Subject: Re: Linux 4.15-rc4 From: Donald Parsons To: linux-kernel Date: Mon, 18 Dec 2017 18:24:20 -0500 Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.24.6 (3.24.6-1.fc26) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1218 Lines: 26 Suspend still failing to start up again. Screen is blank and ssh finds no path but computer looks and sounds like it is running normally. PC is 6 months old and suspend worked flawlessly until roughly 2 to 3 weeks ago. This is Fedora 26 using always the latest Fedora provided kernels or Linus' kernels compiled by me. Both started to have resume failures. vmlinuz-4.13.15-200.fc26.x86_64 works usually (failed once out of 3 or 4) and later ones never work(? fail 2 out of 2). It seems a suspend problem was back-ported starting about vmlinuz- 4.13.15 because I never saw failure earlier, eg. vmlinuz-4.13.5--14- 200.fc26.x86_64 Also the chance of resume failure seems to increase the longer I wait, like resume will probably work after 10 or 20 minutes but after 12 hours it seems to fail almost always. But to be certain, this would need much more testing! Hardware in desktop PC: Motherboard, ASRock Fata1ity Z270 Gaming K6 (2.11 beta bios) Video card, MSI GeForce GTX 1070 Gaming X 8G CPU, Intel i7-7700K (not overclocked) Memory, G.SKILL DDR4 3200 8GBx2 (F4-3200C16D-16GVK) M.2 storage, Samsung 1TB 960 EVO NVMe M.2 SSD PSU, EVGA 750BQ model 110-BQ-0750 Don