Netdev List
 help / color / mirror / Atom feed
From: Francois Romieu <romieu@fr.zoreil.com>
To: Denys Fedoryshchenko <denys@visp.net.lb>
Cc: netdev@vger.kernel.org
Subject: Re: r8169, 3.5.0, does't work at all
Date: Fri, 27 Jul 2012 11:13:19 +0200	[thread overview]
Message-ID: <20120727091319.GA27071@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <e9e38770b95bc3664fdc642fdfb65a13@visp.net.lb>

Denys Fedoryshchenko <denys@visp.net.lb> :
[...]
> and i can search for more machines with similar cards.

Thanks.

There seems to be a more recent bios for this motherboard. Is the second
8168b an add-on or is it a dual-port DH61HO ?

You are using x86 32 with PAE and slub where I use x86 64 with slab.
I am building a x86 32 bits test configuration for a 8168b right now.

Let's see what happened during the 3.4 .. 3.5 cycle in the r8169 driver:

- You may revert 7dbb491878a2c51d372a8890fa45a8ff80358af1 ("r8169: avoid NAPI
  scheduling delay.")

  I can see a napi rtl8169_poll failing to schedule rtl_slow_event_work
  when it is already scheduled on a different cpu, said rtl_slow_event_work
  running while rtl8169_poll is delayed and rtl8169_poll stomping on the
  IntrMask after rtl_slow_event_work did.

  It does not tell why the device does not recover after the netdev watchdog
  but it could be worth trying.

- You may revert 851e60221926a53344b4227879858bef841b0477 ("r8169: Config1 is
  read-only on 8168c and later.") as well.

  It changes the PMEEnable write ordering for the 8168b (RTL_GIGA_MAC_VER_17)
  and a few others chipset.

-- 
Ueimor

      reply	other threads:[~2012-07-27  9:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-26 11:58 r8169, 3.5.0, does't work at all Denys Fedoryshchenko
2012-07-26 19:56 ` Francois Romieu
2012-07-26 20:44   ` Denys Fedoryshchenko
2012-07-27  9:13     ` Francois Romieu [this message]

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=20120727091319.GA27071@electric-eye.fr.zoreil.com \
    --to=romieu@fr.zoreil.com \
    --cc=denys@visp.net.lb \
    --cc=netdev@vger.kernel.org \
    /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