mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Donald Parsons <dparsons@brightdsl.net>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux 4.15-rc4
Date: Mon, 18 Dec 2017 18:24:20 -0500	[thread overview]
Message-ID: <1513639460.2649.23.camel@brightdsl.net> (raw)

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

             reply	other threads:[~2017-12-18 23:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-18 23:24 Donald Parsons [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-12-18  3:38 Linus Torvalds

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=1513639460.2649.23.camel@brightdsl.net \
    --to=dparsons@brightdsl.net \
    --cc=linux-kernel@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

Powered by JetHome