From: Aaro Koskinen <aaro.koskinen@iki.fi>
To: Tom Li <tomli@tomli.me>
Cc: James Hogan <jhogan@kernel.org>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Huacai Chen <chenhc@lemote.com>,
Ralf Baechle <ralf@linux-mips.org>,
linux-mips@vger.kernel.org
Subject: Re: CS5536 Spurious Interrupt Problem on Loongson2
Date: Fri, 22 Feb 2019 21:43:43 +0200 [thread overview]
Message-ID: <20190222194343.GA26495@darkstar.musicnaut.iki.fi> (raw)
In-Reply-To: <20190222143710.GA8504@localhost.localdomain>
Hi,
On Fri, Feb 22, 2019 at 10:37:11PM +0800, Tom Li wrote:
> Continue replying the original thread is off-topic and
> difficult to follow, so here I start a new thread for this problem.
The proper thread is here:
https://lore.kernel.org/linux-mips/20190106124607.GK27785@darkstar.musicnaut.iki.fi/#r
> Therefore, I'm suspicious that this problem is related to a specific firmware/
> hardware revision, or a probabilistic issue. PMON/EC version may be the first
> thing we need to confirm.
>
> My system is,
>
> $ cat /proc/cmdline
> PMON_VER=LM8089-1.4.9a EC_VER=PQ1D28 machtype=lemote-yeeloong-2f-8.9inches
Mini-PC does not have any EC. PMON is:
Version: PMON2000 2.1 (Bonito) #121: Mon Jan 5 14:19:11 CST 2009.
But firmware upgrade is not an option for me.
> Interrupts have no problem at all.
You should check "/proc/irq/14/spurious". Anyway, it well may be that some
machines work fine.
A.
next prev parent reply other threads:[~2019-02-22 19:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 14:37 CS5536 Spurious Interrupt Problem on Loongson2 Tom Li
2019-02-22 19:43 ` Aaro Koskinen [this message]
2019-02-22 20:22 Alexandre Oliva
2019-02-23 1:56 ` Tom Li
2019-02-23 6:08 ` Jiaxun Yang
2019-02-23 15:30 ` Aaro Koskinen
2019-02-24 4:55 ` Alexandre Oliva
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=20190222194343.GA26495@darkstar.musicnaut.iki.fi \
--to=aaro.koskinen@iki.fi \
--cc=chenhc@lemote.com \
--cc=jhogan@kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-mips@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=tomli@tomli.me \
/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).