public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Bill Kenworthy <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Kernel 4.12.5 hard lockups, nothing in logs.
Date: Sun, 20 Aug 2017 11:47:14 +0800	[thread overview]
Message-ID: <033c887c-b9a1-c576-aee0-85e7953b7c3b@iinet.net.au> (raw)

Hi all,
	I am getting random lockups on kernel 4.12.5.

Three intel hosts (atom, early i7, i7 haswell) - its worse after a
suspend resume session.  Because these are in use Ive gone back to
4.9.34 which is stable.

I also have some VM's and an MS surface pro 4 which are stable on
4.12.5, 6 and 8) - confusing!

Is anyone else seeing this?

BillK


             reply	other threads:[~2017-08-20  3:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-20  3:47 Bill Kenworthy [this message]
2017-08-20  9:21 ` [gentoo-user] Kernel 4.12.5 hard lockups, nothing in logs Alan McKinnon
2017-08-20  9:39   ` Bill Kenworthy
2017-08-20 10:39     ` Mick
2017-08-21  6:49   ` Raffaele Belardi
2017-08-23 22:54   ` Frank Steinmetzger
2017-08-20 14:47 ` Roman Dobosz

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=033c887c-b9a1-c576-aee0-85e7953b7c3b@iinet.net.au \
    --to=billk@iinet.net.au \
    --cc=gentoo-user@lists.gentoo.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