[releng_8 tinderbox] failure on i386/pc98
TB --- 2010-11-20 09:41:08 - tinderbox 2.6 running on freebsd-stable.sentex.ca TB --- 2010-11-20 09:41:08 - starting RELENG_8 tinderbox run for i386/pc98 TB --- 2010-11-20 09:41:08 - cleaning the object tree TB --- 2010-11-20 09:41:18 - cvsupping the source tree TB --- 2010-11-20 09:41:18 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8/i386/pc98/supfile TB --- 2010-11-20 09:42:07 - building world TB --- 2010-11-20 09:42:07 - MAKEOBJDIRPREFIX=/obj TB --- 2010-11-20 09:42:07 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-11-20 09:42:07 - TARGET=pc98 TB --- 2010-11-20 09:42:07 - TARGET_ARCH=i386 TB --- 2010-11-20 09:42:07 - TZ=UTC TB --- 2010-11-20 09:42:07 - __MAKE_CONF=/dev/null TB --- 2010-11-20 09:42:07 - cd /src TB --- 2010-11-20 09:42:07 - /usr/bin/make -B buildworld World build started on Sat Nov 20 09:42:08 UTC 2010 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything World build completed on Sat Nov 20 10:43:36 UTC 2010 TB --- 2010-11-20 10:43:36 - generating LINT kernel config TB --- 2010-11-20 10:43:36 - cd /src/sys/pc98/conf TB --- 2010-11-20 10:43:36 - /usr/bin/make -B LINT TB --- 2010-11-20 10:43:36 - building LINT kernel TB --- 2010-11-20 10:43:36 - MAKEOBJDIRPREFIX=/obj TB --- 2010-11-20 10:43:36 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-11-20 10:43:36 - TARGET=pc98 TB --- 2010-11-20 10:43:36 - TARGET_ARCH=i386 TB --- 2010-11-20 10:43:36 - TZ=UTC TB --- 2010-11-20 10:43:36 - __MAKE_CONF=/dev/null TB --- 2010-11-20 10:43:36 - cd /src TB --- 2010-11-20 10:43:36 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Sat Nov 20 10:43:36 UTC 2010 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies [...] awk -f /src/sys/tools/makeobjops.awk /src/sys/libkern/iconv_converter_if.m -h awk -f /src/sys/tools/makeobjops.awk /src/sys/opencrypto/cryptodev_if.m -h awk -f /src/sys/tools/makeobjops.awk /src/sys/pc98/pc98/canbus_if.m -h rm -f .newdep /usr/bin/make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES | MKDEP_CPP=cc -E CC=cc xargs mkdep -a -f .newdep -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/dev/ath/ath_hal -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -I/src/sys/gnu/fs/xfs/FreeBSD -I/src/sys/gnu/fs/xfs/FreeBSD/support -I/src/sys/gnu/fs/xfs -I/src/sys/contrib/opensolaris/compat -I/src/sys/dev/cxgb -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestan! ding -fstack-protector In file included from /src/sys/x86/x86/nexus.c:82: /src/sys/i386/isa/isa.h:37:2: error: #error isa.h is included from PC-9801 source mkdep: compile failed *** Error code 1 Stop in /obj/pc98/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2010-11-20 10:45:28 - WARNING: /usr/bin/make returned exit code 1 TB --- 2010-11-20 10:45:28 - ERROR: failed to build lint kernel TB --- 2010-11-20 10:45:28 - 2829.55 user 420.47 system 3860.05 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8-i386-pc98.full ___ 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: Call for testers: FPU changes
On Sat, Nov 20, 2010 at 01:30:54AM -0500, Mike Tancsa wrote: On 11/16/2010 4:43 AM, Kostik Belousov wrote: On Mon, Nov 15, 2010 at 10:42:50PM -0500, Mike Tancsa wrote: On 11/15/2010 4:13 PM, Kostik Belousov wrote: Patch is at http://people.freebsd.org/~kib/misc/releng_8_fpu.1.patch I did some more tests post commit today using the aesni kld taken directly from HEAD. BTW, do you plan to MFC this as well ? Sure, I will merge aesni(4), it was the only reason to work on the kern_fpu in stable/8. I want some pause between KPI and driver MFC, to ease the handling of possible mismerge or fixing latent bugs (since stable has much larger testing base then HEAD). Results at the bottom of http://www.tancsa.com/fpu.html It certainly makes a difference with geli. IPSEC and userland stuff, not so much. The CPU itself is crazy fast, so its hard to see a difference in things like ssh and even ipsec didnt yield any differences. For ssh and userland stuff I guess once there is an aesni userland engine, this would probably help over the cryptodev interface. Yes, the small blocks encoding/decoding has a large overhead of loop setup code. Thank you. pgpGfPDahzWMt.pgp Description: PGP signature
[releng_8 tinderbox] failure on ia64/ia64
TB --- 2010-11-20 09:51:50 - tinderbox 2.6 running on freebsd-stable.sentex.ca TB --- 2010-11-20 09:51:50 - starting RELENG_8 tinderbox run for ia64/ia64 TB --- 2010-11-20 09:51:50 - cleaning the object tree TB --- 2010-11-20 09:52:17 - cvsupping the source tree TB --- 2010-11-20 09:52:17 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8/ia64/ia64/supfile TB --- 2010-11-20 09:53:03 - building world TB --- 2010-11-20 09:53:03 - MAKEOBJDIRPREFIX=/obj TB --- 2010-11-20 09:53:03 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-11-20 09:53:03 - TARGET=ia64 TB --- 2010-11-20 09:53:03 - TARGET_ARCH=ia64 TB --- 2010-11-20 09:53:03 - TZ=UTC TB --- 2010-11-20 09:53:03 - __MAKE_CONF=/dev/null TB --- 2010-11-20 09:53:03 - cd /src TB --- 2010-11-20 09:53:03 - /usr/bin/make -B buildworld World build started on Sat Nov 20 09:53:04 UTC 2010 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything World build completed on Sat Nov 20 11:11:46 UTC 2010 TB --- 2010-11-20 11:11:46 - generating LINT kernel config TB --- 2010-11-20 11:11:46 - cd /src/sys/ia64/conf TB --- 2010-11-20 11:11:46 - /usr/bin/make -B LINT TB --- 2010-11-20 11:11:47 - building LINT kernel TB --- 2010-11-20 11:11:47 - MAKEOBJDIRPREFIX=/obj TB --- 2010-11-20 11:11:47 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-11-20 11:11:47 - TARGET=ia64 TB --- 2010-11-20 11:11:47 - TARGET_ARCH=ia64 TB --- 2010-11-20 11:11:47 - TZ=UTC TB --- 2010-11-20 11:11:47 - __MAKE_CONF=/dev/null TB --- 2010-11-20 11:11:47 - cd /src TB --- 2010-11-20 11:11:47 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Sat Nov 20 11:11:47 UTC 2010 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/dev/acpica/Osd/OsdSchedule.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/dev/acpica/Osd/OsdStream.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/dev/acpica/Osd/OsdSynch.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/dev/acpica/Osd/OsdTable.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param
Re: [Call for Tests] PAT issue on Apple hardware
On Fri, 19 Nov 2010 19:54:21 +0100, Jung-uk Kim j...@freebsd.org wrote: On Tuesday 16 November 2010 03:30 pm, Jung-uk Kim wrote: On Monday 15 November 2010 08:36 pm, Jung-uk Kim wrote: Often times I hear complaints like my Mac hangs after upgrading to 8.1 or snapshot CD hangs on my brand new Mac. I know some of these complaints started happening when we switched to new PAT layout. It is so puzzling because it never happened on non-Apple hardware, AFAIK. I really like to fix this problem but I cannot afford a Mac. :-P If you are one of those lucky people, please test the attached patch and report your hardware model and any improvement or regression. Also, I added a new tunable vm.pmap.pat_works so that you can turn it off from loader (i.e., set vm.pmap.pat_works=0) and restore old behaviour without recompiling a new kernel. I revised this patch to make it more robust. http://people.freebsd.org/~jkim/pat-current.diff Also, I prepared a patch for stable/8. If you have recent Apple hardware and it hangs with 8.1 or stable/8, please test this patch. http://people.freebsd.org/~jkim/pat-stable.diff Anyone? I don't want to commit it blindly. :-( It works for me ! I have an iMac9,1 (Core2 Duo 2.93 GHz and nVidia GT9200) This is the first time it boots on FreeBSD 8.x (8.1-STABLE) Thank you ! ___ 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
problems with network on em
I'm experiencing network interface stalls on em in FreeBSD 8.1-RELEASE (-p1). It looks like the problem could be solved in 8-STABLE, but should I upgrade to it ? Is it OK to try to get only em driver code and recompile as module and try to run it ? sysctl dev.em.2.stats=1: ... em2: Missed Packets = 101334 em2: Receive No Buffers = 488 ... em2: RX overruns = 1356 em2: watchdog timeouts = 1 ... Only ifconfig em2 down;ifconfig em2 up helps for some time. The same happens on em0 interface only, but not in the same time. It is production (NAT) router with pf+pfsync+carp and failover over another router. They are old SunFire X4100 boxes (4GB RAM, 2*2 AMD Opteron 2.2GHz). Regards, Rolandas Naujikas___ 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: problems with network on em
On 11/20/2010 10:09 AM, rol...@gmail.com wrote: I'm experiencing network interface stalls on em in FreeBSD 8.1-RELEASE (-p1). It looks like the problem could be solved in 8-STABLE, but should I upgrade to it ? Is it OK to try to get only em driver code and recompile as module and try to run it ? sysctl dev.em.2.stats=1: ... em2: Missed Packets = 101334 em2: Receive No Buffers = 488 ... em2: RX overruns = 1356 em2: watchdog timeouts = 1 ... Only ifconfig em2 down;ifconfig em2 up helps for some time. The same happens on em0 interface only, but not in the same time. It is production (NAT) router with pf+pfsync+carp and failover over another router. They are old SunFire X4100 boxes (4GB RAM, 2*2 AMD Opteron 2.2GHz). There are a lot of bug fixes in the version for HEAD. I would actually try that. You should be able to compile it in your existing kernel. Just grab the source files from /usr/src/sys/dev/e1000 from CURRENT and overwrite them locally. Then recompile your kernel and try that. ---Mike ___ 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: problems with network on em
On Sat, Nov 20, 2010 at 05:09:28PM +0200, rol...@gmail.com wrote: I'm experiencing network interface stalls on em in FreeBSD 8.1-RELEASE (-p1). It looks like the problem could be solved in 8-STABLE, but should I upgrade to it ? Is it OK to try to get only em driver code and recompile as module and try to run it ? sysctl dev.em.2.stats=1: ... em2: Missed Packets = 101334 em2: Receive No Buffers = 488 ... em2: RX overruns = 1356 em2: watchdog timeouts = 1 ... Only ifconfig em2 down;ifconfig em2 up helps for some time. The same happens on em0 interface only, but not in the same time. It is production (NAT) router with pf+pfsync+carp and failover over another router. They are old SunFire X4100 boxes (4GB RAM, 2*2 AMD Opteron 2.2GHz). You're going to need to provide output from the following, run as root. For the pciconf command, please only include the entry that's relevant to the device in question (em2). You can also XXX-out the MAC address and/or IP addresses if you're worried about security. $ pciconf -lvc $ dmesg | grep em2 $ sysctl dev.em.2 $ uname -a $ netstat -ind -I em2 Thanks. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ 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: problems with network on em
On 2010.11.20, at 17:54, Jeremy Chadwick wrote: On Sat, Nov 20, 2010 at 05:09:28PM +0200, rol...@gmail.com wrote: I'm experiencing network interface stalls on em in FreeBSD 8.1-RELEASE (-p1). It looks like the problem could be solved in 8-STABLE, but should I upgrade to it ? Is it OK to try to get only em driver code and recompile as module and try to run it ? sysctl dev.em.2.stats=1: ... em2: Missed Packets = 101334 em2: Receive No Buffers = 488 ... em2: RX overruns = 1356 em2: watchdog timeouts = 1 ... Only ifconfig em2 down;ifconfig em2 up helps for some time. The same happens on em0 interface only, but not in the same time. It is production (NAT) router with pf+pfsync+carp and failover over another router. They are old SunFire X4100 boxes (4GB RAM, 2*2 AMD Opteron 2.2GHz). You're going to need to provide output from the following, run as root. For the pciconf command, please only include the entry that's relevant to the device in question (em2). You can also XXX-out the MAC address and/or IP addresses if you're worried about security. $ pciconf -lvc e...@pci0:1:2:0: class=0x02 card=0x10118086 chip=0x10108086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'Dual Port Gigabit Ethernet Controller (Copper) (82546EB)' class = network subclass = ethernet cap 01[dc] = powerspec 2 supports D0 D3 current D0 cap 07[e4] = PCI-X 64-bit supports 133MHz, 2048 burst read, 1 split transaction cap 05[f0] = MSI supports 1 message, 64 bit $ dmesg | grep em2 em2: Intel(R) PRO/1000 Legacy Network Connection 1.0.1 port 0x9400-0x943f mem 0xfbfa-0xfbfb irq 24 at device 2.0 on pci1 em2: [FILTER] em2: Ethernet address: 00:14:4f:XX:XX:XX $ sysctl dev.em.2 dev.em.2.%desc: Intel(R) PRO/1000 Legacy Network Connection 1.0.1 dev.em.2.%driver: em dev.em.2.%location: slot=2 function=0 dev.em.2.%pnpinfo: vendor=0x8086 device=0x1010 subvendor=0x8086 subdevice=0x1011 class=0x02 dev.em.2.%parent: pci1 dev.em.2.debug: -1 dev.em.2.stats: -1 dev.em.2.rx_int_delay: 0 dev.em.2.tx_int_delay: 66 dev.em.2.rx_abs_int_delay: 66 dev.em.2.tx_abs_int_delay: 66 dev.em.2.rx_processing_limit: 100 $ uname -a FreeBSD sunfire1.mif 8.1-RELEASE-p1 FreeBSD 8.1-RELEASE-p1 #2: Thu Nov 18 10:39:07 EET 2010 r...@sunfire1.mif:/home/local/obj/usr/src/sys/SUNFIRE amd64 Recompiled with DEVICE_POLLING and HZ=2000, carp and many not used devices removed. $ netstat -ind -I em2 NameMtu Network Address Ipkts Ierrs IdropOpkts Oerrs Coll Drop em21500 Link#3 00:14:4f:XX:XX:XX 66430440 101334 0 59339619 1 00 em21500 192.168.0.0/1 192.168.XX.XXX 633845 - - 3815946 - -- ... em01500 Link#1 00:14:4f:XX:XX:XX 167143400 152726 0 143900328 0 00 Regards, Rolandas Naujikas Thanks. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ 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: problems with network on em
I just got another lockup. It looks like in the time of lockup the number of Ierrs is increasing: NameMtu Network Address Ipkts Ierrs IdropOpkts Oerrs Coll em21500 Link#3 00:14:4f:XX:XX:XX 13060395 18438 0 6579984 1 0 After ifconfig em2 down;ifconfig em2 up Ierrs stays at 0 rate for long time. Without DEVICE_POLLING it was similar situation. Regards, Rolandas Naujikas On 2010.11.20, at 18:24, rol...@gmail.com wrote: On 2010.11.20, at 17:54, Jeremy Chadwick wrote: On Sat, Nov 20, 2010 at 05:09:28PM +0200, rol...@gmail.com wrote: I'm experiencing network interface stalls on em in FreeBSD 8.1-RELEASE (-p1). It looks like the problem could be solved in 8-STABLE, but should I upgrade to it ? Is it OK to try to get only em driver code and recompile as module and try to run it ? sysctl dev.em.2.stats=1: ... em2: Missed Packets = 101334 em2: Receive No Buffers = 488 ... em2: RX overruns = 1356 em2: watchdog timeouts = 1 ... Only ifconfig em2 down;ifconfig em2 up helps for some time. The same happens on em0 interface only, but not in the same time. It is production (NAT) router with pf+pfsync+carp and failover over another router. They are old SunFire X4100 boxes (4GB RAM, 2*2 AMD Opteron 2.2GHz). You're going to need to provide output from the following, run as root. For the pciconf command, please only include the entry that's relevant to the device in question (em2). You can also XXX-out the MAC address and/or IP addresses if you're worried about security. $ pciconf -lvc e...@pci0:1:2:0: class=0x02 card=0x10118086 chip=0x10108086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'Dual Port Gigabit Ethernet Controller (Copper) (82546EB)' class = network subclass = ethernet cap 01[dc] = powerspec 2 supports D0 D3 current D0 cap 07[e4] = PCI-X 64-bit supports 133MHz, 2048 burst read, 1 split transaction cap 05[f0] = MSI supports 1 message, 64 bit $ dmesg | grep em2 em2: Intel(R) PRO/1000 Legacy Network Connection 1.0.1 port 0x9400-0x943f mem 0xfbfa-0xfbfb irq 24 at device 2.0 on pci1 em2: [FILTER] em2: Ethernet address: 00:14:4f:XX:XX:XX $ sysctl dev.em.2 dev.em.2.%desc: Intel(R) PRO/1000 Legacy Network Connection 1.0.1 dev.em.2.%driver: em dev.em.2.%location: slot=2 function=0 dev.em.2.%pnpinfo: vendor=0x8086 device=0x1010 subvendor=0x8086 subdevice=0x1011 class=0x02 dev.em.2.%parent: pci1 dev.em.2.debug: -1 dev.em.2.stats: -1 dev.em.2.rx_int_delay: 0 dev.em.2.tx_int_delay: 66 dev.em.2.rx_abs_int_delay: 66 dev.em.2.tx_abs_int_delay: 66 dev.em.2.rx_processing_limit: 100 $ uname -a FreeBSD sunfire1.mif 8.1-RELEASE-p1 FreeBSD 8.1-RELEASE-p1 #2: Thu Nov 18 10:39:07 EET 2010 r...@sunfire1.mif:/home/local/obj/usr/src/sys/SUNFIRE amd64 Recompiled with DEVICE_POLLING and HZ=2000, carp and many not used devices removed. $ netstat -ind -I em2 NameMtu Network Address Ipkts Ierrs IdropOpkts Oerrs Coll Drop em21500 Link#3 00:14:4f:XX:XX:XX 66430440 101334 0 59339619 1 00 em21500 192.168.0.0/1 192.168.XX.XXX 633845 - - 3815946 - -- ... em01500 Link#1 00:14:4f:XX:XX:XX 167143400 152726 0 143900328 0 00 Regards, Rolandas Naujikas Thanks. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ 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: problems with network on em
On Sat, Nov 20, 2010 at 06:38:19PM +0200, Naujikas Rolandas wrote: I just got another lockup. It looks like in the time of lockup the number of Ierrs is increasing: NameMtu Network Address Ipkts Ierrs IdropOpkts Oerrs Coll em21500 Link#3 00:14:4f:XX:XX:XX 13060395 18438 0 6579984 1 0 After ifconfig em2 down;ifconfig em2 up Ierrs stays at 0 rate for long time. Without DEVICE_POLLING it was similar situation. Regards, Rolandas Naujikas On 2010.11.20, at 18:24, rol...@gmail.com wrote: On 2010.11.20, at 17:54, Jeremy Chadwick wrote: On Sat, Nov 20, 2010 at 05:09:28PM +0200, rol...@gmail.com wrote: I'm experiencing network interface stalls on em in FreeBSD 8.1-RELEASE (-p1). It looks like the problem could be solved in 8-STABLE, but should I upgrade to it ? Is it OK to try to get only em driver code and recompile as module and try to run it ? sysctl dev.em.2.stats=1: ... em2: Missed Packets = 101334 em2: Receive No Buffers = 488 ... em2: RX overruns = 1356 em2: watchdog timeouts = 1 ... Only ifconfig em2 down;ifconfig em2 up helps for some time. The same happens on em0 interface only, but not in the same time. It is production (NAT) router with pf+pfsync+carp and failover over another router. They are old SunFire X4100 boxes (4GB RAM, 2*2 AMD Opteron 2.2GHz). You're going to need to provide output from the following, run as root. For the pciconf command, please only include the entry that's relevant to the device in question (em2). You can also XXX-out the MAC address and/or IP addresses if you're worried about security. $ pciconf -lvc e...@pci0:1:2:0: class=0x02 card=0x10118086 chip=0x10108086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'Dual Port Gigabit Ethernet Controller (Copper) (82546EB)' class = network subclass = ethernet cap 01[dc] = powerspec 2 supports D0 D3 current D0 cap 07[e4] = PCI-X 64-bit supports 133MHz, 2048 burst read, 1 split transaction cap 05[f0] = MSI supports 1 message, 64 bit $ dmesg | grep em2 em2: Intel(R) PRO/1000 Legacy Network Connection 1.0.1 port 0x9400-0x943f mem 0xfbfa-0xfbfb irq 24 at device 2.0 on pci1 em2: [FILTER] em2: Ethernet address: 00:14:4f:XX:XX:XX $ sysctl dev.em.2 dev.em.2.%desc: Intel(R) PRO/1000 Legacy Network Connection 1.0.1 dev.em.2.%driver: em dev.em.2.%location: slot=2 function=0 dev.em.2.%pnpinfo: vendor=0x8086 device=0x1010 subvendor=0x8086 subdevice=0x1011 class=0x02 dev.em.2.%parent: pci1 dev.em.2.debug: -1 dev.em.2.stats: -1 dev.em.2.rx_int_delay: 0 dev.em.2.tx_int_delay: 66 dev.em.2.rx_abs_int_delay: 66 dev.em.2.tx_abs_int_delay: 66 dev.em.2.rx_processing_limit: 100 $ uname -a FreeBSD sunfire1.mif 8.1-RELEASE-p1 FreeBSD 8.1-RELEASE-p1 #2: Thu Nov 18 10:39:07 EET 2010 r...@sunfire1.mif:/home/local/obj/usr/src/sys/SUNFIRE amd64 Recompiled with DEVICE_POLLING and HZ=2000, carp and many not used devices removed. $ netstat -ind -I em2 NameMtu Network Address Ipkts Ierrs IdropOpkts Oerrs Coll Drop em21500 Link#3 00:14:4f:XX:XX:XX 66430440 101334 0 59339619 1 00 em21500 192.168.0.0/1 192.168.XX.XXX 633845 - - 3815946 - -- ... em01500 Link#1 00:14:4f:XX:XX:XX 167143400 152726 0 143900328 0 00 Regards, Rolandas Naujikas Thanks. Oops, I forgot requesting output from one other command: $ vmstat -i Adding Jack Vogel to the thread, who might have ideas/comments. Jack, here's the thread: http://lists.freebsd.org/pipermail/freebsd-stable/2010-November/060183.html As for my comments: Unidirectional errors (input or output) often indicates a duplex mismatch or some sort of weird quirk between one link partner and the other. I *have* seen cases where both sides are auto-neg and one side acts like it has the wrong duplex selection despite ifconfig reporting full-duplex and the switch reporting full. Forcing speed and duplex on both ends (requires a managed switch; please don't try this with a generic consumer switch) resolved the problem. It could be that there's a driver bug causing this to happen -- down/up seems to indicate that could be the case -- but every situation needs to be addressed individually. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to
Re: problems with network on em
I'm trying to test with newest version of /sys/dev/e1000 from FreeBSD 8-STABLE. For that I'm using loadable module option, because it is easier to build with minimal changes in kernel source. Only /sys/dev/e1000 and /sys/modules/em need to be updated. Without changes in /sys/modules/em/Makefile it compiles, but have missing symbol or if you compile static kernel - the same problem. Now I'm testing and it looks promising (except I see a little bigger kernel thread netisr cpu load, but it's acceptable). Regards, Rolandas Naujikas On 2010.11.20, at 19:05, Jeremy Chadwick wrote: On Sat, Nov 20, 2010 at 06:38:19PM +0200, Naujikas Rolandas wrote: I just got another lockup. It looks like in the time of lockup the number of Ierrs is increasing: NameMtu Network Address Ipkts Ierrs IdropOpkts Oerrs Coll em21500 Link#3 00:14:4f:XX:XX:XX 13060395 18438 0 6579984 1 0 After ifconfig em2 down;ifconfig em2 up Ierrs stays at 0 rate for long time. Without DEVICE_POLLING it was similar situation. Regards, Rolandas Naujikas On 2010.11.20, at 18:24, rol...@gmail.com wrote: On 2010.11.20, at 17:54, Jeremy Chadwick wrote: On Sat, Nov 20, 2010 at 05:09:28PM +0200, rol...@gmail.com wrote: I'm experiencing network interface stalls on em in FreeBSD 8.1-RELEASE (-p1). It looks like the problem could be solved in 8-STABLE, but should I upgrade to it ? Is it OK to try to get only em driver code and recompile as module and try to run it ? sysctl dev.em.2.stats=1: ... em2: Missed Packets = 101334 em2: Receive No Buffers = 488 ... em2: RX overruns = 1356 em2: watchdog timeouts = 1 ... Only ifconfig em2 down;ifconfig em2 up helps for some time. The same happens on em0 interface only, but not in the same time. It is production (NAT) router with pf+pfsync+carp and failover over another router. They are old SunFire X4100 boxes (4GB RAM, 2*2 AMD Opteron 2.2GHz). You're going to need to provide output from the following, run as root. For the pciconf command, please only include the entry that's relevant to the device in question (em2). You can also XXX-out the MAC address and/or IP addresses if you're worried about security. $ pciconf -lvc e...@pci0:1:2:0: class=0x02 card=0x10118086 chip=0x10108086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'Dual Port Gigabit Ethernet Controller (Copper) (82546EB)' class = network subclass = ethernet cap 01[dc] = powerspec 2 supports D0 D3 current D0 cap 07[e4] = PCI-X 64-bit supports 133MHz, 2048 burst read, 1 split transaction cap 05[f0] = MSI supports 1 message, 64 bit $ dmesg | grep em2 em2: Intel(R) PRO/1000 Legacy Network Connection 1.0.1 port 0x9400-0x943f mem 0xfbfa-0xfbfb irq 24 at device 2.0 on pci1 em2: [FILTER] em2: Ethernet address: 00:14:4f:XX:XX:XX $ sysctl dev.em.2 dev.em.2.%desc: Intel(R) PRO/1000 Legacy Network Connection 1.0.1 dev.em.2.%driver: em dev.em.2.%location: slot=2 function=0 dev.em.2.%pnpinfo: vendor=0x8086 device=0x1010 subvendor=0x8086 subdevice=0x1011 class=0x02 dev.em.2.%parent: pci1 dev.em.2.debug: -1 dev.em.2.stats: -1 dev.em.2.rx_int_delay: 0 dev.em.2.tx_int_delay: 66 dev.em.2.rx_abs_int_delay: 66 dev.em.2.tx_abs_int_delay: 66 dev.em.2.rx_processing_limit: 100 $ uname -a FreeBSD sunfire1.mif 8.1-RELEASE-p1 FreeBSD 8.1-RELEASE-p1 #2: Thu Nov 18 10:39:07 EET 2010 r...@sunfire1.mif:/home/local/obj/usr/src/sys/SUNFIRE amd64 Recompiled with DEVICE_POLLING and HZ=2000, carp and many not used devices removed. $ netstat -ind -I em2 NameMtu Network Address Ipkts Ierrs IdropOpkts Oerrs Coll Drop em21500 Link#3 00:14:4f:XX:XX:XX 66430440 101334 0 59339619 1 00 em21500 192.168.0.0/1 192.168.XX.XXX 633845 - - 3815946 - -- ... em01500 Link#1 00:14:4f:XX:XX:XX 167143400 152726 0 143900328 0 00 Regards, Rolandas Naujikas Thanks. Oops, I forgot requesting output from one other command: $ vmstat -i Adding Jack Vogel to the thread, who might have ideas/comments. Jack, here's the thread: http://lists.freebsd.org/pipermail/freebsd-stable/2010-November/060183.html As for my comments: Unidirectional errors (input or output) often indicates a duplex mismatch or some sort of weird quirk between one link partner and the other. I *have* seen cases where both sides are auto-neg and one side acts like it has the wrong duplex selection despite ifconfig reporting full-duplex and the switch reporting full. Forcing speed and duplex on both ends (requires a managed switch; please don't try this with a generic consumer switch) resolved the problem. It could be that there's a driver bug causing this to happen -- down/up seems to indicate that could be the case -- but every situation needs to be addressed
[releng_8 tinderbox] failure on i386/pc98
TB --- 2010-11-20 19:28:16 - tinderbox 2.6 running on freebsd-stable.sentex.ca TB --- 2010-11-20 19:28:16 - starting RELENG_8 tinderbox run for i386/pc98 TB --- 2010-11-20 19:28:16 - cleaning the object tree TB --- 2010-11-20 19:28:27 - cvsupping the source tree TB --- 2010-11-20 19:28:27 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8/i386/pc98/supfile TB --- 2010-11-20 19:29:10 - building world TB --- 2010-11-20 19:29:10 - MAKEOBJDIRPREFIX=/obj TB --- 2010-11-20 19:29:10 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-11-20 19:29:10 - TARGET=pc98 TB --- 2010-11-20 19:29:10 - TARGET_ARCH=i386 TB --- 2010-11-20 19:29:10 - TZ=UTC TB --- 2010-11-20 19:29:10 - __MAKE_CONF=/dev/null TB --- 2010-11-20 19:29:10 - cd /src TB --- 2010-11-20 19:29:10 - /usr/bin/make -B buildworld World build started on Sat Nov 20 19:29:11 UTC 2010 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything World build completed on Sat Nov 20 20:31:12 UTC 2010 TB --- 2010-11-20 20:31:12 - generating LINT kernel config TB --- 2010-11-20 20:31:12 - cd /src/sys/pc98/conf TB --- 2010-11-20 20:31:12 - /usr/bin/make -B LINT TB --- 2010-11-20 20:31:13 - building LINT kernel TB --- 2010-11-20 20:31:13 - MAKEOBJDIRPREFIX=/obj TB --- 2010-11-20 20:31:13 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-11-20 20:31:13 - TARGET=pc98 TB --- 2010-11-20 20:31:13 - TARGET_ARCH=i386 TB --- 2010-11-20 20:31:13 - TZ=UTC TB --- 2010-11-20 20:31:13 - __MAKE_CONF=/dev/null TB --- 2010-11-20 20:31:13 - cd /src TB --- 2010-11-20 20:31:13 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Sat Nov 20 20:31:13 UTC 2010 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies [...] awk -f /src/sys/tools/makeobjops.awk /src/sys/libkern/iconv_converter_if.m -h awk -f /src/sys/tools/makeobjops.awk /src/sys/opencrypto/cryptodev_if.m -h awk -f /src/sys/tools/makeobjops.awk /src/sys/pc98/pc98/canbus_if.m -h rm -f .newdep /usr/bin/make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES | MKDEP_CPP=cc -E CC=cc xargs mkdep -a -f .newdep -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/dev/ath/ath_hal -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -I/src/sys/gnu/fs/xfs/FreeBSD -I/src/sys/gnu/fs/xfs/FreeBSD/support -I/src/sys/gnu/fs/xfs -I/src/sys/contrib/opensolaris/compat -I/src/sys/dev/cxgb -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestan! ding -fstack-protector In file included from /src/sys/x86/x86/nexus.c:82: /src/sys/i386/isa/isa.h:37:2: error: #error isa.h is included from PC-9801 source mkdep: compile failed *** Error code 1 Stop in /obj/pc98/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2010-11-20 20:33:01 - WARNING: /usr/bin/make returned exit code 1 TB --- 2010-11-20 20:33:01 - ERROR: failed to build lint kernel TB --- 2010-11-20 20:33:01 - 2840.70 user 416.85 system 3884.28 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8-i386-pc98.full ___ 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: problems with network on em
Did you mean the 7.1.7 version from HEAD ? Jack On Sat, Nov 20, 2010 at 11:18 AM, Naujikas Rolandas rolandas.nauji...@mif.vu.lt wrote: I'm trying to test with newest version of /sys/dev/e1000 from FreeBSD 8-STABLE. For that I'm using loadable module option, because it is easier to build with minimal changes in kernel source. Only /sys/dev/e1000 and /sys/modules/em need to be updated. Without changes in /sys/modules/em/Makefile it compiles, but have missing symbol or if you compile static kernel - the same problem. Now I'm testing and it looks promising (except I see a little bigger kernel thread netisr cpu load, but it's acceptable). Regards, Rolandas Naujikas On 2010.11.20, at 19:05, Jeremy Chadwick wrote: On Sat, Nov 20, 2010 at 06:38:19PM +0200, Naujikas Rolandas wrote: I just got another lockup. It looks like in the time of lockup the number of Ierrs is increasing: NameMtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll em21500 Link#3 00:14:4f:XX:XX:XX 13060395 18438 0 6579984 1 0 After ifconfig em2 down;ifconfig em2 up Ierrs stays at 0 rate for long time. Without DEVICE_POLLING it was similar situation. Regards, Rolandas Naujikas On 2010.11.20, at 18:24, rol...@gmail.com wrote: On 2010.11.20, at 17:54, Jeremy Chadwick wrote: On Sat, Nov 20, 2010 at 05:09:28PM +0200, rol...@gmail.com wrote: I'm experiencing network interface stalls on em in FreeBSD 8.1-RELEASE (-p1). It looks like the problem could be solved in 8-STABLE, but should I upgrade to it ? Is it OK to try to get only em driver code and recompile as module and try to run it ? sysctl dev.em.2.stats=1: ... em2: Missed Packets = 101334 em2: Receive No Buffers = 488 ... em2: RX overruns = 1356 em2: watchdog timeouts = 1 ... Only ifconfig em2 down;ifconfig em2 up helps for some time. The same happens on em0 interface only, but not in the same time. It is production (NAT) router with pf+pfsync+carp and failover over another router. They are old SunFire X4100 boxes (4GB RAM, 2*2 AMD Opteron 2.2GHz). You're going to need to provide output from the following, run as root. For the pciconf command, please only include the entry that's relevant to the device in question (em2). You can also XXX-out the MAC address and/or IP addresses if you're worried about security. $ pciconf -lvc e...@pci0:1:2:0: class=0x02 card=0x10118086 chip=0x10108086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'Dual Port Gigabit Ethernet Controller (Copper) (82546EB)' class = network subclass = ethernet cap 01[dc] = powerspec 2 supports D0 D3 current D0 cap 07[e4] = PCI-X 64-bit supports 133MHz, 2048 burst read, 1 split transaction cap 05[f0] = MSI supports 1 message, 64 bit $ dmesg | grep em2 em2: Intel(R) PRO/1000 Legacy Network Connection 1.0.1 port 0x9400-0x943f mem 0xfbfa-0xfbfb irq 24 at device 2.0 on pci1 em2: [FILTER] em2: Ethernet address: 00:14:4f:XX:XX:XX $ sysctl dev.em.2 dev.em.2.%desc: Intel(R) PRO/1000 Legacy Network Connection 1.0.1 dev.em.2.%driver: em dev.em.2.%location: slot=2 function=0 dev.em.2.%pnpinfo: vendor=0x8086 device=0x1010 subvendor=0x8086 subdevice=0x1011 class=0x02 dev.em.2.%parent: pci1 dev.em.2.debug: -1 dev.em.2.stats: -1 dev.em.2.rx_int_delay: 0 dev.em.2.tx_int_delay: 66 dev.em.2.rx_abs_int_delay: 66 dev.em.2.tx_abs_int_delay: 66 dev.em.2.rx_processing_limit: 100 $ uname -a FreeBSD sunfire1.mif 8.1-RELEASE-p1 FreeBSD 8.1-RELEASE-p1 #2: Thu Nov 18 10:39:07 EET 2010 r...@sunfire1.mif:/home/local/obj/usr/src/sys/SUNFIRE amd64 Recompiled with DEVICE_POLLING and HZ=2000, carp and many not used devices removed. $ netstat -ind -I em2 NameMtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll Drop em21500 Link#3 00:14:4f:XX:XX:XX 66430440 101334 0 59339619 1 00 em21500 192.168.0.0/1 192.168.XX.XXX 633845 - - 3815946 - -- ... em01500 Link#1 00:14:4f:XX:XX:XX 167143400 152726 0 143900328 0 00 Regards, Rolandas Naujikas Thanks. Oops, I forgot requesting output from one other command: $ vmstat -i Adding Jack Vogel to the thread, who might have ideas/comments. Jack, here's the thread: http://lists.freebsd.org/pipermail/freebsd-stable/2010-November/060183.html As for my comments: Unidirectional errors (input or output) often indicates a duplex mismatch or some sort of weird quirk between one link partner and the other. I *have* seen cases where both sides are auto-neg and one side acts like it has the wrong duplex selection despite ifconfig reporting full-duplex and the switch reporting full. Forcing speed and duplex on both ends (requires a managed switch; please don't try this with a
Re: problems with network on em
I don't know about version, but I'm using RELENG_8 branch only. It is FreeBSD 8-STABLE also. Regards, Rolandas Naujikas P.S. I just got ~1Gbit/s (125MB/s,115Kpps) forwarding traffic in testing (24 nodes was downloading a file with wget from server from another side of router), but finally there was some deadlock. I'm recovering the data on it. On 2010.11.20, at 22:37, Jack Vogel wrote: Did you mean the 7.1.7 version from HEAD ? Jack On Sat, Nov 20, 2010 at 11:18 AM, Naujikas Rolandas rolandas.nauji...@mif.vu.lt wrote: I'm trying to test with newest version of /sys/dev/e1000 from FreeBSD 8-STABLE. For that I'm using loadable module option, because it is easier to build with minimal changes in kernel source. Only /sys/dev/e1000 and /sys/modules/em need to be updated. Without changes in /sys/modules/em/Makefile it compiles, but have missing symbol or if you compile static kernel - the same problem. Now I'm testing and it looks promising (except I see a little bigger kernel thread netisr cpu load, but it's acceptable). Regards, Rolandas Naujikas On 2010.11.20, at 19:05, Jeremy Chadwick wrote: On Sat, Nov 20, 2010 at 06:38:19PM +0200, Naujikas Rolandas wrote: I just got another lockup. It looks like in the time of lockup the number of Ierrs is increasing: NameMtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll em21500 Link#3 00:14:4f:XX:XX:XX 13060395 18438 0 6579984 1 0 After ifconfig em2 down;ifconfig em2 up Ierrs stays at 0 rate for long time. Without DEVICE_POLLING it was similar situation. Regards, Rolandas Naujikas On 2010.11.20, at 18:24, rol...@gmail.com wrote: On 2010.11.20, at 17:54, Jeremy Chadwick wrote: On Sat, Nov 20, 2010 at 05:09:28PM +0200, rol...@gmail.com wrote: I'm experiencing network interface stalls on em in FreeBSD 8.1-RELEASE (-p1). It looks like the problem could be solved in 8-STABLE, but should I upgrade to it ? Is it OK to try to get only em driver code and recompile as module and try to run it ? sysctl dev.em.2.stats=1: ... em2: Missed Packets = 101334 em2: Receive No Buffers = 488 ... em2: RX overruns = 1356 em2: watchdog timeouts = 1 ... Only ifconfig em2 down;ifconfig em2 up helps for some time. The same happens on em0 interface only, but not in the same time. It is production (NAT) router with pf+pfsync+carp and failover over another router. They are old SunFire X4100 boxes (4GB RAM, 2*2 AMD Opteron 2.2GHz). You're going to need to provide output from the following, run as root. For the pciconf command, please only include the entry that's relevant to the device in question (em2). You can also XXX-out the MAC address and/or IP addresses if you're worried about security. $ pciconf -lvc e...@pci0:1:2:0: class=0x02 card=0x10118086 chip=0x10108086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'Dual Port Gigabit Ethernet Controller (Copper) (82546EB)' class = network subclass = ethernet cap 01[dc] = powerspec 2 supports D0 D3 current D0 cap 07[e4] = PCI-X 64-bit supports 133MHz, 2048 burst read, 1 split transaction cap 05[f0] = MSI supports 1 message, 64 bit $ dmesg | grep em2 em2: Intel(R) PRO/1000 Legacy Network Connection 1.0.1 port 0x9400-0x943f mem 0xfbfa-0xfbfb irq 24 at device 2.0 on pci1 em2: [FILTER] em2: Ethernet address: 00:14:4f:XX:XX:XX $ sysctl dev.em.2 dev.em.2.%desc: Intel(R) PRO/1000 Legacy Network Connection 1.0.1 dev.em.2.%driver: em dev.em.2.%location: slot=2 function=0 dev.em.2.%pnpinfo: vendor=0x8086 device=0x1010 subvendor=0x8086 subdevice=0x1011 class=0x02 dev.em.2.%parent: pci1 dev.em.2.debug: -1 dev.em.2.stats: -1 dev.em.2.rx_int_delay: 0 dev.em.2.tx_int_delay: 66 dev.em.2.rx_abs_int_delay: 66 dev.em.2.tx_abs_int_delay: 66 dev.em.2.rx_processing_limit: 100 $ uname -a FreeBSD sunfire1.mif 8.1-RELEASE-p1 FreeBSD 8.1-RELEASE-p1 #2: Thu Nov 18 10:39:07 EET 2010 r...@sunfire1.mif:/home/local/obj/usr/src/sys/SUNFIRE amd64 Recompiled with DEVICE_POLLING and HZ=2000, carp and many not used devices removed. $ netstat -ind -I em2 NameMtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll Drop em21500 Link#3 00:14:4f:XX:XX:XX 66430440 101334 0 59339619 1 00 em21500 192.168.0.0/1 192.168.XX.XXX 633845 - - 3815946 - -- ... em01500 Link#1 00:14:4f:XX:XX:XX 167143400 152726 0 143900328 0 00 Regards, Rolandas Naujikas Thanks. Oops, I forgot requesting output from one other command: $ vmstat -i Adding Jack Vogel to the thread, who might have ideas/comments. Jack, here's the thread: http://lists.freebsd.org/pipermail/freebsd-stable/2010-November/060183.html As for my comments: Unidirectional errors (input or output) often indicates a duplex mismatch or some sort of weird quirk between
Re: problems with network on em
I'd appreciate it if you could try and get the driver from HEAD, I will be putting it into STABLE next week, and it would be nice to see if it fixed your problem. It will build in your STABLE environment just fine, do you know how to do this, if not just say so and I can give you further details. Regards, Jack On Sat, Nov 20, 2010 at 1:53 PM, Naujikas Rolandas rolandas.nauji...@mif.vu.lt wrote: I don't know about version, but I'm using RELENG_8 branch only. It is FreeBSD 8-STABLE also. Regards, Rolandas Naujikas P.S. I just got ~1Gbit/s (125MB/s,115Kpps) forwarding traffic in testing (24 nodes was downloading a file with wget from server from another side of router), but finally there was some deadlock. I'm recovering the data on it. On 2010.11.20, at 22:37, Jack Vogel wrote: Did you mean the 7.1.7 version from HEAD ? Jack On Sat, Nov 20, 2010 at 11:18 AM, Naujikas Rolandas rolandas.nauji...@mif.vu.lt wrote: I'm trying to test with newest version of /sys/dev/e1000 from FreeBSD 8-STABLE. For that I'm using loadable module option, because it is easier to build with minimal changes in kernel source. Only /sys/dev/e1000 and /sys/modules/em need to be updated. Without changes in /sys/modules/em/Makefile it compiles, but have missing symbol or if you compile static kernel - the same problem. Now I'm testing and it looks promising (except I see a little bigger kernel thread netisr cpu load, but it's acceptable). Regards, Rolandas Naujikas On 2010.11.20, at 19:05, Jeremy Chadwick wrote: On Sat, Nov 20, 2010 at 06:38:19PM +0200, Naujikas Rolandas wrote: I just got another lockup. It looks like in the time of lockup the number of Ierrs is increasing: NameMtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll em21500 Link#3 00:14:4f:XX:XX:XX 13060395 18438 0 6579984 1 0 After ifconfig em2 down;ifconfig em2 up Ierrs stays at 0 rate for long time. Without DEVICE_POLLING it was similar situation. Regards, Rolandas Naujikas On 2010.11.20, at 18:24, rol...@gmail.com wrote: On 2010.11.20, at 17:54, Jeremy Chadwick wrote: On Sat, Nov 20, 2010 at 05:09:28PM +0200, rol...@gmail.com wrote: I'm experiencing network interface stalls on em in FreeBSD 8.1-RELEASE (-p1). It looks like the problem could be solved in 8-STABLE, but should I upgrade to it ? Is it OK to try to get only em driver code and recompile as module and try to run it ? sysctl dev.em.2.stats=1: ... em2: Missed Packets = 101334 em2: Receive No Buffers = 488 ... em2: RX overruns = 1356 em2: watchdog timeouts = 1 ... Only ifconfig em2 down;ifconfig em2 up helps for some time. The same happens on em0 interface only, but not in the same time. It is production (NAT) router with pf+pfsync+carp and failover over another router. They are old SunFire X4100 boxes (4GB RAM, 2*2 AMD Opteron 2.2GHz). You're going to need to provide output from the following, run as root. For the pciconf command, please only include the entry that's relevant to the device in question (em2). You can also XXX-out the MAC address and/or IP addresses if you're worried about security. $ pciconf -lvc e...@pci0:1:2:0: class=0x02 card=0x10118086 chip=0x10108086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'Dual Port Gigabit Ethernet Controller (Copper) (82546EB)' class = network subclass = ethernet cap 01[dc] = powerspec 2 supports D0 D3 current D0 cap 07[e4] = PCI-X 64-bit supports 133MHz, 2048 burst read, 1 split transaction cap 05[f0] = MSI supports 1 message, 64 bit $ dmesg | grep em2 em2: Intel(R) PRO/1000 Legacy Network Connection 1.0.1 port 0x9400-0x943f mem 0xfbfa-0xfbfb irq 24 at device 2.0 on pci1 em2: [FILTER] em2: Ethernet address: 00:14:4f:XX:XX:XX $ sysctl dev.em.2 dev.em.2.%desc: Intel(R) PRO/1000 Legacy Network Connection 1.0.1 dev.em.2.%driver: em dev.em.2.%location: slot=2 function=0 dev.em.2.%pnpinfo: vendor=0x8086 device=0x1010 subvendor=0x8086 subdevice=0x1011 class=0x02 dev.em.2.%parent: pci1 dev.em.2.debug: -1 dev.em.2.stats: -1 dev.em.2.rx_int_delay: 0 dev.em.2.tx_int_delay: 66 dev.em.2.rx_abs_int_delay: 66 dev.em.2.tx_abs_int_delay: 66 dev.em.2.rx_processing_limit: 100 $ uname -a FreeBSD sunfire1.mif 8.1-RELEASE-p1 FreeBSD 8.1-RELEASE-p1 #2: Thu Nov 18 10:39:07 EET 2010 r...@sunfire1.mif :/home/local/obj/usr/src/sys/SUNFIRE amd64 Recompiled with DEVICE_POLLING and HZ=2000, carp and many not used devices removed. $ netstat -ind -I em2 NameMtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll Drop em21500 Link#3 00:14:4f:XX:XX:XX 66430440 101334 0 59339619 1 00 em21500 192.168.0.0/1 192.168.XX.XXX 633845 - - 3815946 - -- ... em0
Re: problems with network on em
When comparing there (in HEAD) I found many changes, most of them are not related with my hardware. Would it compile on FreeBSD 8.1-RELEASE-p1 ? I could try on secondary router and test it again with 1Gbs traffic. Regards, Rolandas Naujikas On 2010.11.21, at 00:13, Jack Vogel wrote: I'd appreciate it if you could try and get the driver from HEAD, I will be putting it into STABLE next week, and it would be nice to see if it fixed your problem. It will build in your STABLE environment just fine, do you know how to do this, if not just say so and I can give you further details. Regards, Jack On Sat, Nov 20, 2010 at 1:53 PM, Naujikas Rolandas rolandas.nauji...@mif.vu.lt wrote: I don't know about version, but I'm using RELENG_8 branch only. It is FreeBSD 8-STABLE also. Regards, Rolandas Naujikas P.S. I just got ~1Gbit/s (125MB/s,115Kpps) forwarding traffic in testing (24 nodes was downloading a file with wget from server from another side of router), but finally there was some deadlock. I'm recovering the data on it. On 2010.11.20, at 22:37, Jack Vogel wrote: Did you mean the 7.1.7 version from HEAD ? Jack On Sat, Nov 20, 2010 at 11:18 AM, Naujikas Rolandas rolandas.nauji...@mif.vu.lt wrote: I'm trying to test with newest version of /sys/dev/e1000 from FreeBSD 8-STABLE. For that I'm using loadable module option, because it is easier to build with minimal changes in kernel source. Only /sys/dev/e1000 and /sys/modules/em need to be updated. Without changes in /sys/modules/em/Makefile it compiles, but have missing symbol or if you compile static kernel - the same problem. Now I'm testing and it looks promising (except I see a little bigger kernel thread netisr cpu load, but it's acceptable). Regards, Rolandas Naujikas On 2010.11.20, at 19:05, Jeremy Chadwick wrote: On Sat, Nov 20, 2010 at 06:38:19PM +0200, Naujikas Rolandas wrote: I just got another lockup. It looks like in the time of lockup the number of Ierrs is increasing: NameMtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll em21500 Link#3 00:14:4f:XX:XX:XX 13060395 18438 0 6579984 1 0 After ifconfig em2 down;ifconfig em2 up Ierrs stays at 0 rate for long time. Without DEVICE_POLLING it was similar situation. Regards, Rolandas Naujikas On 2010.11.20, at 18:24, rol...@gmail.com wrote: On 2010.11.20, at 17:54, Jeremy Chadwick wrote: On Sat, Nov 20, 2010 at 05:09:28PM +0200, rol...@gmail.com wrote: I'm experiencing network interface stalls on em in FreeBSD 8.1-RELEASE (-p1). It looks like the problem could be solved in 8-STABLE, but should I upgrade to it ? Is it OK to try to get only em driver code and recompile as module and try to run it ? sysctl dev.em.2.stats=1: ... em2: Missed Packets = 101334 em2: Receive No Buffers = 488 ... em2: RX overruns = 1356 em2: watchdog timeouts = 1 ... Only ifconfig em2 down;ifconfig em2 up helps for some time. The same happens on em0 interface only, but not in the same time. It is production (NAT) router with pf+pfsync+carp and failover over another router. They are old SunFire X4100 boxes (4GB RAM, 2*2 AMD Opteron 2.2GHz). You're going to need to provide output from the following, run as root. For the pciconf command, please only include the entry that's relevant to the device in question (em2). You can also XXX-out the MAC address and/or IP addresses if you're worried about security. $ pciconf -lvc e...@pci0:1:2:0: class=0x02 card=0x10118086 chip=0x10108086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'Dual Port Gigabit Ethernet Controller (Copper) (82546EB)' class = network subclass = ethernet cap 01[dc] = powerspec 2 supports D0 D3 current D0 cap 07[e4] = PCI-X 64-bit supports 133MHz, 2048 burst read, 1 split transaction cap 05[f0] = MSI supports 1 message, 64 bit $ dmesg | grep em2 em2: Intel(R) PRO/1000 Legacy Network Connection 1.0.1 port 0x9400-0x943f mem 0xfbfa-0xfbfb irq 24 at device 2.0 on pci1 em2: [FILTER] em2: Ethernet address: 00:14:4f:XX:XX:XX $ sysctl dev.em.2 dev.em.2.%desc: Intel(R) PRO/1000 Legacy Network Connection 1.0.1 dev.em.2.%driver: em dev.em.2.%location: slot=2 function=0 dev.em.2.%pnpinfo: vendor=0x8086 device=0x1010 subvendor=0x8086 subdevice=0x1011 class=0x02 dev.em.2.%parent: pci1 dev.em.2.debug: -1 dev.em.2.stats: -1 dev.em.2.rx_int_delay: 0 dev.em.2.tx_int_delay: 66 dev.em.2.rx_abs_int_delay: 66 dev.em.2.tx_abs_int_delay: 66 dev.em.2.rx_processing_limit: 100 $ uname -a FreeBSD sunfire1.mif 8.1-RELEASE-p1 FreeBSD 8.1-RELEASE-p1 #2: Thu Nov 18 10:39:07 EET 2010 r...@sunfire1.mif :/home/local/obj/usr/src/sys/SUNFIRE amd64 Recompiled with DEVICE_POLLING and HZ=2000, carp and many not used devices removed. $ netstat -ind -I em2 NameMtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll
ahci+zfs+gvinum will panci on boot
On FreeBSD 8.1-release, I was unable to load ahci without causing a system panic. Since recently going to FreeBSD 8.1-STABLE #0: Fri Nov 19 12:17:12 MST, I have been able to boot with ahci loaded as a module but it leaves my two mirrored root-on-zfs main drives as ad devices while attaching to my three gvinum controlled drives so they become ada devices. I tried recompiling my -stable kernel to make ahci take over the disks but found the system goes back to a panic state on boot until I remove loading gvinum from /boot/loader.conf, at which point all disks attach as ada devices. The kernel configuration changes are: --- /usr/src/sys/amd64/conf/GENERIC 2010-10-25 00:58:37.0 -0700 +++ /root/kernels/MYKERNEL8 2010-11-19 12:10:37.362055289 -0700 @@ -95,11 +95,12 @@ # ATA and ATAPI devices device ata -device atadisk # ATA disk drives -device ataraid # ATA RAID drives +device ahci +#deviceatadisk # ATA disk drives +#deviceataraid # ATA RAID drives device atapicd # ATAPI CDROM drives -device atapifd # ATAPI floppy drives -device atapist # ATAPI tape drives +#deviceatapifd # ATAPI floppy drives +#deviceatapist # ATAPI tape drives optionsATA_STATIC_ID # Static device numbering # SCSI Controllers and the panic as best as I could get from a camcorder recording of my screen is: GEOM: new disk ada4 GEOM: ada0s2: geometry does not match label (255,63s != 16h,63s). GEOM: ada1s2: media size does not match label GEOM: ada2s2: geometry does not match label (255,63s != 16h,63s). [possible data skipped due to screen scroll; text is blurry so may contain typos] Instruction pointer = 0x20:0x80546bad stack pointer = 0x28:0xff80e5fa2b20 frame pointer = 0x28:0xff80ef5a2b70 code segment= base 0x0, limit 0xf, type 0x1b = BPL 0, pros 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL=0 current process = 8 (gv_vorker) trap number = 12 panic: page fault cpuid = 0 KDB: stack backtrace: #0 0x805d701e at kdb_backtrace+0x5e #1 0x805a5167 at panic+0x187 #2 0x80890bb0 at trap_fatal+0x290 #3 0x80890f8f at trap_pfault+0x28f #4 0x808917d6 at trap+0x346 #5 0x808766b4 at caclltrap 0x8 #6 0x81035c54 at gv_plex_start+0x154 #7 0x81032362 at gv_worker+0x11f2 #8 0x8057b968 at fork_exit+0x110 #9 0x80876b8e at fork_trampoline+0xe Uptime: 10s Cannot dump. Device not defined or unavailable. Automatic reboot in 15 seconds = press a key on the console to abort. All 5 hard drives are attached to atapci1: ATI IXP700/800 UDMA133 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177, 0x376,0xff00-0xff0f at device 20.1 on pci0 Optical drives are attached to the following two interfaces: ahci0: JMicron JMB363 AHCI SATA controller mem 0xfeafe000-0xfeaf irq 17 at device 0.0 on pci5 atapci0: JMicron JMB363 UDMA133 controller port 0xd800-0xd807,0xd400-0xd403,0x d000-0xd007,0xc800-0xc803,0xc400-0xc40f irq 18 at device 0.1 on pci5 If any further information would be helpful, let me know. I have not been able to get a dump from the panics (which is likely my bad in some way). Maybe I can yank out one of the two 2GB sticks of ram and setup my flash drive as a swap device, but will it be available soon enough? The motherboard doesnt have a serial port connector, but I think there is a header to attach one. If useful, I can look into linking it to my dad's old computer's serial port that way. Edward Sanford Sutton, III ___ 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
