From: Tom Li <tomli@tomli.me>
To: Aaro Koskinen <aaro.koskinen@iki.fi>, 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: CS5536 Spurious Interrupt Problem on Loongson2
Date: Fri, 22 Feb 2019 22:37:11 +0800 [thread overview]
Message-ID: <20190222143710.GA8504@localhost.localdomain> (raw)
Hi all,
During the discussion of Loongson/Yeeloong driver mainlining, both
Alexandre Oliva and Aaro Koskinen reported the their Loongson machine
is being bombarded by spurious interrupt from CS5536 when using the
libata driver. Continue replying the original thread is off-topic and
difficult to follow, so here I start a new thread for this problem.
On Sun, Feb 17, 2019 at 01:59:26AM -0300, Alexandre Oliva wrote:
> Tom, why do you say bisecting this is impossible? I realize you wrote
> you did so for 24 hours non-stop, but... I'm curious as to what
> obstacles you ran into. It's such a reproducible problem for me that I
> can't see how bisecting it might be difficult.
>
> Or were by any chance you talking about the reboot/shutdown problem
> then?
I meant the already-identified and fixed reboot/shutdown problem, not the
CS3356 spurious interrupt problem.
To be honest, I don't understand why the libata driver can even be a problem
at all. To add some background information, I started using the libata driver
since 2014, and to this day, I NEVER encountered any problem with it. And not
only me, I had a personal project - a prebuilt kernel for Yeeloong laptops,
and at least three different users had tried it. In addition, Jiaxun Yang also
who did some independent work - none of these people have reported any problem
similar to this one.
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
$ cat /proc/interrupts
CPU0
1: 11 XT-PIC 1 i8042
2: 0 XT-PIC 2 cascade
8: 0 XT-PIC 8 rtc0
9: 0 XT-PIC 9 snd_cs5535audio
10: 0 XT-PIC 10 sci
12: 87 XT-PIC 12 i8042
14: 6418 XT-PIC 14 pata_cs5536
18: 0 MIPS 2 cascade
22: 0 MIPS 6 cascade
23: 148498 MIPS 7 timer
37: 296 bonito_irq eth0
ERR: 0
Interrupts have no problem at all.
(P.S: Interrupt 10, sci, is the platform driver I'm developing, just ignore it)
Thus, I don't see any CS5536 interrupt problem when using the libata driver.
My first question is, what are your EC/PMON versions? can you report back?
Thanks,
Tom Li
next reply other threads:[~2019-02-22 14:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 14:37 Tom Li [this message]
2019-02-22 19:43 ` CS5536 Spurious Interrupt Problem on Loongson2 Aaro Koskinen
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=20190222143710.GA8504@localhost.localdomain \
--to=tomli@tomli.me \
--cc=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 \
/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).