linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hauke Mehrtens <hauke@hauke-m.de>
To: James Hogan <james.hogan@imgtec.com>, Felix Fietkau <nbd@nbd.name>
Cc: linux-mips@linux-mips.org, ralf@linux-mips.org, john@phrozen.org
Subject: Re: [PATCH] MIPS: Lantiq: Fix cascaded IRQ setup
Date: Sun, 12 Feb 2017 00:50:48 +0100	[thread overview]
Message-ID: <073628a4-9c45-b3c3-6caa-c88bea138aa9@hauke-m.de> (raw)
In-Reply-To: <20170211231906.GI24226@jhogan-linux.le.imgtec.org>

On 02/12/2017 12:19 AM, James Hogan wrote:
> Hi Felix,
> 
> On Thu, Jan 19, 2017 at 12:28:22PM +0100, Felix Fietkau wrote:
>> With the IRQ stack changes integrated, the XRX200 devices started
>> emitting a constant stream of kernel messages like this:
>>
>> [  565.415310] Spurious IRQ: CAUSE=0x1100c300
>>
>> This appears to be caused by IP0 firing for some reason without being
>> handled. Fix this by setting up IP2-6 as a proper chained IRQ handler and
>> calling do_IRQ for all MIPS CPU interrupts.
>>
>> Cc: john@phrozen.org
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Felix Fietkau <nbd@nbd.name>
> 
> Is this still applicable after Matt's fix is applied?
> https://patchwork.linux-mips.org/patch/15110/

Hi,

I just tried it without Matt's and Felix's fix and I saw the problem,
then I applied Matt's fix and the problem was gone.

Hauke

  parent reply	other threads:[~2017-02-11 23:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-19 11:28 [PATCH] MIPS: Lantiq: Fix cascaded IRQ setup Felix Fietkau
2017-01-19 11:54 ` John Crispin
2017-02-11 23:19 ` James Hogan
2017-02-11 23:19   ` James Hogan
2017-02-11 23:50   ` Hauke Mehrtens [this message]
2017-02-12 11:05     ` Felix Fietkau
2017-02-13 11:12       ` James Hogan
2017-02-13 11:12         ` James Hogan

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=073628a4-9c45-b3c3-6caa-c88bea138aa9@hauke-m.de \
    --to=hauke@hauke-m.de \
    --cc=james.hogan@imgtec.com \
    --cc=john@phrozen.org \
    --cc=linux-mips@linux-mips.org \
    --cc=nbd@nbd.name \
    --cc=ralf@linux-mips.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;
as well as URLs for NNTP newsgroup(s).