From: mikpe@csd.uu.se
To: 0@pervalidus.tk, linux-kernel@vger.kernel.org
Subject: Re: 2.4.20: CONFIG_X86_UP_APIC and CONFIG_X86_UP_IOAPIC won't allow me to connect with my ADSL
Date: Thu, 17 Apr 2003 12:36:07 +0200 (MEST) [thread overview]
Message-ID: <200304171036.h3HAa7nw024924@harpo.it.uu.se> (raw)
Wed, 16 Apr 2003 21:53:21 -0300 (BRT), 0@pervalidus.tk wrote:
>I just installed an ECS K7VTA3 5.0 and ADSL. I was using an
>ASUS A7S333 and cable modem.
>
>With a kernel compiled with CONFIG_X86_UP_APIC and
>CONFIG_X86_UP_IOAPIC adsl-start will timeout. adsl-connect also
>fails.
Any APIC or interrupt-related errors in the kernel log?
>With a kernel compiled without CONFIG_X86_UP_APIC and
>CONFIG_X86_UP_IOAPIC I can succesfully establish a connection.
...
>My APIC enabled dmesg is available at
>http://www.fredlwm.hpg.com.br/dmesg-2.4.20-APIC
Nothing suspicious in this one.
First thing to try:
Keep UP_APIC enabled but disable UP_IOAPIC.
If this doesn't help:
Apply the patch below, which fixes a known problem on some mainboards.
If the patch doesn't help:
Accept that your mainboard doesn't work with APIC (local or I/O) enabled.
/Mikael
--- linux-2.4.21-pre7/arch/i386/kernel/apic.c.~1~ 2003-04-05 12:35:30.000000000 +0200
+++ linux-2.4.21-pre7/arch/i386/kernel/apic.c 2003-04-05 13:10:51.000000000 +0200
@@ -649,7 +649,6 @@
}
set_bit(X86_FEATURE_APIC, &boot_cpu_data.x86_capability);
mp_lapic_addr = APIC_DEFAULT_PHYS_BASE;
- boot_cpu_physical_apicid = 0;
if (nmi_watchdog != NMI_NONE)
nmi_watchdog = NMI_LOCAL_APIC;
@@ -1169,8 +1168,7 @@
connect_bsp_APIC();
- phys_cpu_present_map = 1;
- apic_write_around(APIC_ID, boot_cpu_physical_apicid);
+ phys_cpu_present_map = 1 << boot_cpu_physical_apicid;
apic_pm_init2();
next reply other threads:[~2003-04-17 10:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-17 10:36 mikpe [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-18 9:54 mikpe
2003-04-17 0:53 Frédéric L. W. Meunier
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=200304171036.h3HAa7nw024924@harpo.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=0@pervalidus.tk \
--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®