From: Peter Zijlstra <peterz@infradead.org>
To: "Thomas Müller" <thomas@mathtm.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: disabling secondary CPU hangs / system fails to suspend with kernel 4.19+
Date: Fri, 15 Mar 2019 13:15:41 +0100 [thread overview]
Message-ID: <20190315121541.GD6058@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <cbaafd35-a17d-8331-4cef-281a562b91b5@mathtm.de>
On Fri, Mar 15, 2019 at 12:41:00PM +0100, Thomas Müller wrote:
> > What .config do you have?
> The one packaged by Fedora. I've attached the one for 4.20.15 as reference.
Thanks, I'll have a poke, see what, if anything, is different from the
kernels I ran.
> > And what, if anything do you see on the
> > console when it goes funny?
> Nothing unfortunately.
> When trying to suspend the display immediately goes blank, the system becomes unresponsive and the
> status LED within the power button start flashing rapidly (just like it does when the power cord is
> attached).
>
>
> > I think you wrote that hot-un-plug never completes? Is there anything in
> > dmesg when it's stuck in:
> >
> > echo 0 > /sys/devices/system/cpu/cpu1/online
> >
> > ?
> I've just tried that again and the system immediately froze.
Hmm, I tought you said the system remained semi usable, just that reboot
stopped working thereafter and it needed a power cycle.
> `journalctl -f` was running in a second window but it had no chance to output anything... :/
Ah, you're using a GUI!
Stop doing that ;-)
See if you can use the VGA console; not a FB console or a DRM console,
but the real ancient, proper text mode, VGA console.
Now, don't ask me how to do that, because I don't know, I've been
running on pure serial console output for the past 10 years or so, heck
I don't even have systemd.
And you might have to do something like: dmesg -n8, to get the console
to print the kernel messages or something.
next prev parent reply other threads:[~2019-03-15 12:15 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 [this message]
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
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=20190315121541.GD6058@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas@mathtm.de \
/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