From: john stultz <johnstul@us.ibm.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@digeo.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>, James <jamesclv@us.ibm.com>
Subject: Re: [PATCH] linux-2.5.69_clear-smi-fix_A1
Date: 12 May 2003 18:03:38 -0700 [thread overview]
Message-ID: <1052787818.4171.29.camel@w-jstultz2.beaverton.ibm.com> (raw)
In-Reply-To: <3EC04261.6020206@us.ibm.com>
On Mon, 2003-05-12 at 17:54, Dave Hansen wrote:
> john stultz wrote:
> > I've been having problems with ACPI on a box here in our lab. Some of
> > our more recent hardware requires that SMIs are routed through the
> > IOAPIC, thus when we clear_IO_APIC() at boot time, we clear the BIOS
> > initialized SMI pin. This basically clobbers the SMI so we can then
> > never make the transition into ACPI mode.
> >
> > This patch simply reads the apic entry in clear_IO_APIC to make sure the
> > delivery_mode isn't dest_SMI. If it is, we leave the apic entry alone
> > and return.
> >
> > With this patch, the box boots and SMIs function properly.
>
> So, without the patch, what happens? Does the thing just completely
> freeze when it tries to turn ACPI on? Does the machine _require_ that
> you use ACPI?
When trying to boot w/ ACPI the transition fails and the box hobbles
along to different degrees. Normally the interrupt routing is bad and a
scsi or network card fails to init.
Without ACPI the system boots fine. SMIs are still clobbered, but
they're less critical.
But really, ACPI (and SMIs) should "just work". ;)
thanks
-john
next prev parent reply other threads:[~2003-05-13 0:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 0:30 john stultz
2003-05-13 0:54 ` Dave Hansen
2003-05-13 1:03 ` john stultz [this message]
2003-05-13 14:03 ` Dave Jones
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=1052787818.4171.29.camel@w-jstultz2.beaverton.ibm.com \
--to=johnstul@us.ibm.com \
--cc=akpm@digeo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=haveblue@us.ibm.com \
--cc=jamesclv@us.ibm.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®