From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: linux-parisc@vger.kernel.org
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
John David Anglin <dave.anglin@bell.net>
Subject: Re: [PATCH] parisc: Suspend lockup detectors before system halt
Date: Tue, 25 Jul 2017 22:01:34 +0200 [thread overview]
Message-ID: <2651830.be6NMSIgim@daneel.sf-tec.de> (raw)
In-Reply-To: <d015022e-2ecd-889f-7466-348fa2c230a6@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 917 bytes --]
Helge Deller wrote:
> On 25.07.2017 21:47, Rolf Eike Beer wrote:
> > Helge Deller wrote:
> >> Some machines can't power off the machine, so disable the lockup
> >> detectors
> >> to avoid this watchdog BUG to show up every few seconds:
> >> watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd-shutdow:1]
> >
> > I don't think HPPA is the only architecture that has this problem,
>
> Maybe.
> I haven't heard of others yet, probably because most other architectures
> do power off themselves, so they won't see this problem.
>
> > so isn't there a generic solution? Or: is it time to add one?
>
> Sure, you are welcome to test, post and discuss patches upstream if you
> like. It's not a very critical issue, so I can wait with pushing my patch.
I wont be able to do anything like that this week (maybe longer), so please go
ahead with your patch to get rid of the annoying warning. Cleanups later.
Eike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2017-07-25 20:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 19:41 [PATCH] parisc: Suspend lockup detectors before system halt Helge Deller
2017-07-25 19:47 ` Rolf Eike Beer
2017-07-25 19:55 ` Helge Deller
2017-07-25 20:00 ` Helge Deller
2017-07-25 20:01 ` Rolf Eike Beer [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=2651830.be6NMSIgim@daneel.sf-tec.de \
--to=eike-kernel@sf-tec.de \
--cc=James.Bottomley@hansenpartnership.com \
--cc=dave.anglin@bell.net \
--cc=linux-parisc@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox