netdev - Re: r8169 2.2LK: Low link speed after suspend

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 3 Jul 2007 20:00:51 +0200
From:	Peter Missel <peter.missel@...inehome.de>
To:	Francois Romieu <romieu@...zoreil.com>
Cc:	netdev@...r.kernel.org, Jens Stroebel <drifter@...oft.de>
Subject: Re: r8169 2.2LK: Low link speed after suspend

Hi Francois!

> Peter Missel <peter.missel@...inehome.de> :
>
> > 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 majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html