mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Thomas Müller" <thomas@mathtm.de>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: disabling secondary CPU hangs / system fails to suspend with kernel 4.19+
Date: Fri, 12 Apr 2019 07:30:15 +0200	[thread overview]
Message-ID: <9a345d3c-c17c-95b2-dcbe-af72dee42a1a@mathtm.de> (raw)
In-Reply-To: <ab509a07-d597-2925-b39a-f1b4e86e5850@mathtm.de>

Hi,

good news: starting with 5.0.6 suspend is working again.

Best regards
Thomas

Am 29.03.19 um 10:22 schrieb Thomas Müller:
> Hi,
> 
> Am 18.03.19 um 12:57 schrieb Peter Zijlstra:
>> On Fri, Mar 15, 2019 at 09:21:02PM +0100, Thomas Müller wrote:
>>> I've just re-tested with runlevel 3.
>>> Not a real VGA console, but at least no Wayland or Gnome to interfere...
>>>
>>> `echo 0 > /sys/...` just blocks and no message whatsoever is visible in dmesg.
>>>
>>> I've executed `echo 0 > ...` in the background to keep my console functional and I can e.g. echo
>>> something to /dev/kmsg and it shows up, so reading/updating the log buffer appears to be working
>>> just fine.
>>
>> Damn.. Thanks for trying. I'll see if I can come up with something, but
>> I'm out of idea for now :/
>>
> Any new ideas so far?
> 
> For reference:
> I've just tested a vanilla 5.0.5 with localmodconfig (attached)... same behavior :(
> 
> 
> Best regards
> Thomas
> 

      reply	other threads:[~2019-04-12  5:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-14 15:17 Thomas Müller
2019-03-15  9:09 ` Peter Zijlstra
2019-03-15 11:41   ` Thomas Müller
2019-03-15 12:15     ` Peter Zijlstra
2019-03-15 20:21       ` Thomas Müller
2019-03-18 11:57         ` Peter Zijlstra
2019-03-29  9:22           ` Thomas Müller
2019-04-12  5:30             ` Thomas Müller [this message]

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=9a345d3c-c17c-95b2-dcbe-af72dee42a1a@mathtm.de \
    --to=thomas@mathtm.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.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