Re: problem with chpass after recent libutil change
On 06/13/2012 23:44, Baptiste Daroussin wrote: On Wed, Jun 13, 2012 at 06:57:38PM +0200, Claude Buisson wrote: Hi, I have some 8-STABLE and 9-STABLE systems which have been upgraded from sources csuped on June 3, and I found that I could no more change the shell for toor: #chpass -s /bin/csh toor chpass: entry inconsistent chpass: pw_copy: Invalid argument and seemingly ONLY for toor. reverting lib/lib/libutil/pw_util.c from r236451 (on 9.X) or r236452 (on 8.X) to the previous version seems to be workaround. Claude Buisson Can you try with the following patch? http://people.freebsd.org/~bapt/add-special-case-for-toor.diff Regards, Bapt All systems now patched. chpass now OK. no known side effect Thanks Claude Buisson ___ 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: su problem
On 6/10/12 1:52 PM, Daniel Braniss wrote: Sami Halabi sodyn...@gmail.com wrote: Hi Oliver, I saw you had similar problem for console on 2010 http://freebsd.1045724.n5.nabble.com/Serial-console-problems-with-stab=le-8-td3950684.html No, I don't think that the problem is related. My problem was with the serial console, while you don't have a serial console attached at all (at least you didn't mention it). but the thread wasn't ended by recommendation or conclusions by you. did you solve that problem then? No, I came to the conclusion that the serial console support in FreeBSD 8 was broken somehow. So I removed the console cable; it's running with an old VGA CRT as the console for now. Fortunately I require console access very seldom, so I don't have to drive to that machine often. It's still annoying, but I didn't find a better solution; downgrading to 7.x isn't an option. just for the record, serial on 8.x works fine! the device naming has changed from sio to uart, and maybe some features. We use it on all our servers, even redirecting it where possible via ILO,IMPI,DRAC. and is great for debuging or saving long trips :-) WARNING: control access to these devices, specialy since root can login on the console! danny Daniel, would you kindly elaborate on the DRAC console redirection thingy ? We're using Dells here and I loathe having to use their web interface and the java app to get a console shell. you need the drac module - sometimes it's optional, but if you can access it via the web you probably have it. you will have to: set the bios to allow serial over ethernet, I can't remember off heart at the moment. configure /boot/loader.conf: console=comconsole,vidconsole comconsole_speed=38400-- the speed is what you set it in the bios configure /boot/device.hints: hint.uart.0.flags=0x10-- or .1. depending on the bios settings install from ports sysutils/ipmitools connect the ethernet port and finaly: ipmitool -A MD5 -H c hostname.drac -U root -I lanplus sol activate danny ___ 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: devd problem with 9-stable
On Thu, 14 Jun 2012 02:41:58 +0200, Kevin Oberman kob6...@gmail.com
wrote:
Since updating my systems to 9-Stable, I am not getting my smartcard
reader attached when hot-plugged.
From devd.conf
attach 50 {
device-name ugen[0-9]+;
match vendor 0x0529;
match product 0x0600;
action /usr/local/sbin/openct-control attach usb:529/600 usb
/dev/$dev$
};
detach 50 {
device-name ugen[0-9]+;
match vendor 0x0529;
match product 0x0600;
action /usr/bin/pkill -fx '/usr/local/sbin/ifdhandler -H -p
[a-z0-9]+ $
};
If I manually enter the action command, it works fine, but it fails
when I insert the device. It worked fine under version 8. I have
confirmed devd is seeing the device inserted just fine. the action
just does not seem to be carried out.
Any idea where I should look? I saw a couple of threads on current
from others seeing something similar, but could find no resolution.
I have seen a
Did you run devd with debug messages on? Options -D and -d are helpful.
If you do does devd match the right devd.conf sections and start the
action?
Ronald.
___
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: ULE Scheduler
At Wed, 13 Jun 2012 17:49:15 +0300, Daniel Kalchev wrote: On 12.06.12 16:08, Momchil Ivanov wrote: So the L2 cache is shared between both cores and hence it's size does not matter at all? If the cache is shared between both cores then it does not matter on which core the process runs, as long as data is in teh case. The cache size is irrelevant. Some CPUs have shared cache between cores, some don't. The ULE scheduler takes this into account, the 4BSD does not. Even if the ULE scheduler takes the CPU topology into consideration, if you only have two cores, it is almost guaranteed that processes will be switched between both, because the OS is running way more than two processes at the same time. Even with more cores... it is not guaranteed an computational process won't be 'bouncing'. Here is an example. Suppose you have an 8 core (or threads) CPU. If you happen to have an modern Ethernet controller, like the Intel 82576 (the igb driver in FreeBSD), then it will use up to 8 interrupt lines, by default routing them each to a different core. Then, if you have heavier network traffic, chances are that at any given moment all 8 interrupts might be fired and all 8 cores switched to service network traffic -- removing your computational process from the running queue. The next time it runs, it might run on any other core, especially if the cache is not shared. Of course, if you have sufficiently large number of CPUs, you can configure your system so that such things do not happen, like by limiting the number of cores the igb driver attaches to, and have some of the cores dedicated to 'only' running an computational task. There is however, very little sense doing so. OK, thank you for the explanation. Regards, Momchil ___ 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
9.1-RELEASE target schedule
Just a quick note to say we have settled on a target schedule for the FreeBSD 9.1 Release. The schedule itself is here: http://www.freebsd.org/releases/9.1R/schedule.html The highlights: Code Freeze:July 2nd, 2012 BETA1: July 6th, 2012 RC1:July 20th, 2012 RC2:August 3rd, 2012 Release:August 13th, 2012 Those are the target dates for when builds start. The builds becoming available is usually a few days afterwards (except for the final release which is often times 4 days to a week after the builds start because there is more prep work involved...). Thanks. -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | signature.asc Description: This is a digitally signed message part
Re: Boot hangs on v9 system at CD device probe
On Tue, Jun 12, 2012 at 03:17:47PM -0700, Kevin Oberman wrote: On Sat, Jun 9, 2012 at 3:29 PM, Marius Strobl mar...@alchemy.franken.de wrote: On Sat, Jun 09, 2012 at 02:38:53PM -0700, Kevin Oberman wrote: On Sat, Jun 9, 2012 at 5:13 AM, Marius Strobl mar...@alchemy.franken.de wrote: On Fri, Jun 08, 2012 at 10:11:48PM -0700, Kevin Oberman wrote: On Thu, May 31, 2012 at 9:10 AM, Kevin Oberman kob6...@gmail.com wrote: I just did the obvious as suggested and built a kernel without ATA_CAM and with atapicam. It boots fine and I have my CD/DVD working on 9.0. Clearly, there is some issue with ATAPI drives with ATA_CAM as others have seen the same thing. It is entirely possible that a serial connected drives don't have this issue. It does look like there is some locking issue between CAM and GEOM under some circumstances. I worry that 10 will lose support for other than ATA_CAM and that the work-around will no longer be available. Of course, if ahci fixes it, the problem will go away on systems that support it. Next time I get to the system I will try putting ATA_CAM back and adding ahci and report on the results. I don't think that the latter test makes much sense as the above mentioned controller doesn't support AHCI. If you could test whether the following patch works around the issue when using ATA_CAM that would be more useful. http://people.freebsd.org/~marius/ata_ite_ATA_CAM_ATA_NO_ATAPI_DMA.diff Will do. It will be a couple of days, though, as I am currently in the process of updating the 1000 ports installed on that system for the major version update. When that is complete, I'll try to get to the location of the system and see if it does the job. Mondy has several meetings, so it will probably be at least Tuesday. No hurry ... I installed the patch and it worked. 9.0-Stable system with ATA_CAM and cdrom now boot correctly. Thanks! Will this be committed to head and MFCed soon? I've committed it to head in r237107 as a band-aid for now as it's a sufficiently severe problem. Obviously, fixing ATA_CAM to not break ATAPI CAM instead is the right thing to do. I've already spent quite some time trying to find the underlying but didn't get anywhere with that so far though (granted, most of that wasted time was because of me thinking that this would be due to an endian bug only seen on big endian machines, which turned out to not be the case). AFAICT, mav@ also has ALI hardware affected by this issue, maybe he'll have a look at it eventually ... Marius ___ 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: ATI Mobility Radeon HD 5470
On Thu, 2012-06-07 at 14:25 -0700, Vladimir Vasilenko wrote: Hello. Can I use this video card with FreeBSD? If yes so, where I can driver download? Best regards, Vladimir Vasilenko vladi...@shumbely.com I don't know if anyone responded to your question here. I suspect that the latest updates to xorg that have occured in freebsd will support your video card. There is no driver to download for this, it is provided via the xorg installation, but you will have to update your system. You may want to try pc-bsd http://pcbsd.org if you're looking to setup a fully functional desktop-like PC. Sean ref. http://miwi.bsdcrew.de/2012/06/cft-xorg-7-7-ready-for-testing/ ___ 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: ATI Mobility Radeon HD 5470
On Thu, Jun 14, 2012 at 05:40:26PM -0700 I heard the voice of Sean Bruno, and lo! it spake thus: I don't know if anyone responded to your question here. I suspect that the latest updates to xorg that have occured in freebsd will support your video card. That's an Evergreen. UMS support is going to be very skimpy. -- Matthew Fuller (MF4839) | fulle...@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ 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 and IPMI how-to (was Re: su problem)
Daniel Braniss writes: just for the record, serial on 8.x works fine! the device naming has changed from sio to uart, and maybe some features. We use it on all our servers, even redirecting it where possible via ILO,IMPI,DRAC. and is great for debuging or saving long trips :-) Would some kind soul point me to a howto for configuring IPMI on FreeBSD? I have a Dell PowerEdge 840 that supports IPMI, but I have no idea how to set it up - either in the BIOS or in FreeBSD. I've messed around with ipmitools a little, but I haven't gotten it to work. Best wishes, Matthew -- I FIGHT FOR THE USERS smime.p7s Description: S/MIME cryptographic signature
Re: FreeBSD and IPMI how-to (was Re: su problem)
On Thu, 2012-06-14 at 18:27 -0700, Matthew X. Economou wrote: Daniel Braniss writes: just for the record, serial on 8.x works fine! the device naming has changed from sio to uart, and maybe some features. We use it on all our servers, even redirecting it where possible via ILO,IMPI,DRAC. and is great for debuging or saving long trips :-) Would some kind soul point me to a howto for configuring IPMI on FreeBSD? I have a Dell PowerEdge 840 that supports IPMI, but I have no idea how to set it up - either in the BIOS or in FreeBSD. I've messed around with ipmitools a little, but I haven't gotten it to work. Best wishes, Matthew I would start with installing the ipmitool port. Other may suggest freeipmi and openipmi for great justice. try poking around with sudo ipmitool shell and see if you can figure out what's going on. Sean ___ 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
[releng_8 tinderbox] failure on arm/arm
TB --- 2012-06-15 02:52:03 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-06-15 02:52:03 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-06-15 02:52:03 - starting RELENG_8 tinderbox run for arm/arm TB --- 2012-06-15 02:52:03 - cleaning the object tree TB --- 2012-06-15 02:52:03 - cvsupping the source tree TB --- 2012-06-15 02:52:03 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8/arm/arm/supfile TB --- 2012-06-15 02:52:19 - building world TB --- 2012-06-15 02:52:19 - CROSS_BUILD_TESTING=YES TB --- 2012-06-15 02:52:19 - MAKEOBJDIRPREFIX=/obj TB --- 2012-06-15 02:52:19 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-06-15 02:52:19 - SRCCONF=/dev/null TB --- 2012-06-15 02:52:19 - TARGET=arm TB --- 2012-06-15 02:52:19 - TARGET_ARCH=arm TB --- 2012-06-15 02:52:19 - TZ=UTC TB --- 2012-06-15 02:52:19 - __MAKE_CONF=/dev/null TB --- 2012-06-15 02:52:19 - cd /src TB --- 2012-06-15 02:52:19 - /usr/bin/make -B buildworld World build started on Fri Jun 15 02:52:20 UTC 2012 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 Fri Jun 15 03:29:27 UTC 2012 TB --- 2012-06-15 03:29:27 - cd /src/sys/arm/conf TB --- 2012-06-15 03:29:27 - /usr/sbin/config -m AVILA TB --- 2012-06-15 03:29:27 - building AVILA kernel TB --- 2012-06-15 03:29:27 - CROSS_BUILD_TESTING=YES TB --- 2012-06-15 03:29:27 - MAKEOBJDIRPREFIX=/obj TB --- 2012-06-15 03:29:27 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-06-15 03:29:27 - SRCCONF=/dev/null TB --- 2012-06-15 03:29:27 - TARGET=arm TB --- 2012-06-15 03:29:27 - TARGET_ARCH=arm TB --- 2012-06-15 03:29:27 - TZ=UTC TB --- 2012-06-15 03:29:27 - __MAKE_CONF=/dev/null TB --- 2012-06-15 03:29:27 - cd /src TB --- 2012-06-15 03:29:27 - /usr/bin/make -B buildkernel KERNCONF=AVILA Kernel build for AVILA started on Fri Jun 15 03:29:27 UTC 2012 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 Kernel build for AVILA completed on Fri Jun 15 03:31:23 UTC 2012 TB --- 2012-06-15 03:31:23 - cd /src/sys/arm/conf TB --- 2012-06-15 03:31:23 - /usr/sbin/config -m BWCT TB --- 2012-06-15 03:31:23 - building BWCT kernel TB --- 2012-06-15 03:31:23 - CROSS_BUILD_TESTING=YES TB --- 2012-06-15 03:31:23 - MAKEOBJDIRPREFIX=/obj TB --- 2012-06-15 03:31:23 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-06-15 03:31:23 - SRCCONF=/dev/null TB --- 2012-06-15 03:31:23 - TARGET=arm TB --- 2012-06-15 03:31:23 - TARGET_ARCH=arm TB --- 2012-06-15 03:31:23 - TZ=UTC TB --- 2012-06-15 03:31:23 - __MAKE_CONF=/dev/null TB --- 2012-06-15 03:31:23 - cd /src TB --- 2012-06-15 03:31:23 - /usr/bin/make -B buildkernel KERNCONF=BWCT Kernel build for BWCT started on Fri Jun 15 03:31:23 UTC 2012 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 -mlittle-endian -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 -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 -mcpu=arm9 -ffreestanding -Werror /src/sys/arm/at91/at91_pio.c cc -mlittle-endian -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 -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 -mcpu=arm9 -ffreestanding -Werror /src/sys/arm/at91/at91_pmc.c cc -mlittle-endian -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 -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 -mcpu=arm9 -ffreestanding -Werror
mfi(4) IO performance regression, post 8.1
Hello FreeBSD folk, We're seeing what appears to be a storage performance regression as we try to move from 8.1 (i386) to 8.3. We looked at 8.2 also and it appears that the regression happened between 8.1 and 8.2. Our system is an Intel S5520UR Server with 12 GB RAM, dual 4-core CPUs. Storage is a LSI MegaSAS 1078 controller (mfi) in a RAID-10 configuration, using UFS + geom_journal for filesystem. Postgresql performance, as seen via pgbench, dropped by approx 20%. This testing was done with our usual PAE-enabled kernels. We then went back to GENERIC kernels and did comparisons using bonnie, results below. Following that is a kernel boot log. Notably, we're seeing this regression only with our RAID mfi(4) based systems. Notably, from looking at FreeBSD source changelogs it appears that the mfi(4) code has seen some changes since 8.1. How can I investigate further? Assistance with sorting this out would be greatly appreciated. Thanks much, Charles Bonnie comparison 8.3 GENERIC ---Sequential Output ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MachineMB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU 100 93580 98.3 82136 26.6 113709 78.8 152081 98.8 3223876 100.0 233590.3 240.4 8.2 GENERIC ---Sequential Output ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MachineMB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU 100 95923 99.1 84042 56.7 110568 69.8 152088 100.6 4290802 82.8 239779.4 234.5 8.1 GENERIC ---Sequential Output ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MachineMB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU 100 140708 100.0 164261 44.4 208553 48.5 153472 100.0 3298756 100.0 270325.1 238.4 Copyright (c) 1992-2010 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.1-RELEASE-p8 #1: Fri Jan 6 12:13:34 EST 2012 cow...@newcastle.greatbaysoftware.com:/usr/obj/usr/relbuild/os/RELENG_8_1/sys/GENERIC i386 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU E5530 @ 2.40GHz (2394.28-MHz 686-class CPU) Origin = GenuineIntel Id = 0x106a5 Family = 6 Model = 1a Stepping = 5 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x9ce3bdSSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,SSE4.1,SSE4.2,POPCNT AMD Features=0x2810NX,RDTSCP,LM AMD Features2=0x1LAHF TSC: P-state invariant real memory = 12884901888 (12288 MB) avail memory = 2289147904 (2183 MB) ACPI APIC Table:INTEL S5520UR FreeBSD/SMP: Multiprocessor System Detected: 16 CPUs FreeBSD/SMP: 2 package(s) x 4 core(s) x 2 SMT threads cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 cpu8 (AP): APIC ID: 16 cpu9 (AP): APIC ID: 17 cpu10 (AP): APIC ID: 18 cpu11 (AP): APIC ID: 19 cpu12 (AP): APIC ID: 20 cpu13 (AP): APIC ID: 21 cpu14 (AP): APIC ID: 22 cpu15 (AP): APIC ID: 23 ioapic0Version 2.0 irqs 0-23 on motherboard ioapic1Version 2.0 irqs 24-47 on motherboard lapic0: Forcing LINT1 to edge trigger kbd0 at kbdmux0 acpi0:INTEL S5520UR on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0:24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 cpu0:ACPI CPU on acpi0 cpu1:ACPI CPU on acpi0 cpu2:ACPI CPU on acpi0 cpu3:ACPI CPU on acpi0 cpu4:ACPI CPU on acpi0 cpu5:ACPI CPU on acpi0 cpu6:ACPI CPU on acpi0 cpu7:ACPI CPU on acpi0 cpu8:ACPI CPU on acpi0 cpu9:ACPI CPU on acpi0 cpu10:ACPI CPU on acpi0 cpu11:ACPI CPU on acpi0 cpu12:ACPI CPU on acpi0 cpu13:ACPI CPU on acpi0 cpu14:ACPI CPU on acpi0 cpu15:ACPI CPU on acpi0 acpi_hpet0:High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0 Timecounter HPET frequency 14318180 Hz quality 900 pcib0:ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0:ACPI PCI bus on pcib0 pcib1:ACPI PCI-PCI bridge irq 28 at device 1.0 on pci0 pci1:ACPI PCI bus on pcib1 igb0:Intel(R) PRO/1000 Network Connection version - 1.9.5 port 0x4020-0x403f mem 0xb1f2-0xb1f3,0xb1f44000-0xb1f47fff irq 40 at device 0.0 on pci1 igb0: Using MSIX interrupts with 5 vectors igb0: [ITHREAD] igb0: [ITHREAD] igb0: [ITHREAD] igb0: [ITHREAD] igb0: [ITHREAD] igb0: Ethernet address: 00:15:17:f2:1b:a0 igb1:Intel(R) PRO/1000 Network Connection version
Re: mfi(4) IO performance regression, post 8.1
Hm, can you try different subversion checkouts of the kernel tree between 8.1 and 8.3, to pinpoint which commit(s) broke things? ADrian ___ 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
