All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: Martin Steigerwald <martin@lichtvoll.de>,
	Oleksandr Natalenko <oleksandr@natalenko.name>
Cc: Ming Lei <ming.lei@redhat.com>, Jens Axboe <axboe@kernel.dk>,
	Christoph Hellwig <hch@lst.de>,
	linux-block@vger.kernel.org, linux-raid@vger.kernel.org,
	linux-kernel@vger.kernel.org, Shaohua Li <shli@kernel.org>
Subject: Re: I/O hangs after resuming from suspend-to-ram
Date: Sat, 26 Aug 2017 18:17:11 +0100	[thread overview]
Message-ID: <59A1AD17.70208@youngman.org.uk> (raw)
In-Reply-To: <4679671.be02cq1OFG@merkaba>

On 26/08/17 12:19, Martin Steigerwald wrote:
> Also… when a hang happened the mouse pointer was frozen, Ctrl-Alt-F1 didn´t 
> work and so on… so it may easily be a completely different issue.
> 
> I did not see much point in reporting it so far… as I have no idea on how to 
> reliably pin-point the issue. It happens once every few days, so a bisect 
> again is out of questions – (it is anyway for a production machine for me) –, 
> it appears to be a hard freeze, so no debug data… its one of these "you don´t 
> get to debug me" hangs again. I really have no idea how to a get hold on such 
> complexity. I am hoping to at least pin-point the exact kernel option that 
> triggers this issue, but it may take weeks to do so. I´d really love a way for 
> the kernel to at least to write out debug data before doing hanging 
> completely.

This sounds like what I'm getting - SuSE 42.3, no raid, doesn't happen
when the power lead is in (but I think the laptop is configured not to
suspend when powered, precisely to avoid exactly this).

It happens to me quite often, unfortunately, but it seems a KDE issue in
that applications work fine, UNTIL KDE seems to get control of the mouse
at which point I can't do anything.

I've got a feeling it's related to wireless networking actually, my
setup is somewhat borked because KDE, systemd, and wifi don't seem to
work nicely together :-(

Cheers,
Wol

  reply	other threads:[~2017-08-26 17:17 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-22 11:45 I/O hangs after resuming from suspend-to-ram Oleksandr Natalenko
2017-08-26 10:37 ` Oleksandr Natalenko
2017-08-26 10:37   ` Oleksandr Natalenko
2017-08-26 10:48   ` Oleksandr Natalenko
2017-08-26 10:48     ` Oleksandr Natalenko
2017-08-26 11:19     ` Martin Steigerwald
2017-08-26 11:19       ` Martin Steigerwald
2017-08-26 17:17       ` Wols Lists [this message]
2017-08-26 19:33         ` Martin Steigerwald
2017-08-26 19:33           ` Martin Steigerwald
2017-08-26 13:32     ` Oleksandr Natalenko
2017-08-26 13:32       ` Oleksandr Natalenko
2017-08-27  6:02     ` Ming Lei
2017-08-27  7:43       ` Oleksandr Natalenko
2017-08-27  7:43         ` Oleksandr Natalenko
2017-08-28 12:58         ` Ming Lei
2017-08-28 12:58           ` Ming Lei
2017-08-28 13:10           ` Martin Steigerwald
2017-08-28 13:10             ` Martin Steigerwald
2017-08-28 13:32             ` Ming Lei
2017-09-20 17:25               ` Martin Steigerwald
2017-09-20 22:17                 ` Ming Lei
2017-09-24 17:33                   ` Martin Steigerwald
2017-09-24 17:33                     ` Martin Steigerwald
2017-09-25  2:59                     ` Ming Lei
2017-09-25 14:13                       ` Martin Steigerwald
2017-09-25 14:13                         ` Martin Steigerwald
2017-09-20 22:20             ` Ming Lei
2017-09-21  7:30               ` Martin Steigerwald
2017-09-21  7:30                 ` Martin Steigerwald
2017-09-21  7:33                 ` Martin Steigerwald
2017-09-21  7:33                   ` Martin Steigerwald
2017-08-28 18:22           ` Oleksandr Natalenko
2017-08-28 18:22             ` Oleksandr Natalenko
2017-08-29  0:24             ` Ming Lei
2017-08-29 15:52               ` Oleksandr Natalenko
2017-08-29 15:52                 ` Oleksandr Natalenko
2017-08-30  2:15                 ` Ming Lei
2017-08-30  5:17                   ` Ming Lei
2017-08-30  6:15                     ` oleksandr
2017-08-30  8:06                       ` Ming Lei
2017-08-30  8:06                         ` Ming Lei
2017-08-30 10:58                         ` oleksandr
2017-08-30 14:37                           ` Ming Lei

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=59A1AD17.70208@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=martin@lichtvoll.de \
    --cc=ming.lei@redhat.com \
    --cc=oleksandr@natalenko.name \
    --cc=shli@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.