[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20120727091319.GA27071@electric-eye.fr.zoreil.com>
Date: Fri, 27 Jul 2012 11:13:19 +0200
From: Francois Romieu <romieu@...zoreil.com>
To: Denys Fedoryshchenko <denys@...p.net.lb>
Cc: netdev@...r.kernel.org
Subject: Re: r8169, 3.5.0, does't work at all
Denys Fedoryshchenko <denys@...p.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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists