Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 13 Jan 2002 13:10:01 -0800 (PST)
From:      "Ted Mittelstaedt" <tedm@toybox.placo.com>
To:        freebsd-bugs@FreeBSD.org
Subject:   RE: misc/33688: Downloading some files with ftp hangs the system
Message-ID:  <200201132110.g0DLA1Z90413@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR misc/33688; it has been noted by GNATS.

From: "Ted Mittelstaedt" <tedm@toybox.placo.com>
To: "Dark0n3" <darkone@raketti.net>,
	<freebsd-gnats-submit@freebsd.org>, <ali.sahin@byd.com.tr>
Cc:  
Subject: RE: misc/33688: Downloading some files with ftp hangs the system
Date: Sun, 13 Jan 2002 13:08:24 -0800

 Hi Dark0n3 and all
 
   I'm CC'ing this feedback that was cc'd to me back to GNATS because Dark0n3
 is
 apparently using a non-standard e-mail client that is trashing the subject
 line, as a result the auto-feedback sorting mechanism of the PR system
 did not append his feedback, even though he did send it to GNATS.
 
   Dark0n3, since your problem is the system is crashing when you transfer
 large files via the loopback device, and you have checked everything else, I
 believe the problem
 you are having is centered on the use of the 3com 3c905 and the xl0 driver.
 This card has had sporatic reports of problems before (although a crash is
 unusual)
 
   Note that there are 2 versions of this card, the 3c905 and the 3c905B.
 Allegedly, the plain 905 has a super-small internal card buffer and more
 bugs.
 
   If possible please try removing the 3c905 and replacing it with a
 different manufacturer's card, or even a 3c905B and recheck the loopback FTP
 problem.
 
   Note that the following feedback is NOT on the submitters sysstem, we still
 need
 the feedback from him.
 
 
 Ted Mittelstaedt
 
 >-----Original Message-----
 >From: Dark0n3 [mailto:darkone@raketti.net]
 >Sent: Sunday, January 13, 2002 6:10 AM
 >To: freebsd-gnats-submit@freebsd.org; tedm@toybox.placo.com;
 >ali.sahin@byd.com.tr
 >Subject:
 >re:%20misc/33688:%20downloading%20some%20files%20with%20ftp%20hangs%20th
 >e%20system
 >
 >
 > I have the exactly same problem (well it doesnt freeze asap, but
 >during the transfer. No matter which client I use [tried ncftp &
 >def. ftp]). And it only occurs when transfering large files ( > 2mb)
 >
 >DMESG:
 >Copyright (c) 1992-2001 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 4.4-RELEASE #0: Sun Jan 13 09:38:24 EET 2002
 >    root@dbsd:/usr/src/sys/compile/MY
 >Timecounter "i8254"  frequency 1193182 Hz
 >Timecounter "TSC"  frequency 350797202 Hz
 >CPU: Pentium II/Pentium II Xeon/Celeron (350.80-MHz 686-class CPU)
 >  Origin = "GenuineIntel"  Id = 0x652  Stepping = 2
 >
 >Features=0x183f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MC
 A,CMOV,PAT,PSE36,MMX,FXSR>
 >real memory  = 268369920 (262080K bytes)
 >config> di sn0
 >config> di lnc0
 >config> di ie0
 >config> di cs0
 >config> q
 >avail memory = 258412544 (252356K bytes)
 >Preloaded elf kernel "kernel" at 0xc02e3000.
 >Preloaded userconfig_script "/boot/kernel.conf" at 0xc02e309c.
 >Pentium Pro MTRR support enabled
 >md0: Malloc disk
 >Using $PIR table, 6 entries at 0xc00fdd10
 >npx0: <math processor> on motherboard
 >npx0: INT 16 interface
 >pcib0: <Intel 82443BX (440 BX) host to PCI bridge> on motherboard
 >pci0: <PCI bus> on pcib0
 >pcib1: <Intel 82443BX (440 BX) PCI-PCI (AGP) bridge> at device 1.0 on pci0
 >pci1: <PCI bus> on pcib1
 >isab0: <Intel 82371AB PCI to ISA bridge> at device 7.0 on pci0
 >isa0: <ISA bus> on isab0
 >atapci0: <Intel PIIX4 ATA33 controller> port 0xf000-0xf00f at device
 >7.1 on pci0
 >ata0: at 0x1f0 irq 14 on atapci0
 >pci0: <Intel 82371AB/EB (PIIX4) USB controller> at 7.2 irq 11
 >chip1: <Intel 82371AB Power management controller> port
 >0x5000-0x500f at device 7.3 on pci0
 >xl0: <3Com 3c905-TX Fast Etherlink XL> port 0x9400-0x943f irq 12 at
 >device 11.0 on pci0
 >xl0: Ethernet address: Somewhat hidden
 >miibus0: <MII bus> on xl0
 >nsphy0: <DP83840 10/100 media interface> on miibus0
 >nsphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 >pci0: <ATI Mach64-GU graphics accelerator> at 12.0 irq 10
 >orm0: <Option ROM> at iomem 0xc0000-0xc7fff on isa0
 >fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
 >fdc0: FIFO enabled, 8 bytes threshold
 >atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
 >atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
 >kbd0 at atkbd0
 >vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
 >sc0: <System console> at flags 0x100 on isa0
 >sc0: VGA <16 virtual consoles, flags=0x300>
 >ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
 >ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
 >plip0: <PLIP network interface> on ppbus0
 >lpt0: <Printer> on ppbus0
 >lpt0: Interrupt-driven port
 >ppi0: <Parallel I/O> on ppbus0
 >ad0: 12419MB <ST313032A> [25232/16/63] at ata0-master UDMA33
 >Mounting root from ufs:/dev/ad0s1a
 >WARNING: / was not properly dismounted
 >
 >
 >1) Run the following stress-testing utilities on the system per
 >their directions:
 >bonnie:  OK
 >iozone: OK
 >cpuburn: OK
 >nettest: OK
 >nttcp: (inetd proggy, blah) Force ping goes 10mb/sec.. so ok (also
 >no probs with ssh/sftp either)
 >
 >2) FTP into your own system via the loopback device (127.0.0.1) and
 >do multiple "gets" and "puts" to see if that crashes the system..
 >CRASH on gets.
 >
 >3) does the sysem hang on only getting files or both getting and putting?
 >Get only...
 >
 >Had RH7.0 on the box (only changed the harddrive to bigger) & it
 >_was_ stable.
 >
 >I tried following stuff:
 > Bios update
 > Switched mem chips
 > Bios reset
 > Reinstall
 > Recompiled kernel & disabled unneccessary stuff
 > Manually set new irqs for devices
 > Changed pci slot for nic & disp adapter.
 > Another CPU
 > Made sure there was space on root device
 >
 >I bet this wont help much, but you can always contact me via email
 >for more info.
 >
 >
 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200201132110.g0DLA1Z90413>