Re: 2.2 <-> 2.4.5-ac5 tcp too slow (false alarm)
>Right now I am compiling 2.4.5 on the clients to verify that it's an >2.2 vs 2.4 issue. It wasn't 2.4 vs. 2.2 but the tulip driver. Swapped it for a dual eepro100 and geth 8MB/s (tbench 4) now. Ingo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.2 <-> 2.4.5-ac5 tcp too slow
>reference in the list archives. i have an x86 laptop running 2.2.17 (2.2.19 >has the same effect) and an alpha pws 500 running 2.4.5-ac5. tcp starts slow >and get slower. Same here. I've set up an Alpha Ruffian with a Quad Starfire as a new firewall. My test clients were x86/2.2.16-18 up to now. TBench between two clients directly: 10 MB/S. TBench through the 2.4.4/5 router: 0,4 MB/s. Right now I am compiling 2.4.5 on the clients to verify that it's an 2.2 vs 2.4 issue. Ingo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.2 - 2.4.5-ac5 tcp too slow
reference in the list archives. i have an x86 laptop running 2.2.17 (2.2.19 has the same effect) and an alpha pws 500 running 2.4.5-ac5. tcp starts slow and get slower. Same here. I've set up an Alpha Ruffian with a Quad Starfire as a new firewall. My test clients were x86/2.2.16-18 up to now. TBench between two clients directly: 10 MB/S. TBench through the 2.4.4/5 router: 0,4 MB/s. Right now I am compiling 2.4.5 on the clients to verify that it's an 2.2 vs 2.4 issue. Ingo - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.2 - 2.4.5-ac5 tcp too slow (false alarm)
Right now I am compiling 2.4.5 on the clients to verify that it's an 2.2 vs 2.4 issue. It wasn't 2.4 vs. 2.2 but the tulip driver. Swapped it for a dual eepro100 and geth 8MB/s (tbench 4) now. Ingo - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.4.5 does not link on Ruffian (alpha)
Hi, I just tried to compile 2.4.5 on a Ruffian. With CPU selection "generic" it fails when linking the kernel (see below). With CPU=Ruffian, it compiles and links fine. Haven't tried booting yet, 'cause the machine is some 20 miles away from here. What more can I provide/do to help? Cheers, Ingo - ld -r -o kernel.o entry.o traps.o process.o osf_sys.o irq.o irq_alpha.o signal. o setup.o ptrace.o time.o semaphore.o alpha_ksyms.o irq_i8259.o irq_srm.o es1888 .o smc37c669.o smc37c93x.o ns87312.o pci.o pci_iommu.o core_apecs.o core_cia.o c ore_irongate.o core_lca.o core_mcpcia.o core_polaris.o core_t2.o core_tsunami.o core_titan.o sys_alcor.o sys_cabriolet.o sys_dp264.o sys_eb64p.o sys_eiger.o sys _jensen.o sys_miata.o sys_mikasa.o sys_nautilus.o sys_titan.o sys_noritake.o sys _rawhide.o sys_ruffian.o sys_rx164.o sys_sable.o sys_sio.o sys_sx164.o sys_takar a.o sys_wildfire.o core_wildfire.o irq_pyxis.o sys_dp264.o: In function `tsunami_inb': sys_dp264.c(.text+0x440): multiple definition of `tsunami_inb' core_tsunami.o(.text+0x500):core_tsunami.c: first defined here sys_dp264.o: In function `clipper_map_irq': sys_dp264.c(.text+0x480): multiple definition of `tsunami_inw' core_tsunami.o(.text+0x540):core_tsunami.c: first defined here sys_dp264.o: In function `tsunami_inl': sys_dp264.c(.text+0x4c0): multiple definition of `tsunami_inl' core_tsunami.o(.text+0x580):core_tsunami.c: first defined here sys_dp264.o: In function `tsunami_outb': sys_dp264.c(.text+0x460): multiple definition of `tsunami_outb' core_tsunami.o(.text+0x520):core_tsunami.c: first defined here sys_dp264.o: In function `tsunami_outw': sys_dp264.c(.text+0x4a0): multiple definition of `tsunami_outw' core_tsunami.o(.text+0x560):core_tsunami.c: first defined here sys_dp264.o: In function `dp264_init_pci': sys_dp264.c(.text+0x4e0): multiple definition of `tsunami_outl' core_tsunami.o(.text+0x5a0):core_tsunami.c: first defined here sys_dp264.o: In function `tsunami_readb': sys_dp264.c(.text+0x540): multiple definition of `tsunami_readb' core_tsunami.o(.text+0x600):core_tsunami.c: first defined here sys_dp264.o: In function `tsunami_readw': sys_dp264.c(.text+0x560): multiple definition of `tsunami_readw' core_tsunami.o(.text+0x620):core_tsunami.c: first defined here sys_dp264.o: In function `webbrick_init_arch': sys_dp264.c(.text+0x580): multiple definition of `tsunami_readl' core_tsunami.o(.text+0x640):core_tsunami.c: first defined here sys_dp264.o: In function `tsunami_readq': sys_dp264.c(.text+0x5a0): multiple definition of `tsunami_readq' core_tsunami.o(.text+0x660):core_tsunami.c: first defined here sys_dp264.o: In function `tsunami_writeb': sys_dp264.c(.text+0x5c0): multiple definition of `tsunami_writeb' core_tsunami.o(.text+0x680):core_tsunami.c: first defined here sys_dp264.o: In function `tsunami_writew': sys_dp264.c(.text+0x5e0): multiple definition of `tsunami_writew' core_tsunami.o(.text+0x6a0):core_tsunami.c: first defined here sys_dp264.o: In function `tsunami_writel': sys_dp264.c(.text+0x600): multiple definition of `tsunami_writel' core_tsunami.o(.text+0x6c0):core_tsunami.c: first defined here sys_dp264.o: In function `tsunami_writeq': sys_dp264.c(.text+0x620): multiple definition of `tsunami_writeq' core_tsunami.o(.text+0x6e0):core_tsunami.c: first defined here sys_dp264.o: In function `tsunami_ioremap': sys_dp264.c(.text+0x500): multiple definition of `tsunami_ioremap' core_tsunami.o(.text+0x5c0):core_tsunami.c: first defined here sys_dp264.o: In function `monet_init_pci': sys_dp264.c(.text+0x520): multiple definition of `tsunami_is_ioaddr' core_tsunami.o(.text+0x5e0):core_tsunami.c: first defined here make[1]: *** [kernel.o] Error 1 make[1]: Leaving directory `/usr/src/linux-2.4.5/arch/alpha/kernel' make: *** [_dir_arch/alpha/kernel] Error 2 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.4.5 does not link on Ruffian (alpha)
Hi, I just tried to compile 2.4.5 on a Ruffian. With CPU selection generic it fails when linking the kernel (see below). With CPU=Ruffian, it compiles and links fine. Haven't tried booting yet, 'cause the machine is some 20 miles away from here. What more can I provide/do to help? Cheers, Ingo - ld -r -o kernel.o entry.o traps.o process.o osf_sys.o irq.o irq_alpha.o signal. o setup.o ptrace.o time.o semaphore.o alpha_ksyms.o irq_i8259.o irq_srm.o es1888 .o smc37c669.o smc37c93x.o ns87312.o pci.o pci_iommu.o core_apecs.o core_cia.o c ore_irongate.o core_lca.o core_mcpcia.o core_polaris.o core_t2.o core_tsunami.o core_titan.o sys_alcor.o sys_cabriolet.o sys_dp264.o sys_eb64p.o sys_eiger.o sys _jensen.o sys_miata.o sys_mikasa.o sys_nautilus.o sys_titan.o sys_noritake.o sys _rawhide.o sys_ruffian.o sys_rx164.o sys_sable.o sys_sio.o sys_sx164.o sys_takar a.o sys_wildfire.o core_wildfire.o irq_pyxis.o sys_dp264.o: In function `tsunami_inb': sys_dp264.c(.text+0x440): multiple definition of `tsunami_inb' core_tsunami.o(.text+0x500):core_tsunami.c: first defined here sys_dp264.o: In function `clipper_map_irq': sys_dp264.c(.text+0x480): multiple definition of `tsunami_inw' core_tsunami.o(.text+0x540):core_tsunami.c: first defined here sys_dp264.o: In function `tsunami_inl': sys_dp264.c(.text+0x4c0): multiple definition of `tsunami_inl' core_tsunami.o(.text+0x580):core_tsunami.c: first defined here sys_dp264.o: In function `tsunami_outb': sys_dp264.c(.text+0x460): multiple definition of `tsunami_outb' core_tsunami.o(.text+0x520):core_tsunami.c: first defined here sys_dp264.o: In function `tsunami_outw': sys_dp264.c(.text+0x4a0): multiple definition of `tsunami_outw' core_tsunami.o(.text+0x560):core_tsunami.c: first defined here sys_dp264.o: In function `dp264_init_pci': sys_dp264.c(.text+0x4e0): multiple definition of `tsunami_outl' core_tsunami.o(.text+0x5a0):core_tsunami.c: first defined here sys_dp264.o: In function `tsunami_readb': sys_dp264.c(.text+0x540): multiple definition of `tsunami_readb' core_tsunami.o(.text+0x600):core_tsunami.c: first defined here sys_dp264.o: In function `tsunami_readw': sys_dp264.c(.text+0x560): multiple definition of `tsunami_readw' core_tsunami.o(.text+0x620):core_tsunami.c: first defined here sys_dp264.o: In function `webbrick_init_arch': sys_dp264.c(.text+0x580): multiple definition of `tsunami_readl' core_tsunami.o(.text+0x640):core_tsunami.c: first defined here sys_dp264.o: In function `tsunami_readq': sys_dp264.c(.text+0x5a0): multiple definition of `tsunami_readq' core_tsunami.o(.text+0x660):core_tsunami.c: first defined here sys_dp264.o: In function `tsunami_writeb': sys_dp264.c(.text+0x5c0): multiple definition of `tsunami_writeb' core_tsunami.o(.text+0x680):core_tsunami.c: first defined here sys_dp264.o: In function `tsunami_writew': sys_dp264.c(.text+0x5e0): multiple definition of `tsunami_writew' core_tsunami.o(.text+0x6a0):core_tsunami.c: first defined here sys_dp264.o: In function `tsunami_writel': sys_dp264.c(.text+0x600): multiple definition of `tsunami_writel' core_tsunami.o(.text+0x6c0):core_tsunami.c: first defined here sys_dp264.o: In function `tsunami_writeq': sys_dp264.c(.text+0x620): multiple definition of `tsunami_writeq' core_tsunami.o(.text+0x6e0):core_tsunami.c: first defined here sys_dp264.o: In function `tsunami_ioremap': sys_dp264.c(.text+0x500): multiple definition of `tsunami_ioremap' core_tsunami.o(.text+0x5c0):core_tsunami.c: first defined here sys_dp264.o: In function `monet_init_pci': sys_dp264.c(.text+0x520): multiple definition of `tsunami_is_ioaddr' core_tsunami.o(.text+0x5e0):core_tsunami.c: first defined here make[1]: *** [kernel.o] Error 1 make[1]: Leaving directory `/usr/src/linux-2.4.5/arch/alpha/kernel' make: *** [_dir_arch/alpha/kernel] Error 2 - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: DHCP Problems with 3com 3c905C Tornado
> I recently installed a system with the 3c905C >NIC on RedHat 6.2. > The freshly installed RedHat 6.2 worked nice >and flawlessly, >However after upgrading >to the 2.2.16 RedHat Kernel RPMS, the DHCP negotiation >no longer worked! >I downloaded 2.2.18 proper. I compiled in the support >for the card, but also: same result. Have you checked conf.modules that now is modules.conf? In my case rh had just renamed/aliased the device and as soon as I had adapted modules.conf accordingly, the card worked. Of course, I might have completely misunderstood the problem, but it sounds a lot like what I saw... Cheers, Ingo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: DHCP Problems with 3com 3c905C Tornado
I recently installed a system with the 3c905C NIC on RedHat 6.2. The freshly installed RedHat 6.2 worked nice and flawlessly, However after upgrading to the 2.2.16 RedHat Kernel RPMS, the DHCP negotiation no longer worked! I downloaded 2.2.18 proper. I compiled in the support for the card, but also: same result. Have you checked conf.modules that now is modules.conf? In my case rh had just renamed/aliased the device and as soon as I had adapted modules.conf accordingly, the card worked. Of course, I might have completely misunderstood the problem, but it sounds a lot like what I saw... Cheers, Ingo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
