LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Eric Lacombe <tuxiko@free.fr>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Steve French <sfrench@us.ibm.com>, Eric Lacombe <tuxiko@free.fr>
Subject: Re: Linux 2.6.19.2: maybe a bug inside the r8169 network driver (was Re: Linux 2.6.19.2: Freeze with CIFS mount)
Date: Wed, 14 Feb 2007 11:49:52 +0100	[thread overview]
Message-ID: <200702141149.53041.tuxiko@free.fr> (raw)
In-Reply-To: <20070213203047.GA4158@electric-eye.fr.zoreil.com>

On Tuesday 13 February 2007 21:30:47 Francois Romieu wrote:
> Eric Lacombe <tuxiko@free.fr> :
> [...]
>
> > That problem also remind me that when I compiled this driver without
> > the "CONFIG_NET_ETHERNET" (in the section "Ethernet (10 or 100Mbit)"), I
> > have really poor performance with the net device. Maybe it is related, or
> > not ;)
> >
> > If it gives you more ideas ?
> > Maybe it could be interesting to know about the r8169 maintainer, but I
> > dont know who he is.
>
> 1. $ ls
>    arch     crypto         include  kernel       mm              scripts
>    block    Documentation  init     lib          net             security
>    COPYING  drivers        ipc      MAINTAINERS  README          sound
>    CREDITS  fs             Kbuild   Makefile     REPORTING-BUGS  usr
>
>    The maintainer of the r8169 driver is listed in the MAINTAINERS file.

I see, thanks ;)

(I thought the MAINTAINERS file was not fully maintained ;)

>
> 2. Disabling CONFIG_NET_ETHERNET is a bad idea. Don't do that.

ok, but why having it only inside the "ethernet 100" menu ?
It is misleading, no ?

>
> 3. See tethereal -w or tcpdump on the adequate interface to save a
>    traffic dump.

yep, but the problem is that I cant do that from the NAS Box. I will try to 
monitor the traffic via the system that will freeze... For the moment I can't 
monitor the net traffic from an alternate PC, but soon.

>
> 4. Are you using a binary module for your video adapter ?

yes, I suppose that I have to unload this one before doing further tests.

>
> 5. How does the 2.6.20 version of the r8169 driver behave ?

I don't have installed it yet, but I'll do it this evening.

>
> 6. You may setup a cron to monitor an ethtool dump of the register of
>    the 8169 at regular interval. ifconfig and /proc/interrupts could
>    exhibit some unusual drift as time passes on too.

I will do that. When I could put a third system to monitor the traffic, I will 
make "the system that freeze" keep sending that information to it.

>
> 7. A dmesg would be welcome.

I could do that, this evening.

>
> 8. Please open a PR at bugzilla.kernel.org.

ok

>
> |...]
> |
> > > There are various ways to analyze system hangs including (at least in
> > > some cases) getting a system dump which
> > > can be used to isolate the failing location - hopefully
> >
> > I would like to have more detailed help, if possible.
>
> CONFIG_MAGIC_SYSRQ is set. Check that the magic sysrq is not disabled at
> runtime through /etc/sysctl.conf. See Documentation/sysrq.txt for details.

ok

>
> Please keep Steve French in the loop.

ok

Thanks for your response ;)

	Eric

  reply	other threads:[~2007-02-14 10:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-30 12:37 Linux 2.6.19.2: Freeze with CIFS mount Eric Lacombe
2007-01-31  3:51 ` Steven French
2007-01-31 14:51   ` Eric Lacombe
2007-02-13 13:52   ` Linux 2.6.19.2: maybe a bug inside the r8169 network driver (was Re: Linux 2.6.19.2: Freeze with CIFS mount) Eric Lacombe
2007-02-13 20:30     ` Francois Romieu
2007-02-14 10:49       ` Eric Lacombe [this message]
2007-03-05 21:19         ` Eric Lacombe
2007-03-05 22:16           ` Francois Romieu
2007-03-06 16:42             ` Eric Lacombe
2007-03-07 19:48               ` Eric Lacombe
2007-03-09  9:30                 ` Eric Lacombe

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=200702141149.53041.tuxiko@free.fr \
    --to=tuxiko@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=romieu@fr.zoreil.com \
    --cc=sfrench@us.ibm.com \
    --subject='Re: Linux 2.6.19.2: maybe a bug inside the r8169 network driver (was Re: Linux 2.6.19.2: Freeze with CIFS mount)' \
    /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

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).