public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: "Sérgio Monteiro Basto"
	<sergiomb-hHo3WeeoaswVhHzd4jOs4w@public.gmane.org>
Cc: Shaohua Li <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	ACPI Developers
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [PATCH] resend Andrew de Quincey patch, that resolve hangs problems
Date: 21 Nov 2003 22:06:18 -0500	[thread overview]
Message-ID: <1069470377.2880.27.camel@dhcppc4> (raw)
In-Reply-To: <1068599493.2115.34.camel-4/PLUo9XfK/yXfm4dIG/yWZHpeb/A1Y/@public.gmane.org>

On Tue, 2003-11-11 at 20:11, Sérgio Monteiro Basto wrote:
> Windows run with APIC mode (at least is what windows says) and in linux
> we must disable APIC in kernel.

Does Windows have ACPI enabled?  (Device Manager will show ACPI devices,
power button and sleep button will work gracefully).  Does winmsd show
that windows is running in IOAPIC mode?  see this bug report for example
screen shots of what you're looking for:

http://bugzilla.kernel.org/show_bug.cgi?id=1164

> > If Windows can run a box in IO-APIC mode, then Linux should be able to
> > do the same.
> > 
> > I hesitate to integrate Andrew's automatic pic-fallback workaround into
> > the baseline kernel because I'm concerned that it will function
> > perfectly.  If we drop into PIC mode automatically, we may not realize
> > that we have a significant Linux-specific problem that we might be able
> > to solve.
> 
> But we have many reports, for VIA or athlon boards, that resolves the
> problems and we have many problem that wasnt yet resolved.
> In my case, the laptop has 2 years and it is history, so I am not worry
> about what is the real problem.
> Conclusion if you put debug information when drop into pic mode, for me
> it better. 

The system in the bug report above has a totally screwed up _PRT, and a
broken SCI OVER_RIDE entry in the MADT, yet XP still runs with ACPI
enabled and working, with IOAPIC enabled, and the devices with the
screwed up _PRT entries are working!

PIC-fallback will not get us there.  When we detect a bad _PRT, I think
we need to drop all the way down to pci=noacpi -- automatically.

This would cover the older machines with IOAPIC that is configured
properly with MPS -- and still allow them to run ACPI.  The newer
machines with IOAPIC and no MPS will need ACPI to get into APIC mode,
and if XP can do it, then Linux should be able to figure out how to do
it too.

So tell me, does booting with "pci=noacpi" allow your system to boot
with correct interrupts in IOAPIC mode, and with ACPI enabled?

thanks,
-Len




-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/

      parent reply	other threads:[~2003-11-22  3:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <571ACEFD467F7749BC50E0A98C17CDD8E84DC4@pdsmsx403.ccr.corp.intel.com>
     [not found] ` <571ACEFD467F7749BC50E0A98C17CDD8E84DC4-4yWAQGcml64gGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2003-11-07  4:31   ` [Patch]fix EC GPE context error Sérgio Monteiro Basto
     [not found]     ` <1068179499.3555.26.camel-4/PLUo9XfK/yXfm4dIG/yWZHpeb/A1Y/@public.gmane.org>
2003-11-10 23:15       ` [PATCH] resend Andrew de Quincey patch, that resolve hangs problems Sérgio Monteiro Basto
     [not found]         ` <1068531948.2682.1076.camel@dhcppc4>
     [not found]           ` <1068531948.2682.1076.camel-D2Zvc0uNKG8@public.gmane.org>
2003-11-12  1:11             ` Sérgio Monteiro Basto
     [not found]               ` <1068599493.2115.34.camel-4/PLUo9XfK/yXfm4dIG/yWZHpeb/A1Y/@public.gmane.org>
2003-11-22  3:06                 ` Len Brown [this message]

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=1069470377.2880.27.camel@dhcppc4 \
    --to=len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=sergiomb-hHo3WeeoaswVhHzd4jOs4w@public.gmane.org \
    --cc=shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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