From: Joshua Kinard <kumba@gentoo.org>
To: Linux/MIPS <linux-mips@linux-mips.org>
Subject: Random IP27 Tests on 4.3.0-rc3
Date: Sun, 4 Oct 2015 01:06:03 -0400 [thread overview]
Message-ID: <5610B3BB.6090406@gentoo.org> (raw)
Has anyone else tested the below various kernel modes on IP27 hardware? Same
observations?
CONFIG_SGI_SN_M_MODE=y
- Boots, works, until the hardlock bug bites.
CONFIG_SGI_SN_N_MODE=y
- Appears to boot, but crashes early. This message is left on the MSC console:
2A 000: *** TLB Refill Exception on node 0
2A 000: *** EPC: 0xa80000000001d890 (0xa80000000001d890)
2A 000: *** Press ENTER to continue.
CONFIG_MAPPED_KERNEL=y
CONFIG_REPLICATE_KTEXT=y
- Does not boot, give this classic (and annoying) error:
Cannot load bootp():.
Text start 0x1c000, size 0x1965a70 doesn't fit in a FreeMemory area.
Unable to execute bootp():: not enough space
CONFIG_REPLICATE_EXHANDLERS=y
- Appears to boot, but crashes early. MSC error:
2A 000: *** TLB Refill Exception on node 0
2A 000: *** EPC: 0x0 (0x0)
2A 000: *** Press ENTER to continue.
CONFIG_NUMA=y is true for all tests above, because that seemingly staves off
the hardlock bug a little longer....though mdraid seems to really exacerbate
the thing now.
--J
reply other threads:[~2015-10-04 5:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5610B3BB.6090406@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.