NForce2 + linux 2.6.3-rc2 + acpi,apic patches

From: Jesse Allen (the3dfxdude_at_hotmail.com)
Date: 02/11/04

  • Next message: Mike Bell: "Re: devfs vs udev, thoughts from a devfs user" 
    Date:	Tue, 10 Feb 2004 18:29:12 -0700
To: linux-kernel@vger.kernel.org

    Hi,

    I have noticed two patches in Andrew Morton's tree, 2.6.3-rc1-mm1, that may be
    helpful for me and other nforce 2 users. The two patches are
    nforce-irq-setup-fix.patch
    8259-timer-ack-fix.patch

    I have compiled 2.6.3-rc2 with those two patches included. Here is
    /proc/interrupts after reboot:
      0: 2347129 local-APIC-edge timer
      1: 6604 IO-APIC-edge i8042
      2: 0 XT-PIC cascade
      4: 4458 IO-APIC-edge serial
      7: 0 IO-APIC-edge parport0
      8: 1 IO-APIC-edge rtc
      9: 0 IO-APIC-level acpi
     14: 4456 IO-APIC-edge ide0
     15: 17 IO-APIC-edge ide1
     20: 239364 IO-APIC-level eth0, ohci_hcd
     21: 0 IO-APIC-level ehci_hcd, NVidia nForce2
     22: 0 IO-APIC-level ohci_hcd

    Timer is now local-APIC-edge instead of XT-PIC. Seems to be better now. I've
    checked to see if the problem with large clock time gain returned. So far, it
    seems to be perfectly synced with my watch.

    I don't know if local-APIC or IO-APIC are really any different with the timer.
    If there is something I should know about the difference, someone please let
    me know =)

    Also, here's a snippet from dmesg:
    enabled ExtINT on CPU#0
    ESR value before enabling vector: 00000000
    ESR value after enabling vector: 00000000
    ENABLING IO-APIC IRQs
    init IO_APIC IRQs
     IO-APIC (apicid-pin) 2-0, 2-16, 2-17, 2-18, 2-19, 2-20, 2-21, 2-22, 2-23 not connected.
    ..TIMER: vector=0x31 pin1=2 pin2=-1
    ..MP-BIOS bug: 8254 timer not connected to IO-APIC
    ...trying to set up timer (IRQ0) through the 8259A ... failed.
    ...trying to set up timer as Virtual Wire IRQ... works.
    Using local APIC timer interrupts.
    calibrating APIC timer ...
    ..... CPU clock speed is 1912.0861 MHz.
    ..... host bus clock speed is 332.0671 MHz.

    Thanks Ross and Maciej for the patches!

    Jesse
    -
    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/

  • Next message: Mike Bell: "Re: devfs vs udev, thoughts from a devfs user"

    Relevant Pages

    • Re: [patch 2.6.25-rc2-git 1/2] atmel_tc library
      ... incorporate patches to configure the relevant platform devices. ... AVR32 currently uses one of the TC blocks as a system timer. ...
      (Linux-Kernel)
    • [ANNOUNCE] ktimers subsystem
      ... ktimers seperate the "timer API" from the "timeout API". ... patches / projects related to it. ... The efforts to integrate the High Resolution Timer patches ...
      (Linux-Kernel)
    • [PATCH 0/9] high precision timer
      ... patches only to the list. ... - I renamed it to ptimer, which stands now for precise timer (or even ... shorter for high precision timer). ... infrastructure for higher resolution, posix timer/itimer still provide ...
      (Linux-Kernel)
    • Re: IO-APIC on nforce2
      ... or patched io_apic.c and process.c and using kernel arg "idle=C1halt"? ... 12: 13499 IO-APIC-edge PS/2 Mouse ... with my new timer setup ... number of MP IRQ sources: ...
      (Linux-Kernel)
    • Re: IO-APIC on nforce2
      ... Ross I get this output on system-log: ... 8254 timer not connected to IO-APIC INTIN2 ... 12: 2054 IO-APIC-edge i8042 ... IRQ redirection table: ...
      (Linux-Kernel)