From: "Paul Aviles" <paul.aviles@palei.com>
To: "Jesse Brandeburg" <jesse.brandeburg@gmail.com>
Cc: <netdev@vger.kernel.org>
Subject: Re: e1000 Detected Tx Unit Hang
Date: Sun, 3 Sep 2006 19:37:38 -0400 [thread overview]
Message-ID: <000d01c6cfb1$f0d26880$3224050a@avilespaxp> (raw)
In-Reply-To: 4807377b0609031045w67f70a3ese6bea93c15f75ba2@mail.gmail.com
Hey Jesse, thanks for your reply. Here is the stuff on /procs. The weird
part is that I have several other identical systems and only one is
affected. Today I moved the hard drive to another similar system and I am
not seeing the problem so I am wondering if is something maybe wrong with
the card eeprom? Is there a way to check that?
Regards,
Paul
cat /proc/interrupts
CPU0 CPU1
0: 7716253 0 IO-APIC-edge timer
3: 11538 0 IO-APIC-edge serial
8: 1 0 IO-APIC-edge rtc
9: 0 0 IO-APIC-level acpi
14: 93406 0 IO-APIC-edge ide0
16: 70540 0 IO-APIC-level uhci_hcd:usb4, eth0
17: 2 0 IO-APIC-level ehci_hcd:usb1
18: 0 0 IO-APIC-level uhci_hcd:usb2, uhci_hcd:usb5
19: 90 0 IO-APIC-level uhci_hcd:usb3
NMI: 0 0
LOC: 7715839 7715838
ERR: 0
MIS: 0
----- Original Message -----
From: "Jesse Brandeburg" <jesse.brandeburg@gmail.com>
To: "Paul Aviles" <paul.aviles@palei.com>
Cc: <netdev@vger.kernel.org>
Sent: Sunday, September 03, 2006 1:45 PM
Subject: Re: e1000 Detected Tx Unit Hang
> On 9/2/06, Paul Aviles <paul.aviles@palei.com> wrote:
>> I am getting "e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang"
>> using
>> stock 2.6.17.11, 2.6.17.5 or 2.6.17.4 kernels on centos 4.3.
>>
>> The server is a Tyan GS12 ( 82541GI/PI and 82547GI) and is connected to
>> a
>> Netgear GS724T Gig switch. I can easily reproduce the problem by trying
>> to
>> do a large ftp transfer to the server. It does not happen if the server
>> is
>> connected to a dummy 100 Mb switch, only when is connected to the Gig
>> switch.
>> I have also tried the options line below disabling tso, tx and rx in the
>> modprobe.conf without any luck.
>
> Hi Paul, sorry to hear about your problem. You're getting hangs on
> the 82547 right? can you send the output of cat /proc/interrupts.
> I'm curious if you are sharing interrupts while running NAPI.
>
> Also, please try the driver without CONFIG_E1000_NAPI enabled in your
> kernel .config, and let us know the results.
>
> Someone has posted (what they think is) a theoretical problem with
> irq_sem on the 82547 at e1000.sf.net and I haven't had a chance to
> figure it out yet.
>
> Jesse
>
> --
> VGER BF report: U 0.495355
> -
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
--
VGER BF report: U 0.516297
next prev parent reply other threads:[~2006-09-03 23:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-02 14:39 e1000 Detected Tx Unit Hang Paul Aviles
2006-09-03 17:45 ` Jesse Brandeburg
2006-09-03 23:37 ` Paul Aviles [this message]
2006-09-05 16:09 ` Jesse Brandeburg
2006-09-06 1:33 ` Paul Aviles
2006-09-11 4:03 ` Paul Aviles
2006-09-17 2:05 ` Paul Aviles
-- strict thread matches above, loose matches on Subject: below --
2008-02-15 22:52 e1000: " Bernd Schubert
2008-02-15 23:29 ` Kok, Auke
2008-02-16 0:26 ` Bernd Schubert
2008-02-19 16:47 ` Kok, Auke
[not found] <000f01c6ce49$affd37e0$3224050a@avilespaxp>
2006-09-02 5:45 ` e1000 " Auke Kok
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='000d01c6cfb1$f0d26880$3224050a@avilespaxp' \
--to=paul.aviles@palei.com \
--cc=jesse.brandeburg@gmail.com \
--cc=netdev@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