Re: 2.4.20: CONFIG_X86_UP_APIC and CONFIG_X86_UP_IOAPIC won't allow me to connect with my ADSL

mikpe@csd.uu.se
Thu, 17 Apr 2003 12:36:07 +0200 (MEST)


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();

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/