| 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
| ||
|
Date: Sun, 1 Jan 2012 18:03:20 -0800 From: Matt Ginzton <matt@...zton.net> To: Francois Romieu <romieu@...zoreil.com> Cc: nic_swsd@...ltek.com, netdev@...r.kernel.org Subject: Re: reproducible kernel freeze using r8169 in Linux 3.0 On Dec 18, 2011, at 12:32 AM, Francois Romieu wrote: > Matt Ginzton <matt@...zton.net> : > [...] >> Please let me know if I'm reporting this to the right place, or if there's >> any other helpful info I can provide. > > Please grep for a XID line in dmesg and send it so we can figure the > specific revision of your chipset (lspci can not figure it). > > If it says something like "blah blah XID 1c4...", you should give current > -rc a try (who shouldn't ?). Just to follow up on this old thread: - my XID line says 1c4000c0 - I tried 3.2-rc7 kernel, and couldn't reproduce any problems at all -- not the complete system freeze from 3.0 kernels, nor the slow_path kernel warning and backtrace from 3.1 kernels. A big improvement indeed -- thank you. I do note that TX performance as measured by pktgen is lower than r8168 -- with r8169 in 3.2-rc7 I see something like 455MB/sec and with r8168, IIRC, the number was closer to 800MB/sec. This may be a very artificial statistic, and isn't something I happen to care about and I'm certainly not going to use r8168 because of it, but it may be worth looking into? cheers, Matt -- 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