Ok i found the reason, wasn't TG3 driver problem, but firmware. If it can help someone else: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=PSD_EU050629_CW01&prodTypeId=329290&prodSeriesId=407731 > > > > > > > > > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- [POSSIBLE BUG]: tg3 network is "lost"
- From: serge <[email protected]>
- [POSSIBLE BUG]: tg3 network is "lost"
- Prev by Date: Re: containers (was Re: -mm merge plans for 2.6.23)
- Next by Date: Re: [PATCH 06/13] IB/ehca: Set SEND_GRH flag for all non-LL UD QPs on eHCA2
- Previous by thread: [POSSIBLE BUG]: tg3 network is "lost"
- Next by thread: Re: [RFC/PATCH] debug workqueue deadlocks with lockdep
- Index(es):
 |