netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Francois Romieu <romieu@fr.zoreil.com>
To: "Dale E. Martin" <dale@the-martins.org>
Cc: netdev@oss.sgi.com
Subject: Re: where is the proper place for r8169 bug reports?
Date: Tue, 1 Feb 2005 23:31:09 +0100	[thread overview]
Message-ID: <20050201223109.GA2957@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <20050201215607.GA8530@gerbil.toadis.porkis>

Dale E. Martin <dale@the-martins.org> :
[...]
> although it looks like the card is only found on cold boots.

Can you send (or put on a webpage) the same dmesg and lspci -vx when
it happens ?

> The irony of this, btw, is that linux/Documentation/Changes still
> recommends gcc 2.95.3 - even in version 2.6.8, possibly in 2.6.10.  (I
> think I saw it in there but I don't have it handy.)

You saw it there. No comment.

> Also, when I first started looking at this, I tried to #define
> RTL8169_DEBUG but was getting compile errors.  Should I file a bug about
> this ?

I lost this one. Re-added to the queue. Don't bother with a PR for it.

[...]
> It looks like the poor 1Ghz C3 in this machine is going to be the
> bottleneck for getting good transfer rates over gigabit ethernet ;-)

It depends on the kind of transfer. A bigger MTU really helps. So does
TSO and checksumming but it is really dependant on the kind of load.
This is the content of the patch against 2.4.28.

[...]
> What is the intention of this patch?  Is it to handle the 2.95.x issue or
> something else ?

See above. Can you:
- send me discretly the .o built from the r8169 sources with 2.95.3 ?
- pest me until you have a 2.95.3 compiled r8169 module which does not
  lock up any more ?

--
Ueimor

  reply	other threads:[~2005-02-01 22:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-31 18:15 where is the proper place for r8169 bug reports? Dale E. Martin
2005-01-31 21:49 ` Francois Romieu
2005-01-31 21:59   ` Dale E. Martin
2005-01-31 22:23     ` Francois Romieu
2005-02-01 21:56       ` Dale E. Martin
2005-02-01 22:31         ` Francois Romieu [this message]
2005-02-02 22:13           ` 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=20050201223109.GA2957@electric-eye.fr.zoreil.com \
    --to=romieu@fr.zoreil.com \
    --cc=dale@the-martins.org \
    --cc=netdev@oss.sgi.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).