From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: In-Reply-To: From: =?UTF-8?Q?Rodrigo_G=2E_L=C3=B3pez?= Date: Fri, 19 Apr 2019 13:05:56 +0200 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary="000000000000f9c7760586e01adf" Subject: Re: [9fans] SMC SYS-5018A-FTN4 lapic weirdness (9front) Topicbox-Message-UUID: fbe857a0-ead9-11e9-9d60-3106f5b1d025 --000000000000f9c7760586e01adf Content-Type: text/plain; charset="UTF-8" Hi. I get the exact same error every time I (in|de)crease the backlight brightness in the x220. On Thu, Apr 18, 2019, 3:49 AM Lyndon Nerenberg wrote: > 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 > > --000000000000f9c7760586e01adf Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi.

I get the exact same error every time I (in|de)crease the backlight brig= htness in the x220.

On Thu, Apr 18, 2019, 3:4= 9 AM Lyndon Nerenberg <lyndon@ortha= nc.ca> wrote:
I have a stack= of Supermicro SYS-5018A-FTN4 servers upon which=C2=A0 I'm trying to spin up 9front.

For the most part they work, but one annoyance is the *endless* stream of
=C2=A0 cpu0: lapicerror: 0x00000080

messages the kernel prints out.=C2=A0 Sometimes these originate from cpu1 a= s well.
The hardware has eight CPU cores.=C2=A0 I don't think I've seen any= thing 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.=C2=A0 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 s= omebody
can use that I'll figure something out.

--lyndon

--000000000000f9c7760586e01adf--