From: Joshua Kinard <kumba@gentoo.org>
To: Linux MIPS List <linux-mips@linux-mips.org>
Subject: IP27: Random hard locks after ~16hrs uptime
Date: Sat, 07 Feb 2015 21:58:29 -0500 [thread overview]
Message-ID: <54D6D0D5.8020704@gentoo.org> (raw)
I've had my Onyx2 running quite a bit lately doing compile runs, and it seems
that after about ~16 hours, there's a random possibility that the machine just
completely stops. No errors printed anywhere, serial becomes completely
unresponsive. I have to issue a 'rst' from the MSC to bring it back up again.
It's currently got dual IP31 R14000 node boards (500MHz), and for the most
part, runs great (I'll regret the electric bill later...). Clearly a bug,
though, but I am not sure where to start debugging on this platform to find
this bug, since I can't trigger it manually. Even tried an NMI interrupt,
since this machine has an NMI handler in the kernel, but all that does is reset
the machine.
Already ran an extensive memory test from the PROM and had no issues with that.
Haven't tried running any of the more thorough hardware tests from IRIX, though.
Ideas?
--
Joshua Kinard
Gentoo/MIPS
kumba@gentoo.org
4096R/D25D95E3 2011-03-28
"The past tempts us, the present confuses us, the future frightens us. And our
lives slip away, moment by moment, lost in that vast, terrible in-between."
--Emperor Turhan, Centauri Republic
next reply other threads:[~2015-02-08 2:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-08 2:58 Joshua Kinard [this message]
2015-02-08 12:06 ` IP27: Random hard locks after ~16hrs uptime Maciej W. Rozycki
2015-02-09 0:53 ` Joshua Kinard
2015-02-09 8:50 ` Joshua Kinard
2015-02-09 14:33 ` IP27: BUG() in mm/vmscan.c, isolate_lru_pages [was: Random hard locks after ~16hrs uptime] Joshua Kinard
2015-02-21 22:26 ` IP27: BUG() in mm/vmscan.c, isolate_lru_pages Joshua Kinard
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=54D6D0D5.8020704@gentoo.org \
--to=kumba@gentoo.org \
--cc=linux-mips@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 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.