Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Mon, 18 Mar 2019 12:57:28 +0100
From:   Peter Zijlstra <peterz@infradead.org>
To:     Thomas =?iso-8859-1?Q?M=FCller?= <thomas@mathtm.de>
Cc:     linux-kernel@vger.kernel.org
Subject: Re: disabling secondary CPU hangs / system fails to suspend with
 kernel 4.19+
Message-ID: <20190318115728.GP6058@hirez.programming.kicks-ass.net>
References: <5c48095e-028a-404f-aaa1-964f83c83817@mathtm.de>
 <20190315090950.GT5996@hirez.programming.kicks-ass.net>
 <cbaafd35-a17d-8331-4cef-281a562b91b5@mathtm.de>
 <20190315121541.GD6058@hirez.programming.kicks-ass.net>
 <2b1c85d3-d94b-1593-e30a-a32d97043579@mathtm.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <2b1c85d3-d94b-1593-e30a-a32d97043579@mathtm.de>
User-Agent: Mutt/1.10.1 (2018-07-13)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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 :/