From: John David Anglin <dave.anglin@bell.net>
To: Helge Deller <deller@gmx.de>,
linux-parisc@vger.kernel.org,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Sven Schnelle <svens@stackframe.org>,
Carlo Pisani <carlojpisani@gmail.com>
Subject: Re: [PATCH v3] parisc: Fix crash due alternative coding for NP iopdir_fdc bit
Date: Mon, 27 May 2019 15:41:44 -0400 [thread overview]
Message-ID: <a3f85e95-272d-86fc-916a-70928d5f07ef@bell.net> (raw)
In-Reply-To: <20190527192000.GA17551@ls3530.dellerweb.de>
On 2019-05-27 3:20 p.m., Helge Deller wrote:
> This fixes the HPMC crashes on a C240 and C36XX machines. For other
> machines we rely on the firmware to set the bit when needed.
>
> In case one finds HPMC issues, people could try to boot their machines
> with the "no-alternatives" kernel option to turn off any alternative
> patching.
Just wondering about soft fail versus hard fail. In lba_pci.c, we have soft fail by default:
#if defined(ENABLE_HARDFAIL)
WRITE_REG32(stat | HF_ENABLE, d->hba.base_addr + LBA_STAT_CTL);
#else
WRITE_REG32(stat & ~HF_ENABLE, d->hba.base_addr + LBA_STAT_CTL);
#endif
However, in sba_iommu.c, we crash on rope errors:
/*
** Make sure the box crashes on rope errors.
*/
WRITE_REG(HF_ENABLE, ioc_hpa + ROPE0_CTL + j);
I suspect Carlo's C3600 HPMC issues must be from rope issue. Should rope errors be soft
as well?
Dave
--
John David Anglin dave.anglin@bell.net
next prev parent reply other threads:[~2019-05-27 19:41 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 19:20 [PATCH v3] parisc: Fix crash due alternative coding for NP iopdir_fdc bit Helge Deller
2019-05-27 19:35 ` Carlo Pisani
2019-05-27 20:13 ` John David Anglin
2019-05-27 20:22 ` Sven Schnelle
2019-05-27 20:49 ` John David Anglin
2019-05-27 20:15 ` Sven Schnelle
2019-05-28 11:06 ` Sven Schnelle
2019-05-28 11:28 ` Rolf Eike Beer
2019-05-28 15:41 ` Sven Schnelle
2019-05-28 15:52 ` Helge Deller
[not found] ` <e81b7ae4-3126-5fda-58e4-4a83bd4fcfcf@bell.net>
2019-05-28 15:11 ` Helge Deller
2019-05-28 15:38 ` Sven Schnelle
2019-05-28 17:06 ` John David Anglin
2019-05-28 17:24 ` Rolf Eike Beer
2019-05-28 17:39 ` Sven Schnelle
2019-05-28 18:40 ` John David Anglin
2019-05-29 14:15 ` Helge Deller
2019-05-29 17:01 ` John David Anglin
2019-05-30 19:55 ` Sven Schnelle
2019-05-30 20:59 ` Sven Schnelle
2019-05-31 12:23 ` John David Anglin
2019-06-02 10:29 ` Carlo Pisani
2019-06-02 14:45 ` John David Anglin
2019-06-02 14:38 ` John David Anglin
2019-06-02 16:12 ` John David Anglin
2019-05-27 19:41 ` John David Anglin [this message]
2019-05-27 20:11 ` Helge Deller
2019-05-27 20:16 ` Carlo Pisani
2019-05-27 20:45 ` John David Anglin
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=a3f85e95-272d-86fc-916a-70928d5f07ef@bell.net \
--to=dave.anglin@bell.net \
--cc=James.Bottomley@hansenpartnership.com \
--cc=carlojpisani@gmail.com \
--cc=deller@gmx.de \
--cc=linux-parisc@vger.kernel.org \
--cc=svens@stackframe.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.