RE: Buffer Problems and hangs in 4.0-CURRENT..
That's not spurprising. When I tried it, Solaris 2.6 x86 didn't support full-duplex 100Base-TX on very many devices. The DEC tulip cards were one of the few that had drivers that supported full-duplex. Charles -Original Message- From: Howard Leadmon [mailto:[EMAIL PROTECTED]] Sent: Sunday, March 12, 2000 4:24 PM To: Alfred Perlstein Cc: [EMAIL PROTECTED] Subject: Re: Buffer Problems and hangs in 4.0-CURRENT.. ... I used the DEC based cards as I had seen so many people raving about them, and at least under Solaris they claim the DEC tulip based boards are the hot ticket. ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Buffer Problems and hangs in 4.0-CURRENT..
* Howard Leadmon [EMAIL PROTECTED] [000312 13:20] wrote: Hello, I am getting the following errors out of FreeBSD 4.0-CURRENT trying to run an IRC server, and was wondering if anyone had any ideas or recommended tunables I should set?? Mar 9 22:32:03 u /usr/ircd/undernet/ircd[154]: Unable to create auth socket for [@163.152.216.46]:No buffer space available Mar 9 22:32:03 u /usr/ircd/undernet/ircd[154]: Unable to create auth socket for [@208.164.193.201]:No buffer space available Mar 9 22:33:00 u syslogd: sendto: No buffer space available I'm assuming you haven't tuned a single thing, therefor you'll want to double "maxusers" in your kernel config file. It would help if you told us the configuration of the machine so that I felt comfortable giving more specific tunables without worrying about them causing other problems because of lack of RAM. -Alfred Howdy, Not a whole lot done, I had the MAXUSERS set to 128, though am about to bump it to 256 when I rebuild to see if that helps. I used to have some tunables for BSDI when I used it, but when I tried to apply them to FBSD it bitched about them being unknown so I just left them out. Was also going to move NMBCLUSTERS up to 20480, not sure if thats the solution or not. I can post the whole config if desired, but really it's very close to the GENERIC except I added SOFTUPDATES, and removed all the drivers I didn't need for my system to hopefully slim it down some.. g, you _still_ haven't even told me how much RAM is in the box and what else it does if anything. Without that kind of information I'm not too comfortable giving advice on tuneables because I DON'T KNOW WHAT I'M TUNING :), when I've just blindly told people to increase NMBCLUSTERS they've had other problems because the kernel's network buffers wired down all the machine's memory. Yes, increasing NMBLCUSTERS is a good thing, but without your configuration it's hard to say how much to increase it. -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Buffer Problems and hangs in 4.0-CURRENT..
Not a whole lot done, I had the MAXUSERS set to 128, though am about to bump it to 256 when I rebuild to see if that helps. I used to have some tunables for BSDI when I used it, but when I tried to apply them to FBSD it bitched about them being unknown so I just left them out. Was also going to move NMBCLUSTERS up to 20480, not sure if thats the solution or not. I can post the whole config if desired, but really it's very close to the GENERIC except I added SOFTUPDATES, and removed all the drivers I didn't need for my system to hopefully slim it down some.. g, you _still_ haven't even told me how much RAM is in the box and what else it does if anything. Without that kind of information I'm not too comfortable giving advice on tuneables because I DON'T KNOW WHAT I'M TUNING :), when I've just blindly told people to increase NMBCLUSTERS they've had other problems because the kernel's network buffers wired down all the machine's memory. Yes, increasing NMBLCUSTERS is a good thing, but without your configuration it's hard to say how much to increase it. -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] Sorry, thought you were asking about the kernel configs, not the hardware configs. Here is my current running config via dmesg, as I think that covers it all.. Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #3: Tue Mar 7 04:20:22 EST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/U2 Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (551.25-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x665 Stepping = 5 Features=0x183fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 402587648 (393152K bytes) config q avail memory = 387334144 (378256K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Preloaded elf kernel "kernel" at 0xc02cc000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02cc09c. Pentium Pro MTRR support enabled md0: Malloc disk 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 5 Timecounter "PIIX" frequency 3579545 Hz chip1: Intel 82371AB Power management controller port 0x5000-0x500f at device 7.3 on pci0 dc0: Intel 21143 10/100BaseTX port 0xd400-0xd47f mem 0xd541-0xd54103ff irq 17 at device 13.0 on pci0 dc0: Ethernet address: 00:c0:f0:3b:a7:eb miibus0: MII bus on dc0 ukphy0: Generic IEEE 802.3u media interface on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci0: Trident model 9660 VGA-compatible display device at 15.0 irq 16 atapci1: HighPoint HPT366 ATA66 controller port 0xe000-0xe0ff,0xdc00-0xdc03,0xd800-0xd807 irq 18 at device 19.0 on pci0 atapci2: HighPoint HPT366 ATA66 controller port 0xec00-0xecff,0xe800-0xe803,0xe400-0xe407 irq 18 at device 19.1 on pci0 fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 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 0x60-0x6f on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 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 ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppi0: Parallel I/O on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port plip0: PLIP network interface on ppbus0 APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 SMP: AP CPU #1 Launched! ad0: 8693MB ST39140A [17662/16/63] at ata0-master using UDMA33 Mounting root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted dc0: TX underrun -- increasing TX threshold Did I miss anything important you need?? --- Howard Leadmon - [EMAIL PROTECTED] - http://www.abs.net ABSnet Internet Services - Phone: 410-361-8160 - FAX: 410-361-8162 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Buffer Problems and hangs in 4.0-CURRENT..
* Howard Leadmon [EMAIL PROTECTED] [000312 13:50] wrote: Not a whole lot done, I had the MAXUSERS set to 128, though am about to bump it to 256 when I rebuild to see if that helps. I used to have some tunables for BSDI when I used it, but when I tried to apply them to FBSD it bitched about them being unknown so I just left them out. Was also going to move NMBCLUSTERS up to 20480, not sure if thats the solution or not. I can post the whole config if desired, but really it's very close to the GENERIC except I added SOFTUPDATES, and removed all the drivers I didn't need for my system to hopefully slim it down some.. g, you _still_ haven't even told me how much RAM is in the box and what else it does if anything. Without that kind of information I'm not too comfortable giving advice on tuneables because I DON'T KNOW WHAT I'M TUNING :), when I've just blindly told people to increase NMBCLUSTERS they've had other problems because the kernel's network buffers wired down all the machine's memory. Yes, increasing NMBLCUSTERS is a good thing, but without your configuration it's hard to say how much to increase it. -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] Sorry, thought you were asking about the kernel configs, not the hardware configs. Here is my current running config via dmesg, as I think that covers it all.. Copyright (c) 1992-2000 The FreeBSD Project. ... real memory = 402587648 (393152K bytes) config q avail memory = 387334144 (378256K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Did I miss anything important you need?? No that's fine, I run several machines with maxusers at 512 and NMBCLUSTERS at 32768 (although the ram is usually at 512 to a 1024), let me know if you have any problems with those settings though as I'd like to know if they are set too high for heavy load. I would also suggest using fxp cards (Intel Ether Express Pro) in the future, they are definetly my favorite. -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Buffer Problems and hangs in 4.0-CURRENT..
Copyright (c) 1992-2000 The FreeBSD Project. ... real memory = 402587648 (393152K bytes) config q avail memory = 387334144 (378256K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Did I miss anything important you need?? No that's fine, I run several machines with maxusers at 512 and NMBCLUSTERS at 32768 (although the ram is usually at 512 to a 1024), let me know if you have any problems with those settings though as I'd like to know if they are set too high for heavy load. I would also suggest using fxp cards (Intel Ether Express Pro) in the future, they are definetly my favorite. -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] I'll let you know how things pan out, but I just did a cvsup to the current code as of today, and also changed the MAXUSERS to 256, and the NMBCLUSTERS to 20480 in the current kernel. I did do a netstat -m on the box and see: u2.abs.net$ netstat -m 3798/4800/81920 mbufs in use (current/peak/max): 2179 mbufs allocated to data 1619 mbufs allocated to packet headers 784/1152/20480 mbuf clusters in use (current/peak/max) 2904 Kbytes allocated to network (70% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines Though the box is not even close to full load, that I will see later on tonight when everyone gets on to chat. I don't remember it ever having 81k mbufs available, so guess changing MAXUSERS set that one up. Anyhow I'll try and keep an eye on it, the real problem is that it just dies and needs a reboot at times, so I don't get to see if I had any failures.. :( As for the EEpro, I thought Intel had dropped that card, but maybe I am wrong. I used the DEC based cards as I had seen so many people raving about them, and at least under Solaris they claim the DEC tulip based boards are the hot ticket. Do you think the Intel board would really work that much better under FBSD, as I can always try and find one to try out.. --- Howard Leadmon - [EMAIL PROTECTED] - http://www.abs.net ABSnet Internet Services - Phone: 410-361-8160 - FAX: 410-361-8162 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Buffer Problems and hangs in 4.0-CURRENT..
* Howard Leadmon [EMAIL PROTECTED] [000312 15:56] wrote: Copyright (c) 1992-2000 The FreeBSD Project. ... real memory = 402587648 (393152K bytes) config q avail memory = 387334144 (378256K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Did I miss anything important you need?? No that's fine, I run several machines with maxusers at 512 and NMBCLUSTERS at 32768 (although the ram is usually at 512 to a 1024), let me know if you have any problems with those settings though as I'd like to know if they are set too high for heavy load. I would also suggest using fxp cards (Intel Ether Express Pro) in the future, they are definetly my favorite. -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] I'll let you know how things pan out, but I just did a cvsup to the current code as of today, and also changed the MAXUSERS to 256, and the NMBCLUSTERS to 20480 in the current kernel. I did do a netstat -m on the box and see: u2.abs.net$ netstat -m 3798/4800/81920 mbufs in use (current/peak/max): 2179 mbufs allocated to data 1619 mbufs allocated to packet headers 784/1152/20480 mbuf clusters in use (current/peak/max) 2904 Kbytes allocated to network (70% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines Though the box is not even close to full load, that I will see later on tonight when everyone gets on to chat. I don't remember it ever having 81k mbufs available, so guess changing MAXUSERS set that one up. Anyhow I'll try and keep an eye on it, the real problem is that it just dies and needs a reboot at times, so I don't get to see if I had any failures.. :( As for the EEpro, I thought Intel had dropped that card, but maybe I am wrong. I used the DEC based cards as I had seen so many people raving about them, and at least under Solaris they claim the DEC tulip based boards are the hot ticket. Do you think the Intel board would really work that much better under FBSD, as I can always try and find one to try out.. Use what works for you. Please make sure to follow up even if everything works out smoothly, it's great to hear about success stories. :) thanks, -Alfred To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Buffer Problems and hangs in 4.0-CURRENT..
* Howard Leadmon [EMAIL PROTECTED] [000312 12:51] wrote: Hello, I am getting the following errors out of FreeBSD 4.0-CURRENT trying to run an IRC server, and was wondering if anyone had any ideas or recommended tunables I should set?? Mar 9 22:32:03 u /usr/ircd/undernet/ircd[154]: Unable to create auth socket for [@163.152.216.46]:No buffer space available Mar 9 22:32:03 u /usr/ircd/undernet/ircd[154]: Unable to create auth socket for [@208.164.193.201]:No buffer space available Mar 9 22:33:00 u syslogd: sendto: No buffer space available I'm assuming you haven't tuned a single thing, therefor you'll want to double "maxusers" in your kernel config file. It would help if you told us the configuration of the machine so that I felt comfortable giving more specific tunables without worrying about them causing other problems because of lack of RAM. -Alfred To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Buffer Problems and hangs in 4.0-CURRENT..
Hello, I am getting the following errors out of FreeBSD 4.0-CURRENT trying to run an IRC server, and was wondering if anyone had any ideas or recommended tunables I should set?? Mar 9 22:32:03 u /usr/ircd/undernet/ircd[154]: Unable to create auth socket for [@163.152.216.46]:No buffer space available Mar 9 22:32:03 u /usr/ircd/undernet/ircd[154]: Unable to create auth socket for [@208.164.193.201]:No buffer space available Mar 9 22:33:00 u syslogd: sendto: No buffer space available I'm assuming you haven't tuned a single thing, therefor you'll want to double "maxusers" in your kernel config file. It would help if you told us the configuration of the machine so that I felt comfortable giving more specific tunables without worrying about them causing other problems because of lack of RAM. -Alfred Howdy, Not a whole lot done, I had the MAXUSERS set to 128, though am about to bump it to 256 when I rebuild to see if that helps. I used to have some tunables for BSDI when I used it, but when I tried to apply them to FBSD it bitched about them being unknown so I just left them out. Was also going to move NMBCLUSTERS up to 20480, not sure if thats the solution or not. I can post the whole config if desired, but really it's very close to the GENERIC except I added SOFTUPDATES, and removed all the drivers I didn't need for my system to hopefully slim it down some.. --- Howard Leadmon - [EMAIL PROTECTED] - http://www.abs.net ABSnet Internet Services - Phone: 410-361-8160 - FAX: 410-361-8162 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
