Re: something wrong with fxp driver ?
On Fri, Jun 27, 2003 at 15:40:22 -0700, Doug White wrote: On Fri, 27 Jun 2003, Ying-Chieh Liao wrote: On Fri, Jun 27, 2003 at 09:28:31 -0400, Robert Watson wrote: You might compare the dmesg output from before/after and see if there are any obvious changes in IRQ allocation, shared interrupts, etc. Perhaps the changes in interrupt routing have resulted in some new behavior. I lost my old kernel : In the future, 'make reinstall' is your friend :) ok, I give up I think I have to revert my system back to 5.1-R -- self-producing in python : l='l=%s;print l%%`l`';print l%`l` -- Frank Stajano pgp0.pgp Description: PGP signature
Re: something wrong with fxp driver ?
On Fri, 27 Jun 2003, Ying-Chieh Liao wrote: On Fri, Jun 27, 2003 at 09:28:31 -0400, Robert Watson wrote: You might compare the dmesg output from before/after and see if there are any obvious changes in IRQ allocation, shared interrupts, etc. Perhaps the changes in interrupt routing have resulted in some new behavior. I lost my old kernel : In the future, 'make reinstall' is your friend :) -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: something wrong with fxp driver ?
On Fri, Jun 27, 2003 at 01:27:28PM +0800, Ying-Chieh Liao wrote: my previous kernel is about May 10, and the fxp works fine for me but I cvsuped and make world/kernel yesterday (6/26), and then terrible thing happens... the connection becomes v...e...r...y... s...l...o...w... my ping time to the gateway is about 8000ms (but sometimes 20ms) I've browse the mail archive of -current and -net, and I've noticed some similar problems with fxp (device timeout), and I also get this message (fxp0 device timeout) in my dmesg output, but I cant find out any solution : Is there any workaround, or patches ? Check that it's negotiating the media type and options correctly. On the gohan machines it has been failing to negotiate full-duplex mode for the past few months, leading to LAN transfer speeds on the order of 20kps unless I set the media options explicitly. Kris pgp0.pgp Description: PGP signature
Re: something wrong with fxp driver ?
On Thu, Jun 26, 2003 at 23:40:24 -0700, Kris Kennaway wrote:
Check that it's negotiating the media type and options correctly. On
the gohan machines it has been failing to negotiate full-duplex mode
for the past few months, leading to LAN transfer speeds on the order
of 20kps unless I set the media options explicitly.
I am not in a full-duplex environment, and autoselect set it to half-duplex as
well.
--
int i;main(){for(;i[]i;++i){--i;}];read('-'-'-',i+++hell\
o, world!\n,'/'/'/'));}read(j,i,p){write(j/p+p,i---j,i/i);}
-- IOCCC 1984
pgp0.pgp
Description: PGP signature
Re: something wrong with fxp driver ?
On Fri, Jun 27, 2003 at 13:27:28 +0800, Ying-Chieh Liao wrote:
my previous kernel is about May 10, and the fxp works fine for me
but I cvsuped and make world/kernel yesterday (6/26), and then terrible thing
happens... the connection becomes v...e...r...y... s...l...o...w...
my ping time to the gateway is about 8000ms (but sometimes 20ms)
The most strange thing is that there is NO packet lost
Every ping packet arrives in order... looks like the kernel piles my packet up
and send them out at once.
Terry [/home/ijliao] -ijliao- [W15] ping -c 10 140.113.1.1
PING 140.113.1.1 (140.113.1.1): 56 data bytes
64 bytes from 140.113.1.1: icmp_seq=0 ttl=62 time=8283.258 ms
64 bytes from 140.113.1.1: icmp_seq=1 ttl=62 time=7278.335 ms
64 bytes from 140.113.1.1: icmp_seq=2 ttl=62 time=6268.138 ms
64 bytes from 140.113.1.1: icmp_seq=3 ttl=62 time=5258.238 ms
64 bytes from 140.113.1.1: icmp_seq=4 ttl=62 time=4248.368 ms
64 bytes from 140.113.1.1: icmp_seq=5 ttl=62 time=3238.358 ms
64 bytes from 140.113.1.1: icmp_seq=6 ttl=62 time=2228.359 ms
64 bytes from 140.113.1.1: icmp_seq=7 ttl=62 time=1218.863 ms
64 bytes from 140.113.1.1: icmp_seq=8 ttl=62 time=208.754 ms
64 bytes from 140.113.1.1: icmp_seq=9 ttl=62 time=549.421 ms
--- 140.113.1.1 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 208.754/3878.009/8283.258/2710.495 ms
--
int i;main(){for(;i[]i;++i){--i;}];read('-'-'-',i+++hell\
o, world!\n,'/'/'/'));}read(j,i,p){write(j/p+p,i---j,i/i);}
-- IOCCC 1984
pgp0.pgp
Description: PGP signature
Re: something wrong with fxp driver ?
You might compare the dmesg output from before/after and see if there are
any obvious changes in IRQ allocation, shared interrupts, etc. Perhaps
the changes in interrupt routing have resulted in some new behavior.
Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED] Network Associates Laboratories
On Fri, 27 Jun 2003, Ying-Chieh Liao wrote:
my previous kernel is about May 10, and the fxp works fine for me
but I cvsuped and make world/kernel yesterday (6/26), and then terrible thing
happens... the connection becomes v...e...r...y... s...l...o...w...
my ping time to the gateway is about 8000ms (but sometimes 20ms)
I've browse the mail archive of -current and -net, and I've noticed some
similar problems with fxp (device timeout), and I also get this message
(fxp0 device timeout) in my dmesg output, but I cant find out any solution :
Is there any workaround, or patches ?
--
char*p=char*p=%c%s%c;main(){printf(p,34,p,34);};main(){printf(p,34,p,34);}
-- Anonymous
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: something wrong with fxp driver ?
On Fri, Jun 27, 2003 at 09:28:31 -0400, Robert Watson wrote: You might compare the dmesg output from before/after and see if there are any obvious changes in IRQ allocation, shared interrupts, etc. Perhaps the changes in interrupt routing have resulted in some new behavior. I lost my old kernel : (I make kernel twice... I thought it was scheduler problem, so I overwrite it by make another kernel ...) here's my dmesg (new, slow network kernel) Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-CURRENT #2: Fri Jun 27 11:47:35 CST 2003 [EMAIL PROTECTED]:/ad0/usr.obj/ad0/usr.src/sys/TERRY Preloaded elf kernel /boot/kernel/kernel at 0xc03c4000. Preloaded userconfig_script /boot/kernel.conf at 0xc03c41a4. Preloaded elf module /boot/kernel/if_fxp.ko at 0xc03c41f4. Preloaded elf module /boot/kernel/miibus.ko at 0xc03c42a0. Preloaded elf module /boot/kernel/random.ko at 0xc03c434c. Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 463910967 Hz CPU: Pentium III/Pentium III Xeon/Celeron (463.91-MHz 686-class CPU) Origin = GenuineIntel Id = 0x673 Stepping = 3 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 536870912 (512 MB) avail memory = 517308416 (493 MB) Pentium Pro MTRR support enabled npx0: math processor on motherboard npx0: INT 16 interface pcibios: BIOS version 2.10 Using $PIR table, 6 entries at 0xc00fdef0 pcib0: Intel 82443BX (440 BX) host to PCI bridge at pcibus 0 on motherboard pci0: PCI bus on pcib0 pci_cfgintr: 0:9 INTA BIOS irq 12 pci_cfgintr: 0:13 INTA BIOS irq 10 pci_cfgintr: 0:15 INTA BIOS irq 11 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 UDMA33 controller port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: serial bus, USB at device 7.2 (no driver attached) pci0: bridge, PCI-unknown at device 7.3 (no driver attached) ahc0: Adaptec 2940 Ultra SCSI adapter port 0xe400-0xe4ff mem 0xea02-0xea020fff irq 12 at device 9.0 on pci0 aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs fxp0: Intel 82557/8/9 EtherExpress Pro/100(B) Ethernet port 0xe800-0xe83f mem 0xea00-0xea01,0xea021000-0xea021fff irq 10 at device 13.0 on pci0 fxp0: Ethernet address 00:02:b3:99:3b:55 miibus0: MII bus on fxp0 inphy0: i82555 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci0: display, VGA at device 15.0 (no driver attached) orm0: Option ROMs at iomem 0xcd000-0xce7ff,0xc8000-0xcc7ff,0xc-0xc7fff on isa0 fdc0: Enhanced floppy controller (i82077, NE72065 or clone) at port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A unknown: PNP0303 can't assign resources (port) unknown: PNP0a03 can't assign resources (port) unknown: PNP0501 can't assign resources (port) unknown: PNP0700 can't assign resources (port) unknown: PNP0501 can't assign resources (port) Timecounters tick every 10.000 msec ata1-slave: timeout waiting for interrupt ata1-slave: ATAPI identify failed ad0: 6197MB IBM-DHEA-36481 [12592/16/63] at ata0-master UDMA33 acd0: CDROM CD-524E at ata1-master PIO3 Waiting 2 seconds for SCSI devices to settle da0 at ahc0 bus 0 target 3 lun 0 da0: IBM DNES-309170W SA30 Fixed Direct Access SCSI-3 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) Mounting root from ufs:/dev/da0s1a -- Pi seconds is a nanocentury. --- Tom Duff pgp0.pgp Description: PGP signature
Re: something wrong with fxp driver ?
On Fri, Jun 27, 2003 at 07:36:51 +0200, Kirill Ponomarew wrote:
On Fri, Jun 27, 2003 at 01:27:28PM +0800, Ying-Chieh Liao wrote:
my previous kernel is about May 10, and the fxp works fine for me
but I cvsuped and make world/kernel yesterday (6/26), and then terrible thing
happens... the connection becomes v...e...r...y... s...l...o...w...
my ping time to the gateway is about 8000ms (but sometimes 20ms)
I've browse the mail archive of -current and -net, and I've noticed some
similar problems with fxp (device timeout), and I also get this message
(fxp0 device timeout) in my dmesg output, but I cant find out any solution :
Is there any workaround, or patches ?
[just my stupid: me too]
I have the same problem. It seems that ATA is b0rken somewhere.
[/just my stupid: me too]
something related to ATA ? I'm not sure ...
but when I make buildkernel, it complains that it didnt recognize
ATA_ENABLE_ATAPI_DMA ...
--
char*p=char*p=%c%s%c;main(){printf(p,34,p,34);};main(){printf(p,34,p,34);}
-- Anonymous
pgp0.pgp
Description: PGP signature
something wrong with fxp driver ?
my previous kernel is about May 10, and the fxp works fine for me
but I cvsuped and make world/kernel yesterday (6/26), and then terrible thing
happens... the connection becomes v...e...r...y... s...l...o...w...
my ping time to the gateway is about 8000ms (but sometimes 20ms)
I've browse the mail archive of -current and -net, and I've noticed some
similar problems with fxp (device timeout), and I also get this message
(fxp0 device timeout) in my dmesg output, but I cant find out any solution :
Is there any workaround, or patches ?
--
char*p=char*p=%c%s%c;main(){printf(p,34,p,34);};main(){printf(p,34,p,34);}
-- Anonymous
pgp0.pgp
Description: PGP signature
