RE: [E1000-devel] [in-tree drivers] freezing e1000e in 2.6.31 (SMPonly? MSI? PAUSE!)

[Allan, Bruce W]

Not a fix, but a workaround.

It's not your gigabit switch either; it's a bug in the driver introduced in 2.6.30...sorry about that.  I'm working on a fix now that should be submitted upstream in the next few days.

Sorry for any inconvenience,
Bruce.

>-----Original Message-----
>From: Nix [mailto:nix@xxxxxxxxxxxxx]
>Sent: Monday, November 09, 2009 4:09 PM
>To: Tantilov, Emil S
>Cc: e1000-devel@xxxxxxxxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx
>Subject: Re: [E1000-devel] [in-tree drivers] freezing e1000e in 2.6.31
>(SMP only? MSI? PAUSE!)
>
>On 8 Nov 2009, nix@xxxxxxxxxxxxx told this:
>
>> On 6 Nov 2009, Emil S. Tantilov verbalised:
>>> Also try disabling Tx pause frames:
>>> ethtool -A fastnet tx off autoneg off
>>
>> Trying that now. No freezes yet, but I haven't really given it long
>> enough.
>
>I just did a large number of kernel-build-and-installs with frame
>pointers over NFS over the errant link. No problems at all.
>
>I think we can say this fixes it (works around it?)
>
>Does this implicate the gigabit switch I'm talking to, or is it a kernel
>bug? (It looks like the cheap Realteks at the other ends of this link
>don't support pause frames at all: at least ethtool -a gives
>-EOPNOTSUPP, but maybe they simply can't be turned off... hm, r8169.c
>vaguely suggests that it supports them but can't turn them off without
>source hacking.)
>
>--------------------------------------------------------------------------
>----
>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-
>Day
>trial. Simplify your report design, integration and deployment - and focus
>on
>what you do best, core application coding. Discover what's new with
>Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>_______________________________________________
>E1000-devel mailing list
>E1000-devel@xxxxxxxxxxxxxxxxxxxxx
>https://lists.sourceforge.net/lists/listinfo/e1000-devel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/