Bug#642025: [Andrey Vasilishin: Re: (r8169): transmit queue 0 timed out]

[Jonathan Nieder <jrnieder@gmail.com>]

Forwarding with permission.

--- Begin Message ---

• To: Jonathan Nieder <jrnieder@gmail.com>
• Subject: Re: (r8169): transmit queue 0 timed out
• From: Андрей Василишин <a.vasilishin@kpi.ua>
• Date: Mon, 25 Jun 2012 20:43:39 +0300
• Message-id: <4FE8A34B.9020603@kpi.ua>
• Reply-to: a.vasilishin@kpi.ua
• In-reply-to: <[🔎] 20120625033525.GA4332@burratino>
• References: <4E7626F7.6060608@kpi.ua> <[🔎] 20120619191035.GA19914@burratino> <[🔎] 4FE1BD74.2070109@kpi.ua> <[🔎] 20120625033525.GA4332@burratino>

25.06.2012 6:35, Jonathan Nieder пишет:

Андрей Василишин wrote:

Андрей Василишин wrote:

NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out

[...]

Now I am using 3.2.0-2 kernel and not using Realtek NIC, thats why I
can't reproduce this bug.

Thanks for the update.  Do you still have access to the Realtek NIC?
If we come up with a patch to try, would you be interested in trying
it?

Oh, I have many servers and almost all of them now working with other NICs. I don't remember which server contain this bug. Most probably there is already last kernel.

(I think there was a bugfix addressing similar symptoms in 3.2-rc5,
actually, so just trying a recent kernel would already be
interesting.)

"No" is a fine answer, but please do let us know so we can plan
accordingly.

If I find old (>=2.6.32) kernel and Realtek NIC, What should I do?

--
WBR, Andrey Vasilishin CDIG1-UANIC, CDIG1-RIPE

--- End Message ---