Date: Mon, 9 Jun 2014 13:36:25 -0400 From: John Baldwin <jhb@freebsd.org> To: Edward Tomasz =?utf-8?q?Napiera=C5=82a?= <trasz@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: "CPU0: local APIC error 0x40" Message-ID: <201406091336.25294.jhb@freebsd.org> In-Reply-To: <20140607084739.GB1086@brick.home> References: <D0664455-A1D7-4886-A32F-B004CAD92630@FreeBSD.org> <201406041036.37413.jhb@freebsd.org> <20140607084739.GB1086@brick.home>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday, June 07, 2014 4:47:39 am Edward Tomasz Napiera=C5=82a wrote:
> On 0604T1036, John Baldwin wrote:
> > On Monday, June 02, 2014 5:32:13 pm Edward Tomasz Napiera=C5=82a wrote:
> > > Some machines, including ThinkPad T61, emit the following error messa=
ge
> > > early during boot:
> > >=20
> > > CPU0: local APIC error 0x40
> > >=20
> > > The message itself doesn't seem to be much of a problem. However,
> > > every once in a while booting hangs just before that line. I've trac=
ked
> > > that down to call to AcpiHwWritePort() at
> > > sys/contrib/dev/acpica/components/hardware/hwacpi.c:117:
> > >=20
> > > switch (Mode)
> > > {
> > > case ACPI_SYS_MODE_ACPI:
> > >=20
> > > /* BIOS should have disabled ALL fixed and GP events */
> > >=20
> > > Status =3D AcpiHwWritePort (AcpiGbl_FADT.SmiCommand,
> > > (UINT32) AcpiGbl_FADT.AcpiEnable, 8);
> > >=20
> > > Any idea what might be going on?
> >=20
> > This is probably triggering an SMI# to enter SMM mode where your BIOS d=
oes=20
> > God-knows-what but apparently triggers one of the local APIC local inte=
rrupts=20
> > while it is configured with an invalid vector (e.g. 0).
>=20
> Is there anything that can be done to fix it? (Note that fixing the
> suspend/resume seems to have also fixed the occasional hang on boot,
> but perhaps it's because I don't need to boot this thing so often now.)
Likely not. This is actually the magic command to tell the BIOS that the OS
is ACPI-aware and to ask the BIOS to enable ACPI support. It can do all so=
rts
of things and is completely outside of OS control while it runs. The local
APIC thing is logged when the OS gains control again, but it's harmless.
=2D-=20
John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201406091336.25294.jhb>