SCIENTIFIC-LINUX-USERS Archives

February 2009

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Akemi Yagi <[log in to unmask]>
Reply To:
Akemi Yagi <[log in to unmask]>
Date:
Wed, 11 Feb 2009 13:51:58 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (26 lines)
On Wed, Feb 11, 2009 at 1:31 PM, Connie Sieh <[log in to unmask]> wrote:
> There are lots of reports of issues like this for tg3 but most reports end
> in "did not hear from requester so closing" or "Fedora Core X is not
> supported any more so closing".  Does anyone know of a real solution to this
> problem.  Reading all the bugzilla and Google results for this problem make
> my head hurt :-) .  Note that the error message
> "tg3_stop_block timed out" can be a generic message thus having many causes.
>
> We have been experiencing intermittent network failures on systems running
> SLF47 2.6.9-78.0.1 kernel/tg3 3.86 driver .  They waiting for the tcp to
> finish, which never happens.  The failures are load-related.
>
> This error happened from time to time over the life of these nodes
> but they were operating more or less stably under SLF45/x86_64, tg3 3.77
> driver.
>
> There are reports of this issue for RHEL 5 too.

I see one success story in the CentOS forum here (note #4):

http://www.centos.org/modules/newbb/viewtopic.php?viewmode=flat&order=ASC&topic_id=15932&forum=39

May not be a solution for all cases but at lease something to look at.

Akemi

ATOM RSS1 RSS2