Re: r8169 2.2LK: Low link speed after suspend
Hi again Francois! 2.6.22-rc7 does suspend-to-disk again ... and the bad news is, the reported problem (link speed 100 not 1000 after resume from suspend-to-disk) is still there when using 2.6.22-rc7 with your -rc6 driver patch. The symptoms are the same as in 2.6.18 with unpatched r8169. ifdown eth2 ifup eth2 does not help, but ifdown eth2 rmmod r8169 modprobe r8169 ifup eth2 does. Now, exacty what do you want me to do with the mii-tool again? Please advise. regards, Peter - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: r8169 2.2LK: Low link speed after suspend
Hi again Francois! > > No NFS but networking or no networking at all ? > > Networking in itself was fine and stable, and with seemingly much better > performance in large file transfers as well. > > NFS appeared to be working too, problem was just that workstation and > server couldn't agree on file locking procedures anymore, and all existing > files could only be read but not written to. This proved quite > unproductive, so I had to revert. I've been browsing bug lists a bit, and seem to suffer exactly from this one: https://bugzilla.novell.com/show_bug.cgi?id=272268 ... whenever I use an updated kernel (2.6.21.5 or 2.6.22-rc7) on the client end. The original 2.6.18.8.0-3 SuSE kernel works fine, and updating the server as well doesn't help. Ideas welcome. g'night. Peter - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: r8169 2.2LK: Low link speed after suspend
Hi Francois! > Peter Missel <[EMAIL PROTECTED]> : > > > Unfortunately I couldn't get NFS to work with the updated kernel, so I > > had to revert to the original from SuSE 10.2. > > No NFS but networking or no networking at all ? Networking in itself was fine and stable, and with seemingly much better performance in large file transfers as well. The system log shows the occasional "APIC error on CPU0" that didn't seem to do any harm at all, except once where it then said it had disabled the PCI IRQ for the Realtek LAN chip. This is not seen on 2.6.18, and occurred only once with (I think) the original, unpatched r8169 driver from 2.6.21.5. With the patched driver, just the "APIC error" message appears with no device related information at all, so I can't really say whether this is anything to do with the Realtek LAN at all. NFS appeared to be working too, problem was just that workstation and server couldn't agree on file locking procedures anymore, and all existing files could only be read but not written to. This proved quite unproductive, so I had to revert. regards, Peter - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: r8169 2.2LK: Low link speed after suspend
Thanks Francois. Unfortunately I couldn't get NFS to work with the updated kernel, so I had to revert to the original from SuSE 10.2. The other thing that didn't work with 2.6.21.5 was suspend-to-disk (would suspend, but not resume), so I don't have any useful input for you this time. I'll be back. regards, Peter > Peter Missel <[EMAIL PROTECTED]> : > [...] > > > The patch applies without failure; I'm getting a warning during build, > > > > CC [M] drivers/net/r8169.o > > drivers/net/r8169.c: In function ‘rtl8169_start_xmit’: > > drivers/net/r8169.c:2341: warning: ‘txd’ may be used uninitialized in > > this function > > It's known and harmless. Blame gcc :o) - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: r8169 2.2LK: Low link speed after suspend
Bonjour Francois! > If you feel adventurous, you will find a compile-tested-only patchkit for > 2.6.21.5 here: > http://www.fr.zoreil.com/linux/kernel/2.6.x/2.6.21.5 > or: > http://www.fr.zoreil.com/people/francois/misc/20060630-2.6.21.5-r8169-test. >patch > > The content should be almost the same as the 2.6.22-rc6 patchkit dated > from 2007/06/28 (i.e. pending 2.6.23 merge). > Many thanks! The patch applies without failure; I'm getting a warning during build, CC [M] drivers/net/r8169.o drivers/net/r8169.c: In function ‘rtl8169_start_xmit’: drivers/net/r8169.c:2341: warning: ‘txd’ may be used uninitialized in this function After installing and loading the new driver, I still do have a gigabit connection, which is good. I'll be reporting about the suspend/resume behaviour next. regards, Peter - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: r8169 2.2LK: Low link speed after suspend
Hello Francois! I have finally gotten round to updating the kernel on this workstation. It is now on 2.6.21.5 as downloaded from www.kernel.org, built for AMD64. Unfortunately, the problem is not gone. After suspend-to-disk and resume, link speed is 100. Unplugging and replugging the cable does not help. Unloading and reloading the driver module brings it back up to 1000. But now I should have a driver that supports mii_tool, right? Since I cannot seem to find this tool available for download, could you please give me a pointer, or mail me the source? Many thanks! regards, Peter - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: r8169 2.2LK: Low link speed after suspend
Hi Francois! Sorry, returning to this issue took me longer than anticipated before I could return to the issue. > Hardly: the r8169 driver has been modified by ~40 patches from 2.6.18 to > now. > > There is an ugly hack^W^W quick backport for 2.6.18 at: > http://www.fr.zoreil.com/people/francois/backport/r8169/20070418-00 > > It compiles but I do not know if it works and I strongly suggest to use > a more recent kernel package anyway. Unfortunately the driver that comes with 2.6.18 doesn't appear to support mii-tool. I get this message: >Mars:~ # mii-tool -w eth2 >SIOCGMIIPHY on 'eth2' failed: Operation not supported Next I'll be looking at the provided backport. Also, I'll be confronted with SuSE 10.2 and the RTL8111B at work next week. I'll keep you updated. Peter - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: r8169 2.2LK: Low link speed after suspend
Hi Francois, and thanks again for the quick replies. > > Does this patchset work against kernel 2.6.18, or, better yet, is there a > > separate source package that lets me build the current driver on this > > older kernel? > > Hardly: the r8169 driver has been modified by ~40 patches from 2.6.18 to > now. > > There is an ugly hack^W^W quick backport for 2.6.18 at: > http://www.fr.zoreil.com/people/francois/backport/r8169/20070418-00 > > It compiles but I do not know if it works and I strongly suggest to use > a more recent kernel package anyway. I'll do my best - a kernel update is certainly not possible on this particular machine, simply because it is a user workstation that is actually being used ;) Also, mii-tool doesn't appear to be included anywhere in this (SuSE 10.2 x64) installation, so I'll have to look into building this from source. Meanwhile, a new bit of information that maybe gives a hint: ethtool -d shows reg 0x6C "PHY status" changes from 0x6b (erroneous 100TX link) to 0x73 (correct 1000TX link). What ethtool dumps aren't MII registers, so I doubt that this tells us anything useful, but here it is anyway. Bonne nuit! Peter - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: r8169 2.2LK: Low link speed after suspend
Hello Francois! Thanks for the quick reply. > > Now after resume, the link is working OK but doesn't come back up to > > normal gigabit operation. ifdown, unloading and reloading the r8169 > > module, and then ifup again fixes it. > > > Can you try 2.6.21-rc7 + (either): > - http://www.fr.zoreil.com/linux/kernel/2.6.x/2.6.21-rc7/r8169-20070416 > - > http://www.fr.zoreil.com/people/francois/misc/20070416-2.6.21-rc7-r8169-tes >t.patch Does this patchset work against kernel 2.6.18, or, better yet, is there a separate source package that lets me build the current driver on this older kernel? > If it does not work better, please fill an entry for it at > bugzilla.kernel.org, Cc: it to me and attach the output of a registers dump > taken from mii-tool before suspend and after a failed resume. I'll possibly get to trying things out by the end of next week. Until then, real life will consume all my spare time. Thanks so far. regards, Peter - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
r8169 2.2LK: Low link speed after suspend
Greetings! I have a SuSE 10.2 64-bit installation that uses a Realtek PCI GbE chip in D-Link disguise (lspci see below). While this works rather well after a normal boot sequence, I don't get a gigabit link after resume from standby or suspend-to-disk. Entering standby, the link speed goes down to 100 Mb as expected; the link stays up during standby/suspend (for WOL purposes apparently). Now after resume, the link is working OK but doesn't come back up to normal gigabit operation. ifdown, unloading and reloading the r8169 module, and then ifup again fixes it. If there's something more I can do to help debug this, please let me know. Please be sure to copy me, since my list traffic here is still somewhat unreliable. Thanks. regards, Peter 00:0d.0 Ethernet controller: D-Link System Inc DGE-528T Gigabit Ethernet Adapter (rev 10) Subsystem: D-Link System Inc DGE-528T Gigabit Ethernet Adapter Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- http://vger.kernel.org/majordomo-info.html
