[lkml]   [2006]   [Feb]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] tg3: netif_carrier_off runs too early; could still be queued when init fails
    Hash: SHA1

    Michael Chan wrote:
    > On Tue, 2006-02-21 at 17:41 -0500, Jeff Mahoney wrote:
    >> dmesg after modprobe tg3:
    >> tg3.c:v3.49 (Feb 2, 2006)
    >> ACPI: PCI Interrupt 0000:0a:02.0[A] -> GSI 24 (level, low) -> IRQ 201
    >> Uhhuh. NMI received for unknown reason 21 on CPU 0.
    >> Dazed and confused, but trying to continue
    >> Do you have a strange power saving mode enabled?
    >> tg3_test_dma() Write the buffer failed -19
    >> tg3: DMA engine test failed, aborting.
    > You're getting an NMI during tg3_init_one() which means that the NIC is
    > probably bad. I did a quick test on the same version of the 5701 NIC
    > with the same tg3 driver and it worked fine.
    > Please find out if the NIC is known to be bad. Thanks.

    Up until recently, this NIC was reported to work. I booted our
    2.6.5-based SLES9 kernel on it. This is the kernel the machine has been
    running for a while with the NIC working, and when I booted it, I got
    the same DMA failure messages as with 2.6.16-rc4.

    I suspect that the hardware has just recently failed, and I figured it
    was a hardware problem when I saw the NMI/DMA messages, but since I
    don't have physical access to the hardware, immediate removal wasn't an

    - -Jeff

    - --
    Jeff Mahoney
    SUSE Labs
    Version: GnuPG v1.4.2 (GNU/Linux)
    Comment: Using GnuPG with Thunderbird -

    -----END PGP SIGNATURE-----
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2006-02-22 17:50    [W:0.020 / U:37.832 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site