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
| ||
|
Message-ID: <20120320182000.GA15866@electric-eye.fr.zoreil.com> Date: Tue, 20 Mar 2012 19:20:00 +0100 From: Francois Romieu <romieu@...zoreil.com> To: Timo Teras <timo.teras@....fi> Cc: Eric Dumazet <eric.dumazet@...il.com>, Ben Hutchings <bhutchings@...arflare.com>, netdev@...r.kernel.org Subject: Re: linux-3.0.18+r8169+ipv4/tcp forwarding = tso/gso weirdness and performance degration Timo Teras <timo.teras@....fi> : [...] > The only differences seem to be the PCI ID field at byte offset 4-5, > Config 0 field at byte offset 0x14, and the checksum at 0x32-0x33. > > If I understand correctly, the Config 0 bit 0 affects Boot ROM size. It > affects only the PXE boot sequence? I have never played with it. I can only tell that it has a different value for my motherboard included 8168b (see previous messages). [...] > But other than that, I'm wondering if the failed mdio writing could have > caused permanent damage in the PHY. It's hard to tell and it wouldn't explain the corrupted eeprom. -- 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