From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+w=401wt.eu-S1751168AbZIBJtd@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1751168AbZIBJtd (ORCPT <rfc822;w@1wt.eu>);
	Wed, 2 Sep 2009 05:49:33 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750783AbZIBJtc
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Wed, 2 Sep 2009 05:49:32 -0400
Received: from mail-fx0-f217.google.com ([209.85.220.217]:37900 "EHLO
	mail-fx0-f217.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1750790AbZIBJtb (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Wed, 2 Sep 2009 05:49:31 -0400
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:cc:subject
         :references:in-reply-to:content-type:content-transfer-encoding;
        b=cHawx6AWuJUyZoac1e3WY+sCEXWTYNkflyoh9n4T/mRTQlsY8comvDvK6GP0fmZBDm
         Z2nOCoqfkn00ExBiRubCUsee4Z0eBf8IpGmjfMiviKdTGLMgYP5UhloGmY4LOk1TZDga
         apuyLNLOlMOy67eymjKIiI8k+FfI+j5a5ma+Y=
Message-ID: <4A9E3FAB.3040700@gmail.com>
Date: Wed, 02 Sep 2009 12:49:31 +0300
From: roma1390 <roma1390@gmail.com>
User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090707)
MIME-Version: 1.0
To: Francois Romieu <romieu@fr.zoreil.com>
CC: linux-kernel@vger.kernel.org, David Dillow <dave@thedillows.org>
Subject: Re: r8169 NETDEV WATCHDOG: eth0: transmit timed out [8/8]
References: <b410963b0908290221s4ed3d66fm50ea2862cf7500f5@mail.gmail.com> <b410963b0909020022q68101ed8n5cdafdcbdabea230@mail.gmail.com> <20090902084746.GA15870@electric-eye.fr.zoreil.com>
In-Reply-To: <20090902084746.GA15870@electric-eye.fr.zoreil.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Francois Romieu wrote:
> roma1390 <roma1390@gmail.com> :
> [...]
>> sorry but debian stable provides latest 2.6.26-2-amd64
>> curent workaround is to use: driver r8168.
> 
> Fine.
> 
> You did not answer David's question regarding your readiness to test
> patches (and / or recent kernel).
> 
> May I assume the answer is negative ?

Sorry, but I think there is a small chances to test. System is very busy,
and we don't have any replacement for it. Btw we didn't have direct access
to system, it's just dedicated server.