Re: systat -v on -CURRENT
Now that you mention it, Yes: ad2 is -0% busy. Disks ad0 ad2 cd0 pass0 ofodintrn KB/t 0.00 0.00 0.00 0.00 %slo-z30576 buf tps 0 0 0 0 tfree23 dirtybuf MB/s 0.00 0.00 0.00 0.00 17867 desiredvnodes % busy0-0 0 01070 numvnodes -Craig - Original Message - From: Andre Guibert de Bruet [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, April 05, 2003 5:20 PM Subject: systat -v on -CURRENT Hi, I've noticed that 'systat -v' sometimes reports a negative disk activity percentile. Has anyone else noticed this behavior? Before I look into the problem, is someone already working on a fix? Regards, Andre Guibert de Bruet | Enterprise Software Consultant Silicon Landmark, LLC. | http://siliconlandmark.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: playing mp3s and burning a cd
I see this too: when I listen to tunes and untar a file, the music plays at about .7x the speed, and sounds kind of robotic, even with xmms niced to -20, and tar/gzip at +20. I am running 5.0-CURRENT-20030320-JPSNAP, so I doubt an 'upgrade' is really going to do anything for you at this time. -Craig From: The Anarcat [EMAIL PROTECTED] Subject: playing mp3s and burning a cd I'm running 5.0-release, so I'm not sure this is the proper forum, but I'm trying my luck anyways. I used to listen to MP3s (using xmms) while burning CDs (using cdrecord) and it used to work fine on -stable. Now on 5.0-release, the music gets *slw* as soon as the massive IO gets on. I presume it's related to the interrupt problems the current branch is generally having. Anyone else seeing this? Should I upgrade to -current? A. -- Seul a un caractère scientifique ce qui peut être réfuté. Ce qui n'est pas réfutable relève de la magie ou de la mystique. - Popper, Karl To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: playing mp3s and burning a cd
Actually, on my box, all I/O devices are in DMA mode, and I'm seeing this no matter what device is doing the heavy I/O. I think this should be fixed by 5.1 because it is very annoying. A Pentium 133 in Windows 95 doesnt even do it this bad. -Craig From: Don [EMAIL PROTECTED] Should a PR be filed or some QA team contacted to make sure this problem doesn't stay alive in 5.2? :) This isn't, by chance, a problem with your setting for the sysctl hw.ata.atapi_dma is it? -Don To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Solved??? Re: playing mp3s and burning a cd
If you have a 1.0GHz Durn processor, theoretically you should be able to burn that CD at 32X (burner permitting), have 10+ Mozilla windows open, all without a skip in the playback, or boggage. I have an AMD K6-2 450, and I currently can't do 1/4 the stuff simultaneously without music skipping as I could in other, anonymous operaing systems. Also, a simple ogg123 off of the commandline skips a little as well, when untaring something. -Craig From: The Anarcat [EMAIL PROTECTED] On Mon Mar 24, 2003 at 02:14:48PM -0500, Don wrote: Should a PR be filed or some QA team contacted to make sure this problem doesn't stay alive in 5.2? :) This isn't, by chance, a problem with your setting for the sysctl hw.ata.atapi_dma is it? How extraordinarly cute! This solves it! I'm currently listening to Me, Mom and Morgentaler and burning a 4x CD without any slowdown, this is great. So I guess a workaround is to toggle DMA for my ATAPI bus. Indeed, the burner is IDE and should be working on DMA mode to get optimal performance. The thing is that atapicam hides the DMA/PIO magic from the usual boot messagesand there's therefore no way to see wether the device is in DMA mode unless you compile in both cd0 and acd0 which I heard isn't recommended... A. PS: what's the proper way to enable ATAPI DMA in the loader.conf file? I don't see any flag WRT that there.. I'm tempted to add: set hw.ata.atapi_cam=1 anywhere there... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: playing mp3s and burning a cd
Fact is, there is no CD/DVD-ROM in existence that should be capable of making anything above 900MHz skip audio when running at full stink. My AMD AthlonXP 1600+ cpu can burn a CD at 40X from the network, while playing Wolfenstein at 1024x768 in WinXP. The fact that FreeBSD can't even burn at 4-6X while running measly XMMS is totally unnacceptable and should be looked at. I would do it myself, but I'm only at the very beginnings of being able to program in C. -Craig From: Julian St. [EMAIL PROTECTED] Subject: Re: playing mp3s and burning a cd Am Mo, 2003-03-24 um 20.33 schrieb Vallo Kallaste: Now on 5.0-release, the music gets *slw* as soon as the massive IO gets on. I presume it's related to the interrupt problems the current branch is generally having. Anyone else seeing this? Should I upgrade to -current? Current isn't better. This is a long time problem and is most noticeable when you downgrade from -current to -stable... it's unforgettable feeling :-P I don't expect it will be fixed in the near future, because it's been so over a year now. Current has it's weak points and this is only one of the regressions. I remember having this problem on 5.0-RELEASE, but it was completely gone once I upgraded to -CURRENT (late february I think). Perhaps it could be interesting to know if this problem is connected to certain hardware components. (Athlon XP 2400+ (2008 MHZ), SiS board, realtek 8139B network, SB Live!, nVidia TNT2U, UDMA100 WD harddisk) Besides: my CDROM drive is working properly using PIO and UDMA33. Regards, Julian To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Squid + natd.
I have a client machine behind my FreeBSD box, which connects to the internet via NAT and Squid. I notice when downloading a file from the internet that squid cpu% goes up, which is cool and all, but natd's does as well. Is there a method using firewall rules in a specific order, or any method for that matter, that allows squid to receive it's data directly, i.e. without natd seeing http or ftp packets? I know that squid may simply be uninstalled, but I like the caching, and I hate banner ads, which I use squid to block. Thanks in advance. -Craig To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Gigabit Link slow, until downed and re-uped
My gigabit link between my Windows XP box and my FreeBSD box is always really slow after booting FreeBSD, until I go like this: ifconfig em0 down ; ifconfig em0 up ..and then I get top speed again. Ping goes from 9ms+ to 0.2ms-. This happens regardless of whether the FreeBSD box is booted first, or second, or even across reboots. However, after fixing it manually, doing a 'shutdown now' and 'exit' (right away) shows them still working fast. The only idea I have is that I tried chaning the MAC address on the FBSD box adapter, but all configuration is back to the way it was. Both cards are Intel PRO/1000MT adapters. If there is any more info that I should give, please let me know. -Craig To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Gigabit Link slow, until downed and re-uped
| My gigabit link between my Windows XP box and my FreeBSD box is always | really slow after booting FreeBSD, until I go like this: | | ifconfig em0 down ; ifconfig em0 up | | ..and then I get top speed again. Ping goes from 9ms+ to 0.2ms-. This | happens regardless of whether the FreeBSD box is booted first, or | second, or even across reboots. However, after fixing it manually, doing Are you using speed/duplex autonegotiation? Try setting both sides manually (man 4 em for details on FreeBSD). --pete I've tried that, and am still having the exact same problem. Also, looking at it in greater detail, when I do take the link down, then back up, my transfer speed from Windows XP --- FreeBSD is roughly half of what it was before the whole problem started happening. This was determined using PerformanceTest on the Windows XP box doing disk tests on a Samba share. No samba settings were changed, and disk space hasn't changed by more than about 500 megs. -Craig To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Top weirdness.
Check these out: http://chat.carleton.ca/~creyenga/1sttime.JPG http://chat.carleton.ca/~creyenga/again.JPG Pretty strange, my normally-aspirated computer is somehow using 168% of cpu. boss# uname -a FreeBSD boss.sewer.org 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Fri Mar 7 01:49:18 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/s/run/src/sys/BOSSKERN i386 Using SCHED_4BSD. -Craig To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Top weirdness.
'cc1' is _not_ a system process. How is this normal? -Craig - Original Message - From: Andre Guibert de Bruet [EMAIL PROTECTED] To: Craig Reyenga [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Saturday, March 15, 2003 19:52 Subject: Re: Top weirdness. Craig, That's the normal output of 'top -S'. Regards, Andre Guibert de Bruet | Enterprise Software Consultant Silicon Landmark, LLC. | http://siliconlandmark.com/ On Sat, 15 Mar 2003, Craig Reyenga wrote: Check these out: http://chat.carleton.ca/~creyenga/1sttime.JPG http://chat.carleton.ca/~creyenga/again.JPG Pretty strange, my normally-aspirated computer is somehow using 168% of cpu. boss# uname -a FreeBSD boss.sewer.org 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Fri Mar 7 01:49:18 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/s/run/src/sys/BOSSKERN i386 Using SCHED_4BSD. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
5.0-RC3 working great, but NOTES incomplete?
I got 5.0-RC3 working great on my box today, but when I went to make a custom kernel and read NOTES i noticed that it makes no mention of IPFIREWALL and friends. Is this intentional? craig@boss:~$ grep IPFIREWALL /sys/i386/conf/NOTES craig@boss:~$ Nothing shows up. What's the scoop? -Craig To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD 5.0 RC3 now available
I haven't actually tried 5.0RC3 yet, so what I'm about to say may be irrelevant, but here goes: One thing I noticed in previous releases is that the choice of packages is a little odd. Many small packages and ones that are not popular seem to make it on the first CD, while bigger and/or more popular ones are stuck being fetched+built manually after. This can be a pain on slower computers, especially with ports such as mozilla and openoffice. I guess what I am suggesting is that more attention be paid to _which_ ports make in onto CD #1. Perhaps one way of doing this is to give each port a pkg-priority that the release build scripts scan for. Anyways, that's just my $0.02, might be $0.00 in this case. -Craig To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD 5.0 RC3 now available
These mentioned licensing issues make sense, however I still think that there should be some sort of system to ensure big and/or popular packages to make it to CD #1. -Craig One thing I noticed in previous releases is that the choice of packages is a little odd. Many small packages and ones that are not popular seem to make it on the first CD, while bigger and/or more popular ones are stuck being fetched+built manually after. This can be a pain on slower computers, especially with ports such as mozilla and openoffice. I guess what I am suggesting is that more attention be paid to _which_ ports make in onto CD #1. Doesn't OpenOffice.Org require the Sun JDK? If so, might that be a bit of a problem due to licensing restrictions? I wouldn't see a problem with Mozilla, though. Except that it is quite, quite bloated. ;) Keith To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD 5.0 RC3 now available
No matter what, disc#1 has a finite amount of space and it's going to be impossible to come up with a combination of packages that keeps everyone happy. Sooner or later, popular comes down to somebody's judgement. To see what's currently in the package split, look at src/release/scripts/print-cdrom-packages.sh (for whatever branch interests you). Note that in addition to the packages listed there, we also need to put all of their dependencies on disc#1 as well. These dependencies likely account for a lot of the small packages and ones that are not popular seem to make in on the first CD. Looking at the script, it would appear that the current method used is simply a combination of the two different ideas. I guess now I should be saying, Please add Mozilla and Apache to the script. (FYI, the 5.0-RC3 package set occupies 339MB of a 560MB ISO image.) If the ISO is currently 560MB, then we have 90MB to spare right? -Craig To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Here's a PR for you: PR's dont send
A couple days ago, I tried to send a PR with send-pr(1), and it said PR sent although it said it quite rapidly, which made it look like that wasn't true, and sure enough the PR certainly didn't make it. Anyways, here's the PR in question: SEND-PR: BE ADVISED THAT FREEBSD PROBLEM REPORTS ARE PUBLIC INFORMATION AND SEND-PR: WILL BE PUBLISHED AS-IS ON THE PROJECT'S MAILING LISTS AND WEB SITES. SEND-PR: DO NOT SUBMIT ANY INFORMATION YOU DO NOT WANT MADE PUBLIC. SEND-PR: SEND-PR: For sensitive security issues, consider contacting the FreeBSD SEND-PR: security officer team ([EMAIL PROTECTED]) directly. SEND-PR: SEND-PR: Choose from the following categories: SEND-PR: SEND-PR: advocacy alpha bin conf docs gnu SEND-PR: i386 ia64 java kern misc ports SEND-PR: powerpc sparc64 standards www SEND-PR: To: [EMAIL PROTECTED] From: Craig R [EMAIL PROTECTED] Reply-To: Craig R [EMAIL PROTECTED] Cc: X-send-pr-version: 3.113 X-GNATS-Notify: Submitter-Id: current-users Originator:Craig R Organization: organization of PR author (multiple lines) Confidential: no FreeBSD PRs are public data Synopsis: Floppy controller won't configure on FIC VA-503+ mainboard, USB busted too Severity: serious Priority: medium Category: kern Class: sw-bug Release: FreeBSD 5.0-RC1 i386 Environment: System: FreeBSD boss.sewer.org 5.0-RC1 FreeBSD 5.0-RC1 #1: Sat Dec 14 13:04:26 E ST 2002 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/BOSSKERN i386 Description: The floppy controller doesn't configure properly on the FIC VA-503+ motherboard. This has been verified with two boards.The lines below (dmesg output) show the problem. As an aside, USB support and pci support appear to be limited as well. A Tyan S1590 mainboard worked fine, which is odd because it has the same VIA Apo llo MVP3 chipset. This PR most likely overlaps with i386/46194. This problem doesn't occur in -STABLE. How-To-Repeat: Buy the motherboard specified, and put FreeBSD 5.0-RC1 on it. This has been a problem since DP2, probably even earlier. Fix: No idea, probabaly in the fdc driver. --- 450aft1 begins here --- Copyright (c) 1992-2002 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.0-RC1 #1: Sat Dec 14 13:04:26 EST 2002 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/BOSSKERN Preloaded elf kernel /boot/kernel/kernel at 0xc03ce000. Preloaded elf module /boot/kernel/acpi.ko at 0xc03ce0a8. Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 451025647 Hz CPU: AMD-K6(tm) 3D processor (451.03-MHz 586-class CPU) Origin = AuthenticAMD Id = 0x58c Stepping = 12 Features=0x8021bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX AMD Features=0x8800SYSCALL,3DNow! real memory = 268369920 (255 MB) avail memory = 256663552 (244 MB) Initializing GEOMetry subsystem K6-family MTRR support enabled (2 registers) npx0: math processor on motherboard npx0: INT 16 interface acpi0: FICVA503P on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 Using $PIR table, 6 entries at 0xc00fdd60 acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-safe frequency 3579545 Hz ACPI-1287: *** Error: Method execution failed, AE_AML_BUFFER_LIMIT can't fetch resources for \\_SB_.PCI0.ISA_.FDC0 - AE_AML_BUFFER_LIMIT acpi_timer0: 32-bit timer at 3.579545MHz port 0x6008-0x600b on acpi0 acpi_cpu0: CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0x6080-0x60ff,0x6000-0x607f,0xcf8-0xcff on ac pi0 pci0: ACPI PCI bus on pcib0 agp0: VIA 82C597 (Apollo VP3) host to PCI bridge mem 0xe000-0xe0ff at device 0.0 on pci0 pcib1: PCIBIOS 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: VIA 82C586 ATA33 controller port 0xe000-0xe00f 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) pcib2: ACPI PCI-PCI bridge at device 7.3 on pci0 pcib2: could not get PCI interrupt routing table for \\_SB_.PCI0.VTAC - AE_NOT_F OUND pci0: couldn't attach pci bus device_probe_and_attach: pcib2 attach returned 6 rl0: RealTek 8139 10/100BaseTX port 0xe800-0xe8ff mem 0xe400-0xe4ff ir q 5 at device 8.0 on pci0 rl0: Realtek 8139B detected. Warning, this may be unstable in autoselect mode rl0: Ethernet address: 00:50:bf:5a:eb:c9 miibus0: MII bus on rl0 rlphy0: RealTek internal media interface on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ed0: NE2000 PCI Ethernet (RealTek 8029) port 0xec00-0xec1f irq 11 at device 9. 0 on pci0 ed0: address 00:60:67:3a:b1:70, type NE2000 (16 bit) pci0: display, VGA at device 10.0 (no driver attached) fdc0: cannot reserve I/O port range (1 ports) ppc0 port
Re: 80386 out of GENERIC
I can't believe this thread is still polluting the email system. 386's are old, slow, and virtually useless. I think that the time wasted on supporting junk hardware would be better spent on utilising the features and capabilities of new hardware. As someone mentioned, if you want to use crap hardware, install NetBSD. FreeBSD's goal isn't to be able to run on anything, it's to be able to run fast on specific things. With that in mind, put your 386's away, or find a different OS. I know it may be hard to part with old junk, but that's life. -Craig - Original Message - From: Leif Neland [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, December 18, 2002 02:12 Subject: Re: 80386 out of GENERIC But still, would it be impossible to have both a GENERIC and a GENERIC386 kernel in the distribution? Or is the whole system compiled in non-386 mode? Even so, if just one site. www.386.freebsd.org were having a 386-enabled version available, wouldn't that make everybody happy? Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 80386 out of GENERIC
Yes, and then make 5.0-useless-Tandy1000.iso for the other 8 guys that could use it. -Craig - Original Message - From: Johnson David [EMAIL PROTECTED] To: Terry Lambert [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, December 16, 2002 12:55 Subject: Re: 80386 out of GENERIC On Saturday 14 December 2002 08:53 pm, Terry Lambert wrote: The best answer out there is the majority has spoken, with the idea being that if you are deploying on 386 hardware, you are an embedded systems vendor, and are willing to live with the process effectively being a cross-compilation. Okay, here's a compromise solution for all those people still needing 386 support out of the box: make a 5.0-mini-386.iso image. p.s. I somehow suspect that embedded systems vendors aren't installing from the CDROM. David To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 80386 out of GENERIC
Sorry for butting in, but my $.02 is that 386's are old enough that FreeBSD, or any other OS for that matter, shouldn't wait up for them. They've gotten to the point where they are basically useless except for running older software, which was likely written for them anyways. If I had a 386 that I wanted FreeBSD on, I'd crack open the old FreeBSD 3.5 install CD's, assuming it even had a cdrom drive. I understand why people care about supporting older hardware. Reasons such as cost, and the ability to allow code bloat to _really_ manifest itself come to mind. However, a 386 is just too old for words and should be running older software with less features. -Craig - Original Message - From: Terry Lambert [EMAIL PROTECTED] To: M. Warner Losh [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Saturday, December 14, 2002 23:55 Subject: Re: 80386 out of GENERIC M. Warner Losh wrote: One problem with most 386 boxes is that they have very little memory. sysinstall is a big, bloated pig dog these days that takes more RAM than most 386 boxes have. This is true also for many 486 boxes too. So even if 386 stuff were in the default kernel, you'd likely have other issues in making sysinstall work and have to do custom hacking... Add to this that Bosko's workaround for the CPU bug with PSE/PGE includes loading the kernel at 4M rather than 1M. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Major disk problem
Actually, I then did that, and thats when it _actually_ pooched the disk -Craig - Original Message - From: Nate Lawson [EMAIL PROTECTED] To: Craig Reyenga [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, December 13, 2002 15:39 Subject: Re: Major disk problem On Thu, 12 Dec 2002, Craig Reyenga wrote: I cvsup'ed today (dec 12, about 5pm est) from DP2, and it went all fine and dandy until I went to boot into it, when it said that /usr had a bad superblock. I then went on to fsck -y it, and it says that _every_ file is an unknown type and goes on to ruin the fs. It was a UFS2 volume. I'm not sure what else to say, just that I wish this didn't happen! I guess it's back to 4.7 for me! Boot single user and do fsck_ffs -b 32 /usr -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Major disk problem
I cvsup'ed today (dec 12, about 5pm est) from DP2, and it went all fine and dandy until I went to boot into it, when it said that /usr had a bad superblock. I then went on to fsck -y it, and it says that _every_ file is an unknown type and goes on to ruin the fs. It was a UFS2 volume. I'm not sure what else to say, just that I wish this didn't happen! I guess it's back to 4.7 for me! -Craig To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Isolating the network problem (Was: Any ideas at all about network problem?)
I have tried a 3com 905 in place of the Realtek, and I can get speeds of about 3.5Mb/sec (that's still no 7.9 like I used to get). It does, however, give a few tx underrun errors at the beginning of large transfers: xl0: transmission error: 90 xl0: tx underrun, increasing tx start threshold to 120 bytes xl0: transmission error: 90 xl0: tx underrun, increasing tx start threshold to 180 bytes xl0: transmission error: 90 xl0: tx underrun, increasing tx start threshold to 240 bytes xl0: transmission error: 90 xl0: tx underrun, increasing tx start threshold to 300 bytes It should also be noted that at the beginning of this whole ordeal, I was getting speeds approximately 1/10th of what I used to get with my Realtek card. A few days ago, I removed the network cables so that I could play halflife (still havent figured out howto use NAT for this), and when I reconnected them as per normal, I've been getting 1/100th the speed! (about 80KB/sec). I bought a new cable today thinking that that was the whole problem, which it is not; the problem still exists. Anyways, the main point of this message is that I also just discovered that I can't use my floppy drive for some reason, which I find quite odd. Also, there are many kernel messages about devices not being configured and such. Here is the full output: Copyright (c) 1992-2002 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.0-DP2 #0: Fri Nov 29 02:10:15 EST 2002 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/BOSSKERN Preloaded elf kernel /boot/kernel/kernel at 0xc03d9000. Preloaded elf module /boot/kernel/acpi.ko at 0xc03d90a8. Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 350797628 Hz CPU: AMD-K6(tm) 3D processor (350.80-MHz 586-class CPU) Origin = AuthenticAMD Id = 0x58c Stepping = 12 Features=0x8021bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX AMD Features=0x8800SYSCALL,3DNow! real memory = 268369920 (255 MB) avail memory = 256626688 (244 MB) Initializing GEOMetry subsystem K6-family MTRR support enabled (2 registers) netsmb_dev: loaded npx0: math processor on motherboard npx0: INT 16 interface acpi0: FICVA503P on motherboard Using $PIR table, 6 entries at 0xc00fdd60 acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-safe frequency 3579545 Hz can't fetch resources for \\_SB_.PCI0.ISA_.FDC0 - AE_AML_BUFFER_LIMIT acpi_timer0: 32-bit timer at 3.579545MHz port 0x6008-0x600b on acpi0 acpi_cpu0: CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0x6080-0x60ff,0x6000-0x607f,0xcf8-0xcff on ac pi0 initial configuration \\_SB_.PCI0.ISA_.LNKA irq 5: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sha rable 0.8.0 \\_SB_.PCI0.ISA_.LNKB irq 10: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sha rable 0.8.1 \\_SB_.PCI0.ISA_.LNKC irq 0: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sha rable 0.8.2 \\_SB_.PCI0.ISA_.LNKD irq 0: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sha rable 0.8.3 \\_SB_.PCI0.ISA_.LNKB irq 10: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sha rable 0.9.0 \\_SB_.PCI0.ISA_.LNKC irq 0: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sha rable 0.9.1 \\_SB_.PCI0.ISA_.LNKD irq 0: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sha rable 0.9.2 \\_SB_.PCI0.ISA_.LNKA irq 5: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sha rable 0.9.3 \\_SB_.PCI0.ISA_.LNKC irq 0: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sha rable 0.10.0 \\_SB_.PCI0.ISA_.LNKD irq 0: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sha rable 0.10.1 \\_SB_.PCI0.ISA_.LNKA irq 5: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sha rable 0.10.2 \\_SB_.PCI0.ISA_.LNKB irq 10: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sha rable 0.10.3 \\_SB_.PCI0.ISA_.LNKA irq 5: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sha rable 0.7.0 \\_SB_.PCI0.ISA_.LNKB irq 10: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sha rable 0.7.1 \\_SB_.PCI0.ISA_.LNKC irq 0: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sha rable 0.7.2 \\_SB_.PCI0.ISA_.LNKD irq 0: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sha rable 0.7.3 \\_SB_.PCI0.ISA_.LNKA irq 5: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sha rable 0.1.0 \\_SB_.PCI0.ISA_.LNKB irq 10: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sha rable 0.1.1 \\_SB_.PCI0.ISA_.LNKC irq 0: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sha rable 0.1.2 \\_SB_.PCI0.ISA_.LNKD irq 0: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sha rable 0.1.3 before setting priority for links \\_SB_.PCI0.ISA_.LNKC: interrupts: 1 3 4 5 6 71011 12 1415 penalty:101100 2100 2100 1600 2100 2100 1600 1100 2100 1 1100 11100 references: 5 priority: 0 \\_SB_.PCI0.ISA_.LNKD: interrupts: 1
Re: Any ideas at all about network problem?
Unfortunately, I have no extra hardware available to me, so I can't experiment with switches and whatnot. Also, wouldn't some sort of software experimentation be more appropriate, considering that my existing setup works _perfetcly_ in 4.7? I'm not sure what to do; should I be trying various versions of if_rl.c? Or is there something else that I should be trying? -Craig - Original Message - From: Brad Knowles [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: Brad Knowles [EMAIL PROTECTED]; Craig Reyenga [EMAIL PROTECTED]; Terry Lambert [EMAIL PROTECTED]; [EMAIL PROTECTED]; Christopher J Olson [EMAIL PROTECTED] Sent: Tuesday, December 03, 2002 19:32 Subject: Re: Any ideas at all about network problem? At 12:31 PM +0200 2002/12/03, [EMAIL PROTECTED] wrote: The two machines involved are connected by a crossover cable: I've heard of lots of problems with machines using cross-over cables. Can you connect the machines through a switch, and ensure that they are hard-wired to 100Base-TX full duplex at both ends, as opposed to auto-negotiating? I'll try a different cable this evening when I get home. Is there a minimum length? The cable is currently 2m long. I'm prepared to do any other debugging people here can suggest to make it work faster. FWIW my single CPU workstaion at the office running 4.7-STABLE with an fxp0 NIC does not suffer the same throughput reduction. I've also heard of lots of problems with some machines when the cable is too short, at least in certain combinations. Try successively longer lengths of cable, at least up to 20-30m. -- Brad Knowles, [EMAIL PROTECTED] They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -Benjamin Franklin, Historical Review of Pennsylvania. GCS/IT d+(-) s:+(++): a C++(+++)$ UMBSHI$ P+++ L+ !E W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+() DI+() D+(++) G+() e++ h--- r---(+++)* z(+++) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Any ideas at all about network problem?
Sure, I'm not sure what to tell you though. If you can tell me what info you need, then I'll find it for you. I sense a small game of chicken meets egg forming here. -Craig - Original Message - From: Cliff L. Biffle [EMAIL PROTECTED] Well... My Realtek card in my 5.0 workstation is fully capable of saturating a 100mbps link. It's an 8139; the only thing I did that might have been unusual was forcing the media/mediaopts after bad experiences with rl's autodetect in the past. Perhaps if you give me more information about your setup I could better reproduce it. :-\ -Cliff L. Biffle To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Any ideas at all about network problem?
Ok, I'm convinced. Clearly I'm the one that has to do the testing because I seem to be the lucky guy with the problem. The super weird thing about all of this is that cpu usage is very minimal during transfers. The 905 card was weird too: it actually ran at 8MB/sec for about 4 sec, then the kernel gave a few TX errors and then it stayed at or below 3.7MB/sec. I have also tried my friends laptop as an alternate client and it showed identical behaviour as my usual WinXP box. My setup has no switches or anything, just a white cable. If I need to give more information, just ask and I'll try to fetch it. I've already given a full dmesg and a few other things, so I'm not sure what to say at this point. Thanks in advance, -Craig - Original Message - From: Terry Lambert [EMAIL PROTECTED] Craig Reyenga wrote: I just tried a 3com 3c905 NIC (my roommate's) and it _also_ transfers slowly (about 3.5MB/sec, so just under half of what i used to get with my realtek in -stable). It also spit out a few messages: [ ... ] I'd really rather not play around with different versions of FreeBSD to fix this problem, because this computer is where I keep all of my stuff, and with exams, I just won't have the time. Yes I know that I shouldn't be using 5.0 then but a problem is a problem and it should be fixed. Your alternative to doing the necessary binary search is to provide enough information that someone else can repeat the reduced performance you are getting with your hardware, so that they can perform the binary search on your behalf. FWIW, the root cause is likely a result of something in the last 8 months, which means log2(240)+1 = 8 compiles to find the problem on your hardware; if, in the last 2.5 years, which we know to be the case, it's log2(2.5*365)+1 = 10 compiles. You already have hardware to test the kernels out on, to see if a particular version has the problem, so you're the logical candidate to do the compiling. Given a 1GHz machine, we are probably talking about 6 hours elapsed time, given a local CVS tree, and compiling and testing occurring serially. If you don't want to do the work, you are going to have to provide a better characterization of the problem so that it can be repeated by someone who's willing to do it on your behalf, or out of curiousity; most people who could deal with it for you aren't the types to buy RealTek or 3C905 ethernet cards, which the driver comments suggest are badly designed hardware. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Any ideas at all about network problem?
Right on. I hope that you find something because right now it seems so hopeless. I'd have to say that this is the strangest problem that I've ever had with FreeBSD. -Craig - Original Message - From: Cliff L. Biffle [EMAIL PROTECTED] To: Craig Reyenga [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Monday, December 02, 2002 13:11 Subject: Re: Any ideas at all about network problem? On Monday 02 December 2002 10:47 am, Craig Reyenga wrote: Ok, I'm convinced. Clearly I'm the one that has to do the testing because I seem to be the lucky guy with the problem. I'm actually on my way to the office now to set up a test scenario with our 5-current boxen. We've got a whole scad of 8139s, 8129s, 3c905s, and some old Davicom-based cards that gave me endless trouble under 4.x. I'll let you know what I find. For reference, the 8139 in my 5-current box here works at full speed, but I'm on 10mbps; we have more 100baseT equipment at work. -Cliff L. Biffle To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Any ideas at all about network problem?
In a recent thread started by me, named Network is crazy slow in DP2 I wrote that I'm getting substantially lower speeds than I should be over my 100mbit link (realtek 8139 on both sides). I'm not going to repeat everything that I have already said in the other thread, but I'm going to re-ask if there are any ideas out there. I've tried quite a few things, including: -rebooting -enabling/disabling the link -switching between polling/non-polling mode -another client to make sure it wasn't just the XP box's fault -changing net.inet.tcp.delayed_ack to 0 from 1 -prayer -ttcp. It shows 1.3mb/sec which a 10mbit link can do. All of my dmesg info and whatnot is in the other thread that I named above. If you have ANY IDEAS for me at all, please let me know. Thanks in advance -Craig To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Any ideas at all about network problem?
It worked fine in 4.7 and all previous versions, just DP2 dunno about DP1. -Craig - Original Message - From: Terry Lambert [EMAIL PROTECTED] To: Craig Reyenga [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Sunday, December 01, 2002 23:38 Subject: Re: Any ideas at all about network problem? Craig Reyenga wrote: In a recent thread started by me, named Network is crazy slow in DP2 I wrote that I'm getting substantially lower speeds than I should be over my 100mbit link (realtek 8139 on both sides). DP1 have the problem? 4.7? cvs diff DP2 DP1? -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Any ideas at all about network problem?
I just tried a 3com 3c905 NIC (my roommate's) and it _also_ transfers slowly (about 3.5MB/sec, so just under half of what i used to get with my realtek in -stable). It also spit out a few messages: xl0: 3Com 3c905-TX Fast Etherlink XL port 0xe800-0xe83f irq 5 at device 8.0 on pci0 xl0: Ethernet address: 00:60:08:91:4c:fe miibus0: MII bus on xl0 nsphy0: DP83840 10/100 media interface on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: transmission error: 90 xl0: tx underrun, increasing tx start threshold to 120 bytes xl0: transmission error: 90 xl0: tx underrun, increasing tx start threshold to 180 bytes xl0: transmission error: 90 xl0: tx underrun, increasing tx start threshold to 240 bytes xl0: transmission error: 90 xl0: tx underrun, increasing tx start threshold to 300 bytes I'd really rather not play around with different versions of FreeBSD to fix this problem, because this computer is where I keep all of my stuff, and with exams, I just won't have the time. Yes I know that I shouldn't be using 5.0 then but a problem is a problem and it should be fixed. -Craig - Original Message - From: Terry Lambert [EMAIL PROTECTED] To: Craig Reyenga [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, December 02, 2002 00:06 Subject: Re: Any ideas at all about network problem? Craig Reyenga wrote: It worked fine in 4.7 and all previous versions, just DP2 dunno about DP1. Well, you will have to back up to a version of the source code before DP2 that didn't have the problem, perform a binary search to find the exact delta that caused the problem, and examine the code differences in order to find the problem change, and why it causes the problem. Personally, I'd start with DP1, but that's because I have a CDROM locally, and the CVS tree is not always buildable, since there is no software enforcement of buildability before a change is committed. There are almost 2 years worth of changes in the things which were not brough back to the -STABLE branches from -CURRENT, so diffing 4.7 and DP2 isn't likely to get you anywhere, I think. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Network is crazy slow in DP2
Yesterday I installed 5.0-DP2 without problems, however my 100mbit link to my desktop computer goes extremely slowly using HTTP, FTP or SMB and proabably others. I used to be able to tranfer files using FTP at over 7.9MB/sec in 4.7 but now the best that I can do is 800KB/sec. When I look at 'top' it appears that the computer isn't even trying i.e. the cpu usage is very low. The network adapter in question is a Realtek 8139B. The problem exists in polling or non-polling mode. Any ideas would be appreciated. -Craig To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Network is crazy slow in DP2
I actually don't have those options in my kernel already, and would it make _that_ much of a difference? -Craig Kris Kennaway wrote: On Fri, Nov 29, 2002 at 03:24:24PM -0500, Craig Reyenga wrote: Yesterday I installed 5.0-DP2 without problems, however my 100mbit link to my desktop computer goes extremely slowly using HTTP, FTP or SMB and proabably others. I used to be able to tranfer files using FTP at over 7.9MB/sec in 4.7 but now the best that I can do is 800KB/sec. When I look at 'top' it appears that the computer isn't even trying i.e. the cpu usage is very low. The network adapter in question is a Realtek 8139B. The problem exists in polling or non-polling mode. Any ideas would be appreciated. Try removing the WITNESS and/or WITNESS_SKIPSPIN debugging options if you want performance (at the expense of ability to catch locking bugs) Kris Name: attached attachedType: application/pgp-signature Encoding: To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Network is crazy slow in DP2
error 1:71 smb_maperror: Unmapped error 1:71 smb_maperror: Unmapped error 1:71 smb_maperror: Unmapped error 1:71 smb_maperror: Unmapped error 1:71 smb_maperror: Unmapped error 1:71 pid 89820 (conftest), uid 0: exited on signal 12 (core dumped) Kernel config: boss# cat BOSSKERN # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.369 2002/10/19 16:54:07 rwatson Exp $ machine i386 cpu I586_CPU ident BOSSKERN maxusers0 options INET#InterNETworking options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Enable FFS soft updates support options UFS_ACL #Support for access control lists options UFS_DIRHASH #Improve performance on big directories options MD_ROOT #MD is a potential root device options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem (requires PSEUDOFS) options PSEUDOFS#Pseudo-filesystem framework options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 #Compatible with FreeBSD4 options SCSI_DELAY=15000#Delay (in ms) before probing SCSI options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING #Posix P1003_1B real-time extensions options KBD_INSTALL_CDEV# install a CDEV entry in /dev # # DP2-specific Options: # # Disable certain VM optimizations as they currently cause memory corruption # on newer Pentium4 and Athlon systems. # options DISABLE_PSE options DISABLE_PG_G device isa device eisa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device vga # VGA video card driver device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc device agp # support several AGP chipsets # Floating point support - do not disable. device npx # Power management support (see NOTES for more options) #device apm # Add suspend/resume support for the i8254. device pmtimer # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer device ppi # Parallel port interface device # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device rl # RealTek 8129/8139 device ed # NE[12]000, SMC Ultra, 3c503, DS8390 cards # Pseudo devices - the number indicates how many units to allocate. device random # Entropy device device loop# Network loopback device ether # Ethernet support device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory disks # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! device bpf # Berkeley packet filter options DEVICE_POLLING options IPFIREWALL options IPFIREWALL_DEFAULT_TO_ACCEPT options IPFIREWALL_FORWARD options IPDIVERT options IPSTEALTH options ACCEPT_FILTER_DATA options ACCEPT_FILTER_HTTP options NETSMB options NETSMBCRYPTO options LIBMCHAIN options SMBFS options LIBICONV Thanks for your help. -Craig Maxime Henrion wrote: Craig Reyenga wrote: Yesterday I installed 5.0-DP2 without problems, however my 100mbit link to my desktop computer goes extremely slowly using HTTP, FTP or SMB and proabably others. I used to be able to tranfer files using FTP at over 7.9MB/sec in 4.7 but now the best that I can do is 800KB/sec. When I look
Re: Network is crazy slow in DP2
ps auwwx | grep fsck only shows the grep command itself, so there's no background fsck running. The output of top -S -I -s1 shows this when transferring a file thru FTP: last pid: 33023; load averages: 1.00, 1.00, 1.00up 0+16:47:00 19:44:30 72 processes: 2 running, 62 sleeping, 8 waiting CPU states: 0.8% user, 0.0% nice, 1.9% system, 3.7% interrupt, 93.6% idle Mem: 41M Active, 54M Inact, 50M Wired, 32K Cache, 35M Buf, 103M Free Swap: 520M Total, 196K Used, 520M Free PID USERNAME PRI NICE SIZERES STATETIME WCPUCPU COMMAND 11 root -160 0K12K RUN885:02 92.53% 92.53% idle 12 root -44 -163 0K12K WAIT19:56 2.78% 2.78% swi1: net 33009 root 40 1736K 1208K sbwait 0:00 0.18% 0.15% ftpd 33 root 200 0K12K syncer 1:50 0.05% 0.05% syncer 15 root 760 0K12K sleep0:42 0.05% 0.05% random 33008 craig 960 2148K 1180K RUN 0:00 0.00% 0.00% top I have ttcp installed now, what shall I do with it? -Craig Maxime Henrion wrote: Craig Reyenga wrote: Sure. The cards at both ends are realtek 8139B's and according to ifconfig, they have negotiated a 100mbit full-duplex link. Uploads AND downloads are slow, using HTTP, FTP and SMB. When I installed DP2, I simply copied my httpd.conf and smb.conf, so I can't imagine that configuration of the daemons is an issue. OK, I have a few more questions. Does ps or top shows that background fcsk is running while doing the transfers ? Can you install and run the ttcp program from ports which will compute raw TCP performance and will help us distinguish where the problem lies. Cheers, Maxime To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
