dummynet -- changing scheduler resets pipe bw ?
I have been reading the ipfw man pages and /usr/src/sys/netinet/ipfw/dummynet.txt to try to better understand how to set up queues/pipes/schedulars/flows. I noticed something odd... changing the sched type [a] doesn't seem to change the type away from WF2Q+ [b] resets the bw to 'unlimited' Maybe I don't have qfq? Rudy Output: 158 ipfw -v pipe 5 show answer for cmd 130, len 4096 5: 6.000 Mbit/s0 ms burst 0 q131077 50 sl. 0 flows (1 buckets) sched 65541 weight 0 lmax 0 pri 0 droptail sched 65541 type FIFO flags 0x0 0 buckets 0 active 159 ipfw pipe 5 config sched qfq 160 ipfw -v pipe 5 show answer for cmd 130, len 4096 5: unlimited 0 ms burst 0 q131077 50 sl. 0 flows (1 buckets) sched 65541 weight 0 lmax 0 pri 0 droptail sched 65541 type FIFO flags 0x0 0 buckets 0 active 161 ipfw pipe 5 config bw 6Mbit/s 162 ipfw -v pipe 5 show answer for cmd 130, len 4096 5: 6.000 Mbit/s0 ms burst 0 q131077 50 sl. 0 flows (1 buckets) sched 65541 weight 0 lmax 0 pri 0 droptail sched 65541 type FIFO flags 0x0 0 buckets 0 active 166 ipfw sched list 1: 21.000 Mbit/s0 ms burst 0 sched 1 type WF2Q+ flags 0x0 0 buckets 0 active 2: 21.000 Mbit/s0 ms burst 0 sched 2 type WF2Q+ flags 0x0 0 buckets 0 active 3: 6.000 Mbit/s0 ms burst 0 sched 3 type WF2Q+ flags 0x0 0 buckets 0 active 4: 12.000 Mbit/s0 ms burst 0 sched 4 type WF2Q+ flags 0x0 0 buckets 0 active 5: 6.000 Mbit/s0 ms burst 0 sched 5 type WF2Q+ flags 0x0 0 buckets 1 active Children flowsets: 5 0 ip 0.0.0.0/0 0.0.0.0/0 19389008 15491784384 204 174119 1090892 00022: 12.000 Mbit/s0 ms burst 0 sched 22 type WF2Q+ flags 0x0 0 buckets 0 active Children flowsets: 23 167 ipfw pipe 5 config sched qfq 168 ipfw sched list 1: 21.000 Mbit/s0 ms burst 0 sched 1 type WF2Q+ flags 0x0 0 buckets 0 active 2: 21.000 Mbit/s0 ms burst 0 sched 2 type WF2Q+ flags 0x0 0 buckets 0 active 3: 6.000 Mbit/s0 ms burst 0 sched 3 type WF2Q+ flags 0x0 0 buckets 0 active 4: 12.000 Mbit/s0 ms burst 0 sched 4 type WF2Q+ flags 0x0 0 buckets 0 active 5: unlimited 0 ms burst 0 sched 5 type WF2Q+ flags 0x0 0 buckets 1 active Children flowsets: 5 0 ip 0.0.0.0/0 0.0.0.0/0 19449511 15527760672 00 1095037 00022: 12.000 Mbit/s0 ms burst 0 sched 22 type WF2Q+ flags 0x0 0 buckets 0 active Children flowsets: 23 FreeBSD jejen.monkeybrains.net 8.1-STABLE FreeBSD 8.1-STABLE #2: Wed Oct 20 15:55:41 PDT 2010 r...@pulga.monkeybrains.net:/usr/obj/usr/src/sys/JEJEN amd64 strings /boot/kernel/dummynet.ko.symbols | head -1 $FreeBSD: src/sys/netinet/ipfw/ip_dummynet.c,v 1.5.2.3 2010/03/23 09:58:59 luigi Exp $ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
KVM tips for bsd as guest?
Downloaded iso, but qemu barfs when trying to install --- loads kernel but panics during boot of 7.2 ( and 8.0-rc3) install ISOs. I am trying to set up a bsd guest ... Host OS is debian. Virtualbox installed no problem. I am looking for a general how-to if there is one out there( tried searching didn't find it). Rudy -- MonkeyBrains.net -- Rudy 415.425.9825 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Tunnel IPv6 requests to my IPv4 servers?
That said, I'll add my voice to the suggestion that it is very simple to get IPv6 going on pretty much anything Hmmm... half the boxes I host, I don't have a login to, yet for some odd reason, I want to make my network 100% IPv6 accessible. I manage two /22's so, I'm sitting on a pile of IPs. First off, I'm going to get a one-to-one mapping setup for every IP -- hopefully through 6tunnel (I'll look into that, thanks for the pointer). Second, I'll migrate to multiple IPs on boxes that I have access to / boxes that support IPv6. (Example: Pre FreeBSD 7.2 box jails only support one IP) Goal: 100% IPv6 ready, whether my customers want it or not! Rudy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Tunnel IPv6 requests to my IPv4 servers?
I got my first IPv6 from ARIN. I set up my router and am successfully advertising my IPv6 block. On my DNS server, I added an IPv6 IP, no problem (try pinging! ns1.monkeybrains.net). Now, I'd like to 'NAT' to some older boxes and not mess with actually putting IPv6 IPs on those boxes. Say I had a box with running IPv4 with: 69.147.83.40 How would I 'nat' or 'gif' or 'tunnel' from a NAT box without putting any IPv6 on 69.147.83.40? I want to have: 2607:f598:0:1::666 on my 'firewall' and have it tunnel to 69.147.83.40 or whatever I've read this: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-ipv6.html But that seems more geared toward getting IPv6 on clients. Rudy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: em0 watchdog timeouts
Finally, while doing some comparisons, I realized that the motherboard having the problem was _not_ the same as the others; it was similar, but not identical. This is a good piece of info. I can try swapping out the MB and see what happens. I do want to add: thank you Jack for all your help and if does turn out to be the MB, then double thanks. Viva Monday! :) What would be nice would be MORE info for a watchdog timeout... maybe a sysctl dev.watchdog.debug=1 or something where when a watchdog event happened --- for whatever driver --- a bunch of stats were dumped relating to the event. Rudy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: em0 watchdog timeouts
BTW, I've always been somewhat dissatisfied with the watchdog design and think its kinda flawed, I could try and make you an experimental with debug and some changes that you can try if you'd like. I'm game -- it would be nice if the machine still reset the watchdog in 3 seconds and didn't cause any more damage from the debug code (eg a panic). :) My frequency of watchdog events is about 2 or 3 times per day. I am running: Intel(R) PRO/1000 Network Connection 6.9.12 Rudy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: em0 watchdog timeouts
I noticed something interesting. I set the rc_int_delay to 0: sysctl dev.em.5.rx_int_delay=0 Chcking via sysctl dev.em.5.debug=1 shows ex_int_delay is indeed 0: Oct 1 17:32:41 mango kernel: em5: rx_int_delay = 0, rx_abs_int_delay = 66 After a watchdog event, sysctl dev.em.5.debug=1 shows ex_int_delay is now 32: Oct 2 11:29:49 mango kernel: em5: rx_int_delay = 32, rx_abs_int_delay = 66 However, running sysctl dev.em.5 shows it as 0: dev.em.5.rx_int_delay: 0 dev.em.5.tx_int_delay: 66 Seems like the adapter and the kernel don't agree on the rx_int_delay value. Rudy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: em0 watchdog timeouts
Ah, I'll stop messing with them. I just set them all to 0 to see if that will help and noticed the card was leaving tx_int_delay=1. # sysctl dev.em.4.debug=1 Oct 2 13:26:07 mango kernel: em4: tx_int_delay = 1, tx_abs_int_delay = 0 Oct 2 13:26:07 mango kernel: em4: rx_int_delay = 0, rx_abs_int_delay = 0 # sysctl dev.em.4 dev.em.4.%desc: Intel(R) PRO/1000 Network Connection 6.9.12 dev.em.4.rx_int_delay: 0 dev.em.4.tx_int_delay: 0 dev.em.4.rx_abs_int_delay: 0 dev.em.4.tx_abs_int_delay: 0 Splitting traffic to different ports has brought down the watchdog events to once a day. ... essentially, I have a quad 30Mbps (not quad 1Gbps) card. heheh. Would turning off net.inet.ip.fastforwarding or any other setting help? Today, I set net.inet.ip.fw.enable=0 and I'll see if that helps. I have a feeling that isn't related to the NIC at all, but I'm not sure what else to try. Rudy Jack Vogel wrote: Watchdog resets the adapter. Messing with these values is of dubious value anyway. Jack On Fri, Oct 2, 2009 at 11:36 AM, Rudy cra...@monkeybrains.net wrote: I noticed something interesting. I set the rc_int_delay to 0: sysctl dev.em.5.rx_int_delay=0 Chcking via sysctl dev.em.5.debug=1 shows ex_int_delay is indeed 0: Oct 1 17:32:41 mango kernel: em5: rx_int_delay = 0, rx_abs_int_delay = 66 After a watchdog event, sysctl dev.em.5.debug=1 shows ex_int_delay is now 32: Oct 2 11:29:49 mango kernel: em5: rx_int_delay = 32, rx_abs_int_delay = 66 However, running sysctl dev.em.5 shows it as 0: dev.em.5.rx_int_delay: 0 dev.em.5.tx_int_delay: 66 Seems like the adapter and the kernel don't agree on the rx_int_delay value. Rudy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: em0 watchdog timeouts
I have rxd and txd set to 1024. How high can I safely go? # add more descriptors to em devices. hw.em.rxd=1024 hw.em.txd=1024 ### other settings... I have tried rx_int_delay=0 and 32 ... doesn't seem to make the watchdogs go away. dev.em.4.rx_int_delay: 32 dev.em.4.tx_int_delay: 66 dev.em.4.rx_abs_int_delay: 66 dev.em.4.tx_abs_int_delay: 66 dev.em.4.rx_processing_limit: 300 I am using a PCI-Express (x8) PCI-e slot according to the motherboard specs: http://supermicro.com/products/motherboard/Xeon3000/3210/X7SBi.cfm Rudy Jack Vogel wrote: Increase the size of your TX ring, meaning the number of TX descriptors. You said this is a quad port card, what size PCI E slot are you in? On some motherboards slot connectors might suggest its of a certain size but its not really wired fully. If you are not in a x8 lane slot move it to one. What about system tuning? Some ideas, let me know how it goes. Jack On Wed, Sep 30, 2009 at 3:28 PM, Rudy cra...@monkeybrains.net wrote: Rudy wrote: Rudy wrote: I am having watchdog timeout issues Oh, here is some more info from 'pciconf -lcv'. I offloaded half the traffic from em0 to em5 and there has only been one watchdog timeout today (on em5) vs. 10 watchdog timeouts yesterday. We do streaming out of our network and the 3 second outage really messes things up... e...@pci0:5:0:0: class=0x02 card=0x10a48086 chip=0x10a48086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' device = '82571EB Gigabit Ethernet Controller' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x4(x4) e...@pci0:5:0:1: class=0x02 card=0x10a48086 chip=0x10a48086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' device = '82571EB Gigabit Ethernet Controller' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x4(x4) e...@pci0:6:0:0: class=0x02 card=0x10a48086 chip=0x10a48086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' device = '82571EB Gigabit Ethernet Controller' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x4(x4) e...@pci0:6:0:1: class=0x02 card=0x10a48086 chip=0x10a48086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' device = '82571EB Gigabit Ethernet Controller' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x4(x4) e...@pci0:13:0:0:class=0x02 card=0x108c15d9 chip=0x108c8086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = '82573E Intel Corporation 82573E Gigabit Ethernet Controller (Copper)' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1) e...@pci0:15:0:0:class=0x02 card=0x109a15d9 chip=0x109a8086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '82573L Intel PRO/1000 PL Network Adaptor' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1) vgap...@pci0:17:3:0:class=0x03 card=0xd18015d9 chip=0x515e1002 rev=0x02 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: em0 watchdog timeouts
I have a quad card in a PCIe 8x port, and there are 2 ports on the motherboard. I just read the manual and see that the on board ports are PCIe 1x. I have been seeing watchdog events on the onboard ports as well as on the PCIe card. The router is doing roughly 50Mbps on em0, em4 em5. Does i386 vs amd64 make any difference to the em0 driver? bumping TX Ring to 2048. grep em /boot/loader.conf if_em_load=YES hw.em.rxd=2048 hw.em.txd=2048 Rudy You said this is a quad port card, what size PCI E slot are you in? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: em0 watchdog timeouts
What about system load, perhaps something is bogging the thing down so that it cannot adequately service the network interrupts?? Hardly anything is running on the box... Only things on the box: zebra bgpd (3 peers...) sshd snmpd Here is the top of 'top': load averages: 0.06, 0.08, 0.07 up 7+01:08:16 17:26:39 15 processes: 1 running, 14 sleeping CPU: 0.0% user, 0.0% nice, 4.5% system, 0.0% interrupt, 95.5% idle Mem: 193M Active, 42M Inact, 156M Wired, 196K Cache, 83M Buf, 1610M Free The specs of the motherboard are respectable, how much memory does it have? Another thought, are you using the out-of-band management features (like IPMI)? If you are not then go into the BIOS and disable that stuff. No IPMI card added to that motherboard (you have to add a daughter card). Have you run netstat or some other resource monitor to see if you run out of anything that might coincide with the watchdogs... What should I look for? # netstat -s 4105/4610/8715 mbufs in use (current/cache/total) 4103/2303/6406/25600 mbuf clusters in use (current/cache/total/max) 4103/2297 mbuf+clusters out of packet secondary zone in use (current/cache) 0/44/44/12800 4k (page size) jumbo clusters in use (current/cache/total/max) 0/0/0/6400 9k jumbo clusters in use (current/cache/total/max) 0/0/0/3200 16k jumbo clusters in use (current/cache/total/max) 9232K/5934K/15166K bytes allocated to network (current/cache/total) 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) 0/0/0 requests for jumbo clusters denied (4k/9k/16k) 0/6/6656 sfbufs in use (current/peak/max) 0 requests for sfbufs denied 0 requests for sfbufs delayed 0 requests for I/O initiated by sendfile 0 calls to protocol drain routines Are there specific router-only tunings that may help? Here are my sysctl settings: kern.ipc.somaxconn=256 kern.random.sys.harvest.interrupt=0 kern.random.sys.harvest.ethernet=0 kern.ipc.nmbcluster=32768 net.inet.icmp.icmplim=1000 net.inet.ip.fastforwarding=1 net.inet.ip.intr_queue_maxlen=92 net.inet.icmp.drop_redirect=1 dev.em.0.rx_processing_limit=200 dev.em.1.rx_processing_limit=200 dev.em.2.rx_processing_limit=200 #dev.em.4.rx_processing_limit=200 # test setting processing limit up to 300 dev.em.4.rx_processing_limit=300 dev.em.5.rx_processing_limit=200 Thanks, Rudy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: em0 watchdog timeouts
Rudy wrote: I am having watchdog timeout issues with my Intel 82573 Pro/1000 ... http://lists.freebsd.org/pipermail/freebsd-net/2008-May/018075.html link to dcgdis.zip didn't work. Do you have a copy? Thanks, Jack. Got the file and flashed -- no upgrade needed. So, while the router was offline, I flashed the motherboards bios (Supermicro X7Sbi), upgraded to 7.2-STABLE, and downloaded the 6.9.12 version of the em driver. Still, watchdog timeouts. Sigh. Will the Intel Gigabit ET Quad Port Adapter make my the timeouts go away??? Should I be using amd64??? Should tx_int_delay=0? Summary: 2 Nics on Motherboard + quad card in PCIe slot. Watchdog timeouts on motherboard nics and on quad card nic when bandwidth 10Mbps There is minimal (bgp session) TCP to the box... it only forwards packets between interfaces. # uname -r -m 7.2-STABLE i386 # dmesg | grep ^em em0: Intel(R) PRO/1000 Network Connection 6.9.12 port 0x2000-0x201f mem 0xd022-0xd023,0xd020-0xd021 irq 16 at device 0.0 on pci5 em0: Using MSI interrupt em0: [FILTER] em0: Ethernet address: 00:15:17:78:99:70 em1: Intel(R) PRO/1000 Network Connection 6.9.12 port 0x2020-0x203f mem 0xd026-0xd027,0xd024-0xd025 irq 17 at device 0.1 on pci5 em1: Using MSI interrupt em1: [FILTER] em1: Ethernet address: 00:15:17:78:99:71 em2: Intel(R) PRO/1000 Network Connection 6.9.12 port 0x3000-0x301f mem 0xd032-0xd033,0xd030-0xd031 irq 17 at device 0.0 on pci6 em2: Using MSI interrupt em2: [FILTER] em2: Ethernet address: 00:15:17:78:99:72 em3: Intel(R) PRO/1000 Network Connection 6.9.12 port 0x3020-0x303f mem 0xd036-0xd037,0xd034-0xd035 irq 18 at device 0.1 on pci6 em3: Using MSI interrupt em3: [FILTER] em3: Ethernet address: 00:15:17:78:99:73 em4: Intel(R) PRO/1000 Network Connection 6.9.12 port 0x4000-0x401f mem 0xd040-0xd041 irq 16 at device 0.0 on pci13 em4: Using MSI interrupt em4: [FILTER] em4: Ethernet address: 00:30:48:67:14:50 em5: Intel(R) PRO/1000 Network Connection 6.9.12 port 0x5000-0x501f mem 0xd050-0xd051 irq 17 at device 0.0 on pci15 em5: Using MSI interrupt em5: [FILTER] em5: Ethernet address: 00:30:48:67:14:51 # vmstat -i interrupt total rate irq1: atkbd0 710 0 irq4: sio0 3 0 irq23: atapci0 14943 0 cpu0: timer929753417 2000 irq256: em0702754836 1511 irq257: em12 0 irq260: em4469338728 1009 irq261: em5 78605337169 cpu1: timer929753403 2000 Total 3110221379 6690 # sysctl dev.em.0.stats=1 Sep 30 01:08:20 mango kernel: em0: Excessive collisions = 0 Sep 30 01:08:20 mango kernel: em0: Sequence errors = 0 Sep 30 01:08:20 mango kernel: em0: Defer count = 0 Sep 30 01:08:20 mango kernel: em0: Missed Packets = 101469 Sep 30 01:08:20 mango kernel: em0: Receive No Buffers = 0 Sep 30 01:08:20 mango kernel: em0: Receive Length Errors = 0 Sep 30 01:08:20 mango kernel: em0: Receive errors = 0 Sep 30 01:08:20 mango kernel: em0: Crc errors = 0 Sep 30 01:08:20 mango kernel: em0: Alignment errors = 0 Sep 30 01:08:20 mango kernel: em0: Collision/Carrier extension errors = 0 Sep 30 01:08:20 mango kernel: em0: RX overruns = 0 Sep 30 01:08:20 mango kernel: em0: watchdog timeouts = 15 Sep 30 01:08:20 mango kernel: em0: RX MSIX IRQ = 0 TX MSIX IRQ = 0 LINK MSIX IRQ = 0 Sep 30 01:08:20 mango kernel: em0: XON Rcvd = 0 Sep 30 01:08:20 mango kernel: em0: XON Xmtd = 0 Sep 30 01:08:20 mango kernel: em0: XOFF Rcvd = 0 Sep 30 01:08:20 mango kernel: em0: XOFF Xmtd = 0 Sep 30 01:08:20 mango kernel: em0: Good Packets Rcvd = 1056196797 Sep 30 01:08:20 mango kernel: em0: Good Packets Xmtd = 1088726903 Sep 30 01:08:20 mango kernel: em0: TSO Contexts Xmtd = 4088 Sep 30 01:08:20 mango kernel: em0: TSO Contexts Failed = 0 # sysctl dev.em.0.debug=1 Sep 30 01:34:59 mango kernel: em0: Adapter hardware address = 0xc5159420 Sep 30 01:34:59 mango kernel: em0: CTRL = 0x401c0241 RCTL = 0x8002 Sep 30 01:34:59 mango kernel: em0: Packet buffer = Tx=16k Rx=32k Sep 30 01:34:59 mango kernel: em0: Flow control watermarks high = 30720 low = 29220 Sep 30 01:34:59 mango kernel: em0: tx_int_delay = 66, tx_abs_int_delay = 66 Sep 30 01:34:59 mango kernel: em0: rx_int_delay = 0, rx_abs_int_delay = 66 Sep 30 01:34:59 mango kernel: em0: fifo workaround = 0, fifo_reset_count = 0 Sep 30 01:34:59 mango kernel: em0: hw tdh = 980, hw tdt = 980 Sep 30 01:34:59 mango kernel: em0: hw rdh = 203, hw rdt = 202 Sep 30 01:34:59 mango kernel: em0: Num Tx descriptors avail = 1024 Sep 30 01:34:59 mango kernel: em0: Tx Descriptors not avail1 = 0 Sep 30 01:34:59 mango kernel: em0: Tx Descriptors not avail2 = 0 Sep 30 01:34:59 mango kernel: em0: Std mbuf failed = 0 Sep 30 01:34:59 mango kernel: em0: Std mbuf cluster
Re: em0 watchdog timeouts
Stefan Krueger wrote: In muc.lists.freebsd.stable, you wrote: Rudy wrote: I am having watchdog timeout issues with my Intel 82573 Pro/1000 ... http://lists.freebsd.org/pipermail/freebsd-net/2008-May/018075.html link to dcgdis.zip didn't work. Do you have a copy? Thanks, Jack. Got the file and flashed -- no upgrade needed. So, while the router was offline, I flashed the motherboards bios (Supermicro X7Sbi), upgraded to 7.2-STABLE, and downloaded the 6.9.12 version of the em driver. Still, watchdog timeouts. Sigh. Hi Rudy, may I ask which clients have access to your FreeBSD 7.2 server? None. It is a router and has minimal services on it (bgpd / zebra / snmpd). Rudy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: em0 watchdog timeouts
Rudy wrote: Rudy wrote: I am having watchdog timeout issues Oh, here is some more info from 'pciconf -lcv'. I offloaded half the traffic from em0 to em5 and there has only been one watchdog timeout today (on em5) vs. 10 watchdog timeouts yesterday. We do streaming out of our network and the 3 second outage really messes things up... e...@pci0:5:0:0: class=0x02 card=0x10a48086 chip=0x10a48086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' device = '82571EB Gigabit Ethernet Controller' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x4(x4) e...@pci0:5:0:1: class=0x02 card=0x10a48086 chip=0x10a48086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' device = '82571EB Gigabit Ethernet Controller' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x4(x4) e...@pci0:6:0:0: class=0x02 card=0x10a48086 chip=0x10a48086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' device = '82571EB Gigabit Ethernet Controller' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x4(x4) e...@pci0:6:0:1: class=0x02 card=0x10a48086 chip=0x10a48086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' device = '82571EB Gigabit Ethernet Controller' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x4(x4) e...@pci0:13:0:0: class=0x02 card=0x108c15d9 chip=0x108c8086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = '82573E Intel Corporation 82573E Gigabit Ethernet Controller (Copper)' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1) e...@pci0:15:0:0: class=0x02 card=0x109a15d9 chip=0x109a8086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '82573L Intel PRO/1000 PL Network Adaptor' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1) vgap...@pci0:17:3:0: class=0x03 card=0xd18015d9 chip=0x515e1002 rev=0x02 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
em0 watchdog timeouts -- looking for dcgdis.zip
I am having watchdog timeout issues with my Intel 82573 Pro/1000 ... http://lists.freebsd.org/pipermail/freebsd-net/2008-May/018075.html link to dcgdis.zip didn't work. Do you have a copy? Thanks in advance, Rudy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
ZFS jumps from slice to partition on upgrade (???)
I just bumped from: FreeBSD 7.2-PRERELEASE #1: Wed Mar 18 00:55:27 PDT 2009 to: FreeBSD 7.2-STABLE #2: Wed Jun 10 18:27:30 PDT 2009 I rebooted and my zpool was WHACK'd. I was getting these errors in /var/log/messages: Jun 11 16:54:55 crepe3 root: ZFS: vdev I/O failure, zpool=tank path=/dev/ad6s2c offset=481721292800 size=1024 error=5 Jun 11 16:54:55 crepe3 root: ZFS: vdev I/O failure, zpool=tank path=/dev/ad6s2c offset=481721293824 size=1024 error=5 I had ad0s2 and ad6s2 in my zpool mirror, but after the upgrade zfs read the devices as: ad0s2 and ad6s2c. So I dropped the 'c' parition and reattached the slice: # zpool detach tank ad6s2c # zpool attach tank ad0s2 ad6s2 and now my 'zpool status' shows it resilvering... pool: tank state: ONLINE status: One or more devices is currently being resilvered. The pool will continue to function, possibly in a degraded state. action: Wait for the resilver to complete. scrub: resilver in progress for 0h22m, 21.91% done, 1h21m to go config: NAMESTATE READ WRITE CKSUM tankONLINE 0 0 0 mirrorONLINE 0 0 0 ad0s2 ONLINE 0 0 0 82.2M resilvered ad6s2 ONLINE 0 0 0 19.0G resilvered QUESTION: Why the heck would ZFS latch onto ad6s2c partition instead of the ad6s2 slice? I've rebooted many times before without issue... it seems the upgrade bonk'd things. Hopefully when this is all done, I can run zfs upgrade... anyone have trouble with zfs upgrade? Rudy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS jumps from slice to partition on upgrade (???)
History for 'tank': 2008-01-17.23:07:08 zpool create tank mirror ad0s2 ad8s2 2008-01-17.23:40:35 zfs create -o quota=100g tank/test.monkeybrains.net ... many more creates/deletes ... then the zfs freakout ... 2009-06-11.16:43:33 zpool clear tank 2009-06-11.16:43:59 zpool scrub tank 2009-06-11.16:48:58 zpool scrub -s tank 2009-06-11.16:54:56 zpool detach tank ad6s2c 2009-06-11.16:55:57 zpool attach tank ad0s2 ad6s2 Maybe having the device jump from ad8s2 to ad6s2 freaked out zfs? Any thoughts, or will the Internet tube swallow this post silently? Rudy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Q: eSATA Hot Swap supported?
Bruce Simpson wrote: Does FreeBSD 7.1 support eSATA hot swappable disks? Answer: Yes. I have a hot-swap case and can swap my internal SATA disks. Your eSATA's show up as 'ad' devices, correct? You may need to run atacontrol to get the drives to show up after you hot-plug them. atacontrol list *find the channel* atacontrol attach ata3 (or whatever number...) man atacontrol for lots of useful info. Rudy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: more zfs/nfs panics
it just seems to delay the panic though, it smells like some memory leak ... Well, the canonical fix seems be to DECREASE vfs.zfs.arc_max to something like 100M and keep decreasing until it works. More info here: http://wiki.freebsd.org/ZFSQuickStartGuide Once you tune, your problems will go away. The default install should not need tuning (so people stop posting this panic problem)... will that be fixed in the next stable release? Rudy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
(actually ZFS) Re: Will XFS be adopted
martinko wrote: Bartosz Stec wrote: Well it's not simple indeed. I use ZFS on my home (not critical) box (RAIDZ1). After 4 weeks uptime with varied workload I assumed it's stable. Unfortunately ZFS crashed next week ;) How did it crash ? Just the system went down or did you lose any data ? Read my previous email on tuning your system so ZFS doesn't crash. I'm planning to build new home server and put all my valuable data on ZFS but after reading all the mailing lists I'm not so sure about it. :( I've been using it on a shared machine with hundreds of customers for over 8 months. It has worked flawlessly. People who complain about the crashes often have not searched the net for: freebsd zfs tuning. Speaking of losing data on a ZFS system, I haven't yet (knock on wood) had a disk failure. Anyone have a disk failure occur and have an easy/hard time replacing the bad disk? Rudy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
(actually ZFS discussion) Re: Will XFS be adopted
Well it's not simple indeed. I use ZFS on my home (not critical) box (RAIDZ1). After 4 weeks uptime with varied workload I assumed it's stable. Unfortunately ZFS crashed next week ;) Tune your system for ZFS and the crashes will go away. Read this: http://wiki.freebsd.org/ZFSTuningGuide A running system with ZFS caches a lot of disk access (making it really fast for some applications). WHen you run the 'top' command, you will see that WIRED amount of ram is higher than a system without ZFS. Mem: 161M Active, 114M Inact, 639M Wired, 1084K Cache, 199M Buf, 1086M Free What applications will benefit from ZFS? Read this article on MySQL and ZFS: http://dev.mysql.com/tech-resources/articles/mysql-zfs.html It proposed that you allocate less ram to MySQL in your my.cnf and let ZFS take care of caching. Here are my loader.conf settings. zfs_load=YES # ZFS tunings vm.kmem_size=800M vm.kmem_size_max=800M # http://wiki.freebsd.org/ZFSTuningGuide vfs.zfs.arc_max=160M vfs.zfs.vdev.cache.size=5M # and I have my root on zfs... vfs.root.mountfrom=zfs:tank/root - Rudy - ** monkeybrains.net colocation ** - ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
df locked up after upgrade to FreeBSD 7.1-PRERELEASE
Has anyone see the 'df' command just hang after an upgrade? From another terminal, I saw df in the 'D' state when running ps. I tried 'df ' in my new terminal, and that too just hung out in the background. typing 'reboot' fixed the problem. =) This box had been up for a while, no problems. The only thing I changed was a 7.0 to 7.1 upgrade. (Haven't rebuilt all the ports to match the new OS, yet) uname -v FreeBSD 7.1-PRERELEASE #0: Thu Nov 13 19:14:42 PST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MONKEY (MONKEY is pretty close to generic, just some ethernet and scsi stuff left out) kldstat Id Refs AddressSize Name 17 0xc040 4d39fc kernel 21 0xc08d4000 164e8geom_mirror.ko 31 0xc3e93000 9000 if_bridge.ko 41 0xc3e9c000 6000 bridgestp.ko 51 0xc3f78000 5000 if_tap.ko 61 0xc3fdd000 3000 daemon_saver.ko df -h FilesystemSizeUsed Avail Capacity Mounted on /dev/ad4s1a 248M213M 14M94%/ devfs 1.0K1.0K 0B 100%/dev procfs4.0K4.0K 0B 100%/proc /dev/mirror/gm0s1d989M200M710M22%/var /dev/mirror/gm0s1e496M1.7M454M 0%/tmp /dev/ad4s1f 2.9G1.4G1.3G52%/usr /dev/mirror/gm0s1g268G105G142G42%/data /dev/ad4s1h 180G391M166G 0%/data2 devfs 1.0K1.0K 0B 100%/var/named/dev - Rudy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: df locked up after upgrade to FreeBSD 7.1-PRERELEASE
Jille Timmermans wrote: Are there 'broken' (lost connection without being umounted) NFS mounts by any chance ? That would cause df to wait for eternity (or till the host comes back up). Doh! I have the FreeBSD source on one server and mount over NFS for builds. I thought I'd already rebooted into the new kernel thus unmounting /usr/src, but I must have remounted (maybe when I ran mergemaster (or something!))!!! Thanks, Rudy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Make buildworld on latest stable fails
Ruslan Ermilov wrote: On Tue, May 07, 2002 at 04:54:47AM -0700, Daniel Rudy wrote: Hello, I've been experiancing a problem as of late. It seems that make buildworld fails when compiling the miniperl module. Here is the text of the failure: cc -O -pipe -I/usr/obj/usr/src/gnu/usr.bin/perl/miniperl -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contr ib/perl5 -L/usr/obj/usr/src/gnu/usr.bin/perl/miniperl/../libperl -static -o miniperl miniperlmain.o perl.o g v.o toke.o perly.o op.o regcomp.o dump.o util.o mg.o hv.o av.o run.o pp_hot.o sv.o pp.o scope.o pp_ctl.o pp_sys. o doop.o doio.o regexec.o taint.o universal.o globals.o perlio.o -lm -lcrypt -lutil /usr/lib/libc.a(gethostnamadr.o)(.text+0x2a): undefined reference to `strcasecmprcasecmprcasecmprcasecmphostbydn sname' /usr/lib/libc.a(gethostnamadr.o)(.text+0x109): undefined reference to `casecmprcasecmprcasecmphostbydnsname' /usr/lib/libc.a(gethostnamadr.o): In function `gethostbyname2': gethostnamadr.o(.text+0x265): undefined reference to `ecmphostbydnsname' *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl/miniperl. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Thinking it was some sort of problem in the source. I dumped the source code and loaded bran new from the cvsup3 server and I still get the same failure. Any ideas or suggestions? Your /usr/lib/libc.a has apparently got broken. The correct and consistent /usr/lib and /usr/include are prerequisites for a successful make world. Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age Part 1.2Type: application/pgp-signature In that case, how do I fix it? I checked the dates of the files, and everything seems to be Apr 29, with a few exceptions. I'm hoping that I don't have to reinstall the system. -- Daniel Rudy To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: SB Live and Qt2.2
I recently went through the same thing (still having intermittent sound problems, but it's getting there). /dev/sndstats seems to be created when you do sh MAKEDEV snd0. That created all the sound devices (mixer, dsp, etc.). Rudyatek I recently upgraded my FBSD 4.0 to a 4.2 (stable) with no problems. Sound device prob: Ive added in the kernel config the devices pcm and sbc, but I dont have a /dev/sndstats. And I cant sh MAKEDEV sndstats. A point to remember is that my sound system is a Sound Blaster Live... How can i create the /dev/sndstats device? Is the kernel for 4.2 able to support my SB Live? And if not, can I patch it to? And if so where can I find the patch? QT2.2 prob: I was trying to add the kde2 package trough the ports system... (yes, I also upgraded the ports skeleton with CVS), and a dependency package, QT2, was required to 'make install', but it just exited with error... here's the exit msg (sorry about this...): /usr/local/lib/libmng.so.0: undefined reference to `cmsOpenProfileFromMem' /usr/local/lib/libmng.so.0: undefined reference to `cmsDoTransform' /usr/local/lib/libmng.so.0: undefined reference to `cmsErrorAction' /usr/local/lib/libmng.so.0: undefined reference to `cmsCreateRGBProfile' /usr/local/lib/libmng.so.0: undefined reference to `cmsFreeGamma' /usr/local/lib/libmng.so.0: undefined reference to `cmsOpenProfileFromFile' /usr/local/lib/libmng.so.0: undefined reference to `cmsCloseProfile' /usr/local/lib/libmng.so.0: undefined reference to `cmsDeleteTransform' /usr/local/lib/libmng.so.0: undefined reference to `cmsCreateTransform' /usr/local/lib/libmng.so.0: undefined reference to `cmsBuildGamma' gmake[5]: *** [/usr/ports/x11-toolkits/qt22/work/qt-2.2.3/bin/uic] Error 1 gmake[5]: Leaving directory `/usr/ports/x11-toolkits/qt22/work/qt-2.2.3/tools/de signer/uic' gmake[4]: *** [uic] Error 2 gmake[4]: Leaving directory `/usr/ports/x11-toolkits/qt22/work/qt-2.2.3/tools/designer' gmake[3]: *** [all] Error 2 gmake[3]: Leaving directory `/usr/ports/x11-toolkits/qt22/work/qt-2.2.3/tools/designer' gmake[2]: *** [designer] Error 2 gmake[2]: Leaving directory `/usr/ports/x11-toolkits/qt22/work/qt-2.2.3/tools' gmake[1]: *** [all] Error 2 gmake[1]: Leaving directory `/usr/ports/x11-toolkits/qt22/work/qt-2.2.3/tools' gmake: *** [sub-tools] Error 2 *** Error code 2 Stop in /usr/ports/x11-toolkits/qt22. *** Error code 1 Stop in /usr/ports/x11-toolkits/qt22. *** Error code 1 Stop in /usr/ports/x11-toolkits/qt22. Does anyone have a clue to what's going wrong? Thanks for all your help. Joao Fernandes. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ftpd problems...
Here is my recommendation, add the following to rc.firewall:
case ${natd_enable} in
[Yy][Ee][Ss])
if [ -n "${natd_interface}" ]; then
${fwcmd} add 98 divert natd all from any to any via
${natd_interface}
fi
;;
[Ff][Tt][Pp])
if [ -n "${natd_interface}" ]; then
${fwcmd} add 97 allow tcp from any 20 to any out via
${natd_interface}
${fwcmd} add 98 divert natd all from any to any via
${natd_interface}
fi
;;
esac
Rudy
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
ftpd problem fixed! Have the DIVERT sockets changed?
I finally (after about 4 hours of hitting my head on the wall) figured it out. Simple really. I am running 'natd' on FreeBSD 4.1 ... The _out_going_ active connection is mapped to the masquerading IP of the box! I have a setup where a box has 5 ips on it and maps ips for about 20 people behind the firewall. I added a new rule to my firewall (before the divert rule) which 'fixes' the problem (rule #00090): 00090 4 705 allow tcp from any 20 to any out xmit ed0 00099 15 2937 divert 8668 ip from any to any via ed0 This rule lets anything from the FTP port out via my outside interface. BTW, Freebsd must have changed the way ipfw works, cause I was having no problems a couple of months ago. I don't *think* that aliased IPs where affected by the divert rule in 4.0. (I don't think they should be either! Only traffic form my second interface, ed1, should get rewritten by natd.) Rudy To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
make world fails at 'truss' (even with sed/main.c patch)
I'm getting a failure in usr.bin/truss/. ioctl.c complains about not finging sys/random.h To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
