From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: 9fans@9fans.net
Subject: [9fans] SMC SYS-5018A-FTN4 lapic weirdness (9front)
Date: Wed, 17 Apr 2019 18:47:35 -0700 [thread overview]
Message-ID: <fd2fd1ab411573f9@orthanc.ca> (raw)
I have a stack of Supermicro SYS-5018A-FTN4 servers upon which I'm trying to
spin up 9front.
For the most part they work, but one annoyance is the *endless* stream of
cpu0: lapicerror: 0x00000080
messages the kernel prints out. Sometimes these originate from cpu1 as well.
The hardware has eight CPU cores. I don't think I've seen anything from
cpu>1, but in the blizzard of messages, who knows.
I poked a wee bit inside the kernel source, but I don't have time right now
to chase this. The hardware runs fine, other than refusing to reboot, which
I put down to the usual BIOS ACPI table stupidity.
For the time being I'm going to put a filter on the kprints, but I'm curious
if this sounds familiar to anyone.
Note this happens with both the 32- and 64-bit kernels.
I don't have a quick way to attach sysinfo(1) to this message, but if somebody
can use that I'll figure something out.
--lyndon
next reply other threads:[~2019-04-18 1:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 1:47 Lyndon Nerenberg [this message]
2019-04-19 11:05 ` Rodrigo G. López
2019-04-18 2:06 cinap_lenrek
2019-04-18 3:10 ` Lyndon Nerenberg
2019-04-18 4:02 ` Lyndon Nerenberg
2019-04-18 2:08 cinap_lenrek
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=fd2fd1ab411573f9@orthanc.ca \
--to=lyndon@orthanc.ca \
--cc=9fans@9fans.net \
/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).