From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Philipp <philipp.buechel-EOsNSARiLbg@public.gmane.org>
Cc: sergiomb-hHo3WeeoaswVhHzd4jOs4w@public.gmane.org,
ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Hang on booting 2.6.3 at "Edge set to Level Trigger"
Date: 19 Mar 2004 12:39:52 -0500 [thread overview]
Message-ID: <1079717992.7274.23.camel@dhcppc4> (raw)
In-Reply-To: <200403191532.53941.philipp.buechel-EOsNSARiLbg@public.gmane.org>
On Fri, 2004-03-19 at 09:32, Philipp wrote:
>
> Am Freitag, 19. März 2004 10:46 schrieb Sérgio "M. Basto":
> > easy one, disable SMP and APIC in kernel configuration or boot with
> > something like this: noloapic
>
> Unfortunately, booting with noapic or noloapic takes no effect. dmesg always
> shows something like
>
> Local APIC disabled by BIOS -- reenabling.
> Found and enabled local APIC!
In 2.6.3, "nolapic" should be effective at disabling detect_init_APIC()
which is doing this. Check that there has not been some modification to
arch/i386/kernel/apic.c
> And if I boot with "noapic acpi=on" or "noloapic acpi=on" the boot process
> hangs on the "Edge set to Level Trigger"-Point.
>
> I guess I have to recompile the kernel with APIC disabled, right?
I guess so.
CONFIG_X86_LOCAL_APIC=n
-Len
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
prev parent reply other threads:[~2004-03-19 17:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 17:45 Hang on booting 2.6.3 at "Edge set to Level Trigger" Philipp
[not found] ` <200403181845.46394.philipp.buechel-EOsNSARiLbg@public.gmane.org>
2004-03-19 9:46 ` Sérgio M. Basto
[not found] ` <1079689606.5242.11.camel-DSl92WGJowabUe/Hp89tnA@public.gmane.org>
2004-03-19 14:32 ` Philipp
2004-03-19 15:15 ` Sergey Vlasov
[not found] ` <20040319181525.3bb8ec96.vsu-u2l5PoMzF/Uox3rIn2DAYQ@public.gmane.org>
2004-03-19 16:58 ` Philipp
[not found] ` <200403191532.53941.philipp.buechel-EOsNSARiLbg@public.gmane.org>
2004-03-19 17:39 ` 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=1079717992.7274.23.camel@dhcppc4 \
--to=len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=philipp.buechel-EOsNSARiLbg@public.gmane.org \
--cc=sergiomb-hHo3WeeoaswVhHzd4jOs4w@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