From: Alexandre Oliva <lxoliva@fsfla.org>
To: Tom Li <tomli@tomli.me>
Cc: Aaro Koskinen <aaro.koskinen@iki.fi>,
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 17:22:15 -0300 [thread overview]
Message-ID: <ora7in8tfs.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: Tom Li's message of "Fri\, 22 Feb 2019 22\:37\:11 +0800"
On Feb 22, 2019, Tom Li <tomli@tomli.me> wrote:
> I meant the already-identified and fixed reboot/shutdown problem, not the
> CS3356 spurious interrupt problem.
Aha.
> 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.
I have had occasional IRQ 14 issues over the years, but they were not
common, and they'd hit while using the system. After 4.20, they seem to
deterministically hit very early during boot-up.
> Therefore, I'm suspicious that this problem is related to a specific firmware/
> hardware revision
That's possible. Another possibility is that it is related with the
hard drive models connected to the controller. What suggested this to
me was the quirks code in the old, non-libata driver, that recognized
specific hard drive models, one of which matches the drive I have on my
yeeloong.
$ hdparm -i /dev/sda
[...]
Model=FUJITSU MHZ2160BH G2, FwRev=00000009, SerialNo=[...]
> $ cat /proc/cmdline
I don't have the PMON or EC versions in /proc/cmdline. machtype is the same.
'vers' in the pmon text prompt responds: PMON2000 2.1 (Bonito) #291
> $ cat /proc/interrupts
Differences (running 4.19) are IRQ 5, and USBs on 11 (XT) and 39 (bonito).
> (P.S: Interrupt 10, sci, is the platform driver I'm developing, just ignore it)
Err, should I be worried that I have that too?
--
Alexandre Oliva, freedom fighter https://FSFLA.org/blogs/lxo
Be the change, be Free! FSF Latin America board member
GNU Toolchain Engineer Free Software Evangelist
Hay que enGNUrecerse, pero sin perder la terGNUra jamás-GNUChe
next reply other threads:[~2019-02-22 20:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 20:22 Alexandre Oliva [this message]
2019-02-23 1:56 ` CS5536 Spurious Interrupt Problem on Loongson2 Tom Li
2019-02-23 6:08 ` Jiaxun Yang
2019-02-23 15:30 ` Aaro Koskinen
2019-02-24 4:55 ` Alexandre Oliva
-- strict thread matches above, loose matches on Subject: below --
2019-02-22 14:37 Tom Li
2019-02-22 19:43 ` Aaro Koskinen
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=ora7in8tfs.fsf@lxoliva.fsfla.org \
--to=lxoliva@fsfla.org \
--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 \
--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).