I haven't done the NAPI yet. These are identical systems altogether, maybe the CPU is a different stepping at the most, but that is all. The "16: 70540 0 IO-APIC-level uhci_hcd:usb4, eth0" is the same in every GS12 I have. No overclocking and same BIOS. Tyan released ver 1.8 about a month ago and I did the upgrade and same effect. Then I thought about upgrading to 2.6.17.11 just to see if the driver will have any issues and nothing, same deal. The only way I was able to control it was usign a dummy 10/100 non-management switch. Then we had no issues.

I will try without NAPI tomorrow 9-6-06 and will report back. My understanding on NAPI was that it will drop packets by design on overload. Why will that cause a system lock?

Are there any other kernel options you would like to enable to track this better and if you need remote access to the system I can accomodate too, just let me know what time zone you are to schedule it. Let me know.

Regards,

Paul Aviles

----- Original Message ----- From: "Jesse Brandeburg" <[EMAIL PROTECTED]>
To: "Paul Aviles" <[EMAIL PROTECTED]>
Cc: <netdev@vger.kernel.org>
Sent: Tuesday, September 05, 2006 12:09 PM
Subject: Re: e1000 Detected Tx Unit Hang


On 9/3/06, Paul Aviles <[EMAIL PROTECTED]> wrote:
Hey Jesse, thanks for your reply. Here is the stuff on /procs. The weird
no problem,

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?

I doubt it is an eeprom problem.  you can dump the eeproms with
ethtool -e eth0 from both machines and compare them .  Odd that only
one system is having the problem.  Could it be that the hardware on
that box is having issues?  Are you sure the machines are running the
same bios version with the same settings?  Any overclocking?

 cat /proc/interrupts
           CPU0       CPU1
 16:      70540          0   IO-APIC-level  uhci_hcd:usb4, eth0

this could contribute to your problem, were you able to test without NAPI?

Jesse




-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to