netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>,
	Francois Romieu <romieu@fr.zoreil.com>
Cc: Network Development <netdev@vger.kernel.org>
Subject: Re: 2.6.29-rc6: Reported regressions 2.6.27 -> 2.6.28
Date: Tue, 24 Feb 2009 17:05:26 +0100	[thread overview]
Message-ID: <200902241705.33271.eike-kernel@sf-tec.de> (raw)
In-Reply-To: <HFSEX4uppGO.A.JSG.2yzoJB@chimera>

[-- Attachment #1: Type: text/plain, Size: 812 bytes --]

Rafael J. Wysocki wrote:

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12500
> Subject		: r8169: NETDEV WATCHDOG: eth0 (r8169): transmit timed out
> Submitter	: Justin Piszcz <jpiszcz@lucidpixels.com>
> Date		: 2009-01-13 21:19 (42 days old)
> References	: http://marc.info/?l=linux-kernel&m=123188160811322&w=4
> Handled-By	: Francois Romieu <romieu@fr.zoreil.com>

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12411
> Subject		: 2.6.28: BUG in r8169
> Submitter	: Andrey Vul <andrey.vul@gmail.com>
> Date		: 2008-12-31 18:37 (55 days old)
> References	: http://marc.info/?l=linux-kernel&m=123074869611409&w=4

Francois,

would you agree to mark both as dupe of #10109? These problems have been there 
for a year now, that is nothing new.

Eike (shortening CC list)

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2009-02-24 16:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-23 22:00 2.6.29-rc6: Reported regressions 2.6.27 -> 2.6.28 Rafael J. Wysocki
2009-02-23 22:02 ` [Bug #12160] networking oops after resume from s2ram (2.6.28-rc6) Rafael J. Wysocki
2009-02-24 16:05 ` Rolf Eike Beer [this message]
2009-02-24 23:23   ` 2.6.29-rc6: Reported regressions 2.6.27 -> 2.6.28 Francois Romieu

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=200902241705.33271.eike-kernel@sf-tec.de \
    --to=eike-kernel@sf-tec.de \
    --cc=netdev@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=romieu@fr.zoreil.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;
as well as URLs for NNTP newsgroup(s).