All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Chan" <mchan@broadcom.com>
To: "benh@kernel.crashing.org" <benh@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	Nathan Lynch <ntl@pobox.com>,
	Matthew Carlson <mcarlson@broadcom.com>,
	netdev <netdev@vger.kernel.org>
Subject: Re: Strange tg3 regression with UMP fw. link reporting
Date: Fri, 08 Aug 2008 13:20:12 -0700	[thread overview]
Message-ID: <1218226812.12081.19.camel@HP1> (raw)
In-Reply-To: <1218233157.24157.343.camel@pasglop>


On Fri, 2008-08-08 at 15:05 -0700, Benjamin Herrenschmidt wrote:
> On Fri, 2008-08-08 at 11:43 -0700, Matt Carlson wrote:
> > We really shouldn't be displaying any error messages in the event of a
> > timeout though.  Earlier versions of the UMP firmware did not support
> > the link update interface.  The best thing the driver can do for all
> > cases is give the firmware a chance to service the event but continue
> > as if the event were serviced if it did not get an explicit ACK.
> 
> But that means that the driver will continuously spin 2.5ms every
> timer tick or so ? Or do I miss something ? Could it be possible to
> count timeouts and if after N attempts at an ack, they all timed out,
> disable the feature completely ?

Please see my other email.  Matt and I will fix it in a way to minimize
the spin as much as possible regardless of firmware version.

> 
> Or is there a way to test the version of the firmware ?
> 
> In any case, the fix should go into -stable as the problem is hurting
> 2.6.26. Also, should we consider updating the tg3 firmware on those
> machines ?
> 

Right, we'll take care of -stable as well.  Thanks.

WARNING: multiple messages have this Message-ID (diff)
From: "Michael Chan" <mchan@broadcom.com>
To: "benh@kernel.crashing.org" <benh@kernel.crashing.org>
Cc: "Matthew Carlson" <mcarlson@broadcom.com>,
	"Segher Boessenkool" <segher@kernel.crashing.org>,
	"linuxppc-dev list" <linuxppc-dev@ozlabs.org>,
	netdev <netdev@vger.kernel.org>, "Nathan Lynch" <ntl@pobox.com>
Subject: Re: Strange tg3 regression with UMP fw. link reporting
Date: Fri, 08 Aug 2008 13:20:12 -0700	[thread overview]
Message-ID: <1218226812.12081.19.camel@HP1> (raw)
In-Reply-To: <1218233157.24157.343.camel@pasglop>


On Fri, 2008-08-08 at 15:05 -0700, Benjamin Herrenschmidt wrote:
> On Fri, 2008-08-08 at 11:43 -0700, Matt Carlson wrote:
> > We really shouldn't be displaying any error messages in the event of a
> > timeout though.  Earlier versions of the UMP firmware did not support
> > the link update interface.  The best thing the driver can do for all
> > cases is give the firmware a chance to service the event but continue
> > as if the event were serviced if it did not get an explicit ACK.
> 
> But that means that the driver will continuously spin 2.5ms every
> timer tick or so ? Or do I miss something ? Could it be possible to
> count timeouts and if after N attempts at an ack, they all timed out,
> disable the feature completely ?

Please see my other email.  Matt and I will fix it in a way to minimize
the spin as much as possible regardless of firmware version.

> 
> Or is there a way to test the version of the firmware ?
> 
> In any case, the fix should go into -stable as the problem is hurting
> 2.6.26. Also, should we consider updating the tg3 firmware on those
> machines ?
> 

Right, we'll take care of -stable as well.  Thanks.



  reply	other threads:[~2008-08-09  0:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-08  7:35 Strange tg3 regression with UMP fw. link reporting Benjamin Herrenschmidt
2008-08-08  7:35 ` Benjamin Herrenschmidt
2008-08-08  8:58 ` Segher Boessenkool
2008-08-08  8:58   ` Segher Boessenkool
2008-08-08  9:18   ` Benjamin Herrenschmidt
2008-08-08 18:43     ` Matt Carlson
2008-08-08 18:43       ` Matt Carlson
2008-08-08 15:20       ` Michael Chan
2008-08-08 15:20         ` Michael Chan
2008-08-08 22:05       ` Benjamin Herrenschmidt
2008-08-08 20:20         ` Michael Chan [this message]
2008-08-08 20:20           ` Michael Chan
2008-08-08 21:25     ` Nathan Lynch
2008-08-08 21:25       ` Nathan Lynch
2008-08-08  9:21   ` Arnd Bergmann
2008-08-08  9:21     ` Arnd Bergmann

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=1218226812.12081.19.camel@HP1 \
    --to=mchan@broadcom.com \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mcarlson@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=ntl@pobox.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.