From: Sergio Monteiro Basto <sergio-qOf5bGQp09kptuEoxK/DLR2eb7JE58TQ@public.gmane.org>
To: Daniele Bertin <daniele.bertin-IWqWACnzNjyonA0d6jMUrA@public.gmane.org>
Cc: acpi-devel
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [ACPI-bugzilla] Boot hang in ACPI mode with and w/o "nolapic" - compaq 2156EA
Date: Sat, 29 Jan 2005 15:22:30 +0000 [thread overview]
Message-ID: <1107012150.1672.12.camel@bastov> (raw)
In-Reply-To: <1106178197.4354.8.camel@localhost>
Yap, after many work, we suspect that the problem is that we have one
local apic on this computers but is not used (even on Windows) because
we don't need it, and in very low level isn't programed either.
So if BIOS reports that local apic is disable, we don't try enabled it
anymore, this feature has enter in kernel 2.6.9.
Conclusion if you use a kernel >= 2.6.9 , the local apic will not be
enabled and computer won't hang anymore.
BTW: the Mailing List for us to write is acpi-devel.
thanks,
On Thu, 2005-01-20 at 00:43 +0100, Daniele Bertin wrote:
> At boot with noapic, ACPI=on my Compaq Presario 2156EA hang safter the
> syslog messages (seen from failsafe boot on the screen):
> ...
> spurious 8259A interupt: IRQ7
> ACPI: IRQ9 SCI: Level Trigger
>
> If I use nolapic the PC hangs even before during the message
> "Calibrating delay loop..."
>
> It works with ACPI=ht but in this case I have no ACPI in my laptop(!).
>
> After searches and trials it seems that the problem is related to the
> use of nolapic with ACPI, see bug 1269 at
> http://bugme.osdl.org/show_bug.cgi?id=1269
>
> So what. What to do to put in practice the solution? I have not seen
> that bug included in the last ACPI versions. I'm a goodwill person and
> even if found of linux I'm only a user for writing, internet and music
> and never patched or compiled a kernel, so a simple explaination will be
> appreciated.
>
> Distribution: Mandrake Linux 10.1. Kernel 2.6.8.1-12mdk. BIOS KAM 1.42.
> ACPI 20040326
>
> Thanks for any help
>
> Daniele
>
> A summary of what I have tried (only the part significant to the present
> debugging):
>
> 1) Use of APIC. PC hangs. After that always noapic in kernel parameter
> in lilo.conf
> 2) Use of nolapic: hang at "Calibrating " as said above. After that use
> of nolapic is avoided
> 3) Use of combination of parameters in append of lilo: pci=noacpi,
> acpi=noirq
> 4) Use of a corrected DSDT table. dump of my PC table with pmtools,
> decompile and compile with iasl compiler after fixing an error related
> to *SYN0105 symbol which was not alphanmeric. The table is found in the
> initrd but the behaviour is the same as with the original DSDT table.
>
>
--
Sérgio M.B.
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
parent reply other threads:[~2005-01-29 15:22 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1106178197.4354.8.camel@localhost>]
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=1107012150.1672.12.camel@bastov \
--to=sergio-qof5bgqp09kptueoxk/dlr2eb7je58tq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=daniele.bertin-IWqWACnzNjyonA0d6jMUrA@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