From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751584AbWFQCvZ (ORCPT ); Fri, 16 Jun 2006 22:51:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751495AbWFQCvZ (ORCPT ); Fri, 16 Jun 2006 22:51:25 -0400 Received: from dsl027-180-168.sfo1.dsl.speakeasy.net ([216.27.180.168]:10665 "EHLO sunset.davemloft.net") by vger.kernel.org with ESMTP id S1751226AbWFQCvY (ORCPT ); Fri, 16 Jun 2006 22:51:24 -0400 Date: Fri, 16 Jun 2006 19:51:47 -0700 (PDT) Message-Id: <20060616.195147.123399792.davem@davemloft.net> To: mchan@broadcom.com Cc: jk@blackdown.de, linux-kernel@vger.kernel.org, netdev@vger.kernel.org Subject: Re: tg3 timeouts with 2.6.17-rc6 From: David Miller In-Reply-To: <1150507652.26368.46.camel@rh4> References: <1150494161.26368.39.camel@rh4> <87bqsslk9e.fsf@blackdown.de> <1150507652.26368.46.camel@rh4> X-Mailer: Mew version 4.2 on Emacs 21.4 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org From: "Michael Chan" Date: Fri, 16 Jun 2006 18:27:32 -0700 > In the meantime, I wonder if we should disable TSO by default on the > 5780 chip for 2.6.17. Sounds reasonable. Would we disable it for all chips that set TG3_FLG2_5780_CLASS or a specific variant?