public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dror Cohen <dror.xiv@gmail.com>
To: e1000-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org,
	linville@tuxdriver.com
Subject: Re: e1000 6.0.60 problems
Date: Mon, 15 Aug 2005 18:02:56 +0300	[thread overview]
Message-ID: <6c58e3190508150802e2cd16@mail.gmail.com> (raw)
In-Reply-To: <6c58e319050815061437bc278f@mail.gmail.com>

some updates:

On 8/15/05, Dror Cohen <dror.xiv@gmail.com> wrote:
> Hello all,
>....
> when using the latest 6.1.16 version of the driver (which doesn't seem
> to have the watch dog fix, but a lot of other fixes) we see similar
> results to our modified version - there are still NETDEV events with
> the "Detected Tx Unit Hang" message followed by the output of the
> registers.

we just had a stuck machine with the 6.1.16 version (again, no console
, had to reboot)
var log messages looks like the one the previous halt (order
allocation failed, from e1000 irq handling). I guess this means the
backporting of the watch dog does indeed help.

> 
> more information can be supplied if needed.
> 
> our questions:
> * Is anyone experiencing similar problems (looks to us alot like: "[
> 955064 ] e1000 freezes Linux with 82544GC (similar to a year-old bug)") ?

forgot the link:
http://sourceforge.net/tracker/index.php?func=detail&aid=955064&group_id=42302&atid=447449

> 
> * Was the watch dog change forgotten, or left out deliberetly ? Does our
> patch seems to be OK ? it is also not present in the latest version (6.1.6).
> 
> * are the allocation problems related in anyway to e1000 problem ?
> 
> ...
> 
> 
> 

since I'm not on the linux-kernel list (but I am on the linux-net and
e1000 lists) please CC
replies to dror at xiv.co.il 

thanks,
Dror

      reply	other threads:[~2005-08-15 15:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-15 13:14 e1000 6.0.60 problems Dror Cohen
2005-08-15 15:02 ` Dror Cohen [this message]

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=6c58e3190508150802e2cd16@mail.gmail.com \
    --to=dror.xiv@gmail.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=linville@tuxdriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox