lkml.org 
[lkml]   [2004]   [Apr]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: 8139too not working in 2.6
    From
    Date
    "Mirko Caserta" <mirko@mcaserta.com> writes:

    > Anyway, it doesn't look like an irq problem to me. It looks more like
    > a wrong detection of the TX triggering level in the driver.

    In interrupts-2.6.6-rc2-mm2-broken-out,

    CPU0 CPU1
    0: 103394 48 IO-APIC-edge timer
    1: 157 0 IO-APIC-edge i8042
    5: 2 1 IO-APIC-edge eth0
    ^^^^^^^^^^^^-- wrong
    8: 2 0 IO-APIC-edge rtc
    9: 0 0 IO-APIC-level acpi
    11: 3 1 IO-APIC-edge i91u
    12: 87 0 IO-APIC-edge i8042
    14: 1068 2 IO-APIC-edge ide0
    15: 953 1 IO-APIC-edge ide1

    The above must be IO-APIC-level.
    And the following is interesting one.

    ACPI: ACPI tables contain no PCI IRQ routing entries
    PCI: Invalid ACPI-PCI IRQ routing table
    PCI: Probing PCI hardware
    PCI: Using IRQ router default [1106/3091] at 0000:00:00.0
    PCI BIOS passed nonexistent PCI bus 0!
    PCI BIOS passed nonexistent PCI bus 0!
    PCI BIOS passed nonexistent PCI bus 0!
    PCI BIOS passed nonexistent PCI bus 0!
    PCI BIOS passed nonexistent PCI bus 0!
    PCI BIOS passed nonexistent PCI bus 1!
    PCI BIOS passed nonexistent PCI bus 0!

    Um.. can you try "pci=noacpi" or "acpi=off"?
    --
    OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
    -
    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/

    \
     
     \ /
      Last update: 2005-03-22 14:02    [W:0.020 / U:44.104 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site