linux-kernel - Re: I/O hangs after resuming from suspend-to-ram

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sat, 26 Aug 2017 18:17:11 +0100
From:   Wols Lists <antlists@...ngman.org.uk>
To:     Martin Steigerwald <martin@...htvoll.de>,
        Oleksandr Natalenko <oleksandr@...alenko.name>
Cc:     Ming Lei <ming.lei@...hat.com>, Jens Axboe <axboe@...nel.dk>,
        Christoph Hellwig <hch@....de>, linux-block@...r.kernel.org,
        linux-raid@...r.kernel.org, linux-kernel@...r.kernel.org,
        Shaohua Li <shli@...nel.org>
Subject: Re: I/O hangs after resuming from suspend-to-ram

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