| 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: Mon, 15 Dec 2008 15:28:45 +0100 From: "Christoph Gysin" <christoph.gysin@...3z3.org> To: "Francois Romieu" <romieu@...zoreil.com> Cc: netdev@...r.kernel.org Subject: [OT] Re: 8139too in >=2.6.26: SIOCSIFFLAGS: Device or resource busy 2008/12/11 Francois Romieu <romieu@...zoreil.com>: > I was not clear enough: can you do a diff of the complete boot messages ? > For instance: > $ dmesg > dmesg-2.6.25 > [change kernel] > $ dmesg > dmesg-2.6.26 > $ diff -upN dmesg-2.6.25 dmesg-2.6.26 > > Rationale: > 1. the 8139too driver underwent almost no change between 2.6.25 and 2.6.26 > 2. rtl8139_open can only fail because of request_irq > > It is not clear that the issue is in the 8139too driver itself. I managed to get the device working even with recent kernels by using a stock ubuntu kernel configuration. Now I wonder what caused the poor performance. As you can see from the performance results, throughput decreases gradually during the test. This is reproducible. I only get back to the inital throughput after a reboot. I'm also wondering what could cause the huge difference between Rx and Tx throughput. Any guesses are greatly appreciated. This is OT now, as the problem seems not to be related to the driver anymore. Sorry for the noise. Christoph -- echo mailto: NOSPAM !#$.'<*>'|sed 's. ..'|tr "<*> !#:2" org@...3z3 -- 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