[Cannot allocate memory][Qemu][x86 i386] limits ? login.conf ?
Hi all. I experiment qemu problems while playing with emulators/virtual machines ... When I try to create any virtual machines with x86_64 or i 386 hardware and more than 256Mo ram that fail. Qemu returns Cannot allocate memory. I tryied to modify login.conf ulimits values, but this still fail. I randomly ... YES RANDOMLY discover ram values are limited to exact values between : 256 512Mo ram allocable ...no more ... no less... on a test setup with the laptop. How I discoverd that ? like this : $ M=2048 $ while : ; do qeum-system-i386 -m $M ; M=$(( $M - 1 )) ; echo $M ; done ; unset M So I let this run until VM starts, then I look the last $M value. Qemu documentation says ram limit is 2047Mo for both i386 x86_64 Anyway Qemu with ram values between 512 846 are just working very fine ... Can check my actual setup in attached file. On this machine Qemu machines ram is limited to 256Mo (with no modifications of ulimits neither in login.conf I don't understand where is the problem. This doesn't seem to cause any hangs, bugs or warning in system log files... Any help or Ideas about that ? FYI : any other hardware emulated seems to work with its own maximum supported ram for example : $ qemu-system-sparc -machine SS-20 -smp 4 -m 768 just works fine on same machine... Max values I have tried in login.conf were : default:\ :path=/usr/bin /bin /usr/sbin /sbin /usr/X11R6/bin /usr/local/bin /usr/local/sbin:\ :umask=022:\ :datasize-max=2048M:\ :datasize-cur=2024M:\ :maxproc-max=512:\ :maxproc-cur=256:\ :vmemoryuse=1024:\ :openfiles-cur=1024:\ :stacksize-cur=8M:\ :localcipher=blowfish,6:\ :ypcipher=old:\ :tc=auth-defaults:\ :tc=auth-ftp-defaults: Cordialement Francois Pussault 10 chemin de négo saoumos apt 202 - bat 2 31300 Toulouse +33 6 17 230 820  +33 5 34 365 269 fpussa...@contactoffice.fr OpenBSD 5.5 (GENERIC.MP) #315: Wed Mar 5 09:37:46 MST 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17161342976 (16366MB) avail mem = 16695902208 (15922MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xee000 (71 entries) bios0: vendor HP version P56 date 11/13/2007 bios0: HP ProLiant DL380 G5 acpi0 at bios0: rev 2 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP SPCR MCFG HPET SPMI ERST APIC BERT HEST acpi0: wakeup devices acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Xeon(R) CPU E5345 @ 2.33GHz, 2333.67 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,LONG,LAHF,PERF cpu0: 4MB 64b/line 16-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 333MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.2.0, IBE cpu1 at mainbus0: apid 4 (application processor) cpu1: Intel(R) Xeon(R) CPU E5345 @ 2.33GHz, 2332.51 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,LONG,LAHF,PERF cpu1: 4MB 64b/line 16-way L2 cache cpu1: smt 0, core 0, package 1 cpu2 at mainbus0: apid 2 (application processor) cpu2: Intel(R) Xeon(R) CPU E5345 @ 2.33GHz, 2332.51 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,LONG,LAHF,PERF cpu2: 4MB 64b/line 16-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Xeon(R) CPU E5345 @ 2.33GHz, 2332.51 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,LONG,LAHF,PERF cpu3: 4MB 64b/line 16-way L2 cache cpu3: smt 0, core 2, package 1 cpu4 at mainbus0: apid 1 (application processor) cpu4: Intel(R) Xeon(R) CPU E5345 @ 2.33GHz, 2332.51 MHz cpu4: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,LONG,LAHF,PERF cpu4: 4MB 64b/line 16-way L2 cache cpu4: smt 0, core 1, package 0 cpu5 at mainbus0: apid 5 (application processor) cpu5: Intel(R) Xeon(R) CPU E5345 @ 2.33GHz, 2332.51 MHz cpu5: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,LONG,LAHF,PERF cpu5: 4MB 64b/line 16-way L2 cache cpu5: smt 0, core 1,
ACPI0 Interrupts and System Time
Hello, I've got a few machines I'm setting up which I noticed ACPI0 is generating a lot of constant interrupts which appears to be consuming system time on CPU0 up to 80%. I think other interrupts are still getting time to process, but I'm not sure if it could still cause a performance impact as I'm looking to use these systems to handle filtering and queuing on the edge of our network. Any ideas or suggestions would be appreciated. The systems are Dell R620, dmesg below. OpenBSD 5.5-stable (GENERIC.MP) #3: Sun May 11 18:30:30 CDT 2014 r...@build.kncm.net:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 34295709696 (32706MB) avail mem = 33374154752 (31828MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xcf42c000 (99 entries) bios0: vendor Dell Inc. version 2.2.2 date 01/16/2014 bios0: Dell Inc. PowerEdge R620 acpi0 at bios0: rev 2 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP APIC SPCR HPET DMAR MCFG WD__ SLIC ERST HEST BERT EINJ TCPA PC__ SRAT SSDT acpi0: wakeup devices PCI0(S5) PCI1(S5) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 4 (boot processor) cpu0: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.45 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 2, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 100MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1.0, IBE cpu1 at mainbus0: apid 6 (application processor) cpu1: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 3, package 0 cpu2 at mainbus0: apid 8 (application processor) cpu2: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 4, package 0 cpu3 at mainbus0: apid 16 (application processor) cpu3: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 8, package 0 cpu4 at mainbus0: apid 18 (application processor) cpu4: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu4: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu4: 256KB 64b/line 8-way L2 cache cpu4: smt 0, core 9, package 0 cpu5 at mainbus0: apid 20 (application processor) cpu5: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu5: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu5: 256KB 64b/line 8-way L2 cache cpu5: smt 0, core 10, package 0 cpu6 at mainbus0: apid 5 (application processor) cpu6: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu6: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu6: 256KB 64b/line 8-way L2 cache cpu6: smt 1, core 2, package 0 cpu7 at mainbus0: apid 7 (application processor) cpu7: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu7:
Re: ACPI0 Interrupts and System Time
Josh Hoppes [josh.hop...@gmail.com] wrote: Hello, I've got a few machines I'm setting up which I noticed ACPI0 is generating a lot of constant interrupts which appears to be consuming system time on CPU0 up to 80%. I think other interrupts are still getting time to process, but I'm not sure if it could still cause a performance impact as I'm looking to use these systems to handle filtering and queuing on the edge of our network. Any ideas or suggestions would be appreciated. For your interrupt storm, you might want to test the latest BIOS and/or the latest OpenBSD snapshot to see where things are at. For your system in general, you'll get the best performance by disabling hyper-threading, and if your CPU supports turbo mode, enable that.
Re: PF queuing max bandwidth
* Matt Carey cvstealth2...@yahoo.com [2014-07-15 03:18]:
While trying to upgrade a pf ruleset from 5.4 to 5.5 and make use of the new
queuing system, I'm running into an issue where the traffic isn't getting
throttled to what I set for a max on a given queue.
Below is the old ruleset that works well under 5.4:
altq on trunk0 bandwidth 9.70Mb hfsc queue { q_voip, q_normal}
queue q_voip bandwidth 1Mb hfsc(realtime 1Mb)
queue q_normal bandwidth 8.70Mb qlimit 500 hfsc(default red ecn upperlimit
8.70Mb)
Belw is the new ruleset that I have for 5.5:
queue std on trunk0 bandwidth 10M, max 10M
queue q_voip parent std bandwidth 1M, min 1M qlimit 500
queue q_normal parent std bandwidth 8M, max 8M default qlimit 500
When looking at the measured throughput on the q_normal queue it isn't being
ceilinged @ the 8MB from the config:
# pfctl - -s queue
queue std on trunk0 bandwidth 10M, max 10M qlimit 50
[ pkts: 0 bytes: 0 dropped pkts: 0 bytes: 0 ]
[ qlength: 0/ 50 ]
[ measured: 0.0 packets/s, 0 b/s ]
queue q_voip parent std on trunk0 bandwidth 1M, min 1M qlimit 500
[ pkts: 90 bytes: 57032 dropped pkts: 0 bytes: 0 ]
[ qlength: 0/500 ]
[ measured: 3.4 packets/s, 19.38Kb/s ]
queue q_normal parent std on trunk0 bandwidth 8M, max 8M default qlimit 500
[ pkts: 101676 bytes: 98995630 dropped pkts: 0 bytes: 0 ]
[ qlength: 0/500 ]
[ measured: 1192.5 packets/s, 9.32Mb/s ]
The interface config is pretty simple, 2 ports bundled together into a LACP
trunk then WAN hangs off a vlan on that trunk. Any help would be appreciated.
really sounds like you're getting into the ballpark area where the
timer resolution isn't good enough to hit your rather small bandwidth
on - assumption here - rather high bandwidth interfaces.
--
Henning Brauer, h...@bsws.de, henn...@openbsd.org
BS Web Services GmbH, http://bsws.de, Full-Service ISP
Secure Hosting, Mail and DNS. Virtual Dedicated Servers, Root to Fully Managed
Henning Brauer Consulting, http://henningbrauer.com/
Re: ACPI0 Interrupts and System Time
On Wed, Jul 16, 2014 at 08:55:15AM -0500, Josh Hoppes wrote: Hello, I've got a few machines I'm setting up which I noticed ACPI0 is generating a lot of constant interrupts which appears to be consuming system time on CPU0 up to 80%. I think other interrupts are still getting time to process, but I'm not sure if it could still cause a performance impact as I'm looking to use these systems to handle filtering and queuing on the edge of our network. Any ideas or suggestions would be appreciated. The systems are Dell R620, dmesg below. We saw (and kettenis@ fixed) a similar issue on this machine in late June. Can you please try a snap from a later date? I'd say at least July 1 or later. -ml OpenBSD 5.5-stable (GENERIC.MP) #3: Sun May 11 18:30:30 CDT 2014 r...@build.kncm.net:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 34295709696 (32706MB) avail mem = 33374154752 (31828MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xcf42c000 (99 entries) bios0: vendor Dell Inc. version 2.2.2 date 01/16/2014 bios0: Dell Inc. PowerEdge R620 acpi0 at bios0: rev 2 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP APIC SPCR HPET DMAR MCFG WD__ SLIC ERST HEST BERT EINJ TCPA PC__ SRAT SSDT acpi0: wakeup devices PCI0(S5) PCI1(S5) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 4 (boot processor) cpu0: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.45 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 2, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 100MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1.0, IBE cpu1 at mainbus0: apid 6 (application processor) cpu1: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 3, package 0 cpu2 at mainbus0: apid 8 (application processor) cpu2: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 4, package 0 cpu3 at mainbus0: apid 16 (application processor) cpu3: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 8, package 0 cpu4 at mainbus0: apid 18 (application processor) cpu4: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu4: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu4: 256KB 64b/line 8-way L2 cache cpu4: smt 0, core 9, package 0 cpu5 at mainbus0: apid 20 (application processor) cpu5: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu5: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu5: 256KB 64b/line 8-way L2 cache cpu5: smt 0, core 10, package 0 cpu6 at mainbus0: apid 5 (application processor) cpu6: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu6: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu6: 256KB 64b/line 8-way L2 cache cpu6: smt 1, core 2, package 0 cpu7 at mainbus0: apid
Re: ACPI0 Interrupts and System Time
Would there happen to be any pre-built snapshots that are known good? This is a short term event and I don't a lot of time to work since doors open tomorrow morning. Was the fix kernel only and would that work with my existing userland or has there been a significant enough change that I would need to do a full upgrade? Thanks for the help so far! On Wed, Jul 16, 2014 at 11:04 AM, Mike Larkin mlar...@azathoth.net wrote: On Wed, Jul 16, 2014 at 08:55:15AM -0500, Josh Hoppes wrote: Hello, I've got a few machines I'm setting up which I noticed ACPI0 is generating a lot of constant interrupts which appears to be consuming system time on CPU0 up to 80%. I think other interrupts are still getting time to process, but I'm not sure if it could still cause a performance impact as I'm looking to use these systems to handle filtering and queuing on the edge of our network. Any ideas or suggestions would be appreciated. The systems are Dell R620, dmesg below. We saw (and kettenis@ fixed) a similar issue on this machine in late June. Can you please try a snap from a later date? I'd say at least July 1 or later. -ml OpenBSD 5.5-stable (GENERIC.MP) #3: Sun May 11 18:30:30 CDT 2014 r...@build.kncm.net:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 34295709696 (32706MB) avail mem = 33374154752 (31828MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xcf42c000 (99 entries) bios0: vendor Dell Inc. version 2.2.2 date 01/16/2014 bios0: Dell Inc. PowerEdge R620 acpi0 at bios0: rev 2 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP APIC SPCR HPET DMAR MCFG WD__ SLIC ERST HEST BERT EINJ TCPA PC__ SRAT SSDT acpi0: wakeup devices PCI0(S5) PCI1(S5) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 4 (boot processor) cpu0: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.45 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 2, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 100MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1.0, IBE cpu1 at mainbus0: apid 6 (application processor) cpu1: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 3, package 0 cpu2 at mainbus0: apid 8 (application processor) cpu2: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 4, package 0 cpu3 at mainbus0: apid 16 (application processor) cpu3: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 8, package 0 cpu4 at mainbus0: apid 18 (application processor) cpu4: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu4: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu4: 256KB 64b/line 8-way L2 cache cpu4: smt 0, core 9, package 0 cpu5 at mainbus0: apid 20 (application processor) cpu5: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu5: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu5: 256KB 64b/line 8-way L2 cache cpu5: smt 0, core 10, package 0 cpu6 at mainbus0: apid 5 (application processor) cpu6: Intel(R) Xeon(R) CPU E5-2643 v2 @
My USB KVM seems to work 100% now
http://marc.info/?t=13604368593r=1w=2 This seems to be fixed in the July 13 snapshot. I no longer have to insert/remove my USB stick to get the keyboard working. THANKS! Kent.
Re: ACPI0 Interrupts and System Time
On Wed, Jul 16, 2014 at 11:36:21AM -0500, Josh Hoppes wrote: Would there happen to be any pre-built snapshots that are known good? This is a short term event and I don't a lot of time to work since doors open tomorrow morning. Was the fix kernel only and would that work with my existing userland or has there been a significant enough change that I would need to do a full upgrade? Thanks for the help so far! The change was just in the kernel, but unless you wanted to go and pull out that one patch and apply it to an older tree, you might be better off installing a complete snap. I've been told there are older snaps kept here: http://ftp.hostserver.de/archive I'd grab one from between 26 Jun and 6 July. Much later than 6 July and you run the risk of running into the hackathon commits, which sometimes destabilize the tree for a short time. The pair of commits I think you may need were made on 23 Jul and 25 Jul (the 23 Jul diff being the more relevant one for your issue). -ml On Wed, Jul 16, 2014 at 11:04 AM, Mike Larkin mlar...@azathoth.net wrote: On Wed, Jul 16, 2014 at 08:55:15AM -0500, Josh Hoppes wrote: Hello, I've got a few machines I'm setting up which I noticed ACPI0 is generating a lot of constant interrupts which appears to be consuming system time on CPU0 up to 80%. I think other interrupts are still getting time to process, but I'm not sure if it could still cause a performance impact as I'm looking to use these systems to handle filtering and queuing on the edge of our network. Any ideas or suggestions would be appreciated. The systems are Dell R620, dmesg below. We saw (and kettenis@ fixed) a similar issue on this machine in late June. Can you please try a snap from a later date? I'd say at least July 1 or later. -ml OpenBSD 5.5-stable (GENERIC.MP) #3: Sun May 11 18:30:30 CDT 2014 r...@build.kncm.net:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 34295709696 (32706MB) avail mem = 33374154752 (31828MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xcf42c000 (99 entries) bios0: vendor Dell Inc. version 2.2.2 date 01/16/2014 bios0: Dell Inc. PowerEdge R620 acpi0 at bios0: rev 2 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP APIC SPCR HPET DMAR MCFG WD__ SLIC ERST HEST BERT EINJ TCPA PC__ SRAT SSDT acpi0: wakeup devices PCI0(S5) PCI1(S5) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 4 (boot processor) cpu0: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.45 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 2, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 100MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1.0, IBE cpu1 at mainbus0: apid 6 (application processor) cpu1: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 3, package 0 cpu2 at mainbus0: apid 8 (application processor) cpu2: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 4, package 0 cpu3 at mainbus0: apid 16 (application processor) cpu3: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 8, package 0 cpu4 at mainbus0: apid 18 (application processor) cpu4: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu4:
Re: ACPI0 Interrupts and System Time
On Wed, Jul 16, 2014 at 09:51:12AM -0700, Mike Larkin wrote: On Wed, Jul 16, 2014 at 11:36:21AM -0500, Josh Hoppes wrote: Would there happen to be any pre-built snapshots that are known good? This is a short term event and I don't a lot of time to work since doors open tomorrow morning. Was the fix kernel only and would that work with my existing userland or has there been a significant enough change that I would need to do a full upgrade? Thanks for the help so far! The change was just in the kernel, but unless you wanted to go and pull out that one patch and apply it to an older tree, you might be better off installing a complete snap. I've been told there are older snaps kept here: http://ftp.hostserver.de/archive I'd grab one from between 26 Jun and 6 July. Much later than 6 July and you run the risk of running into the hackathon commits, which sometimes destabilize the tree for a short time. The pair of commits I think you may need were made on 23 Jul and 25 Jul (the 23 Jul diff being the more relevant one for your issue). Should have been 23 Jun and 25 Jun there ... -ml On Wed, Jul 16, 2014 at 11:04 AM, Mike Larkin mlar...@azathoth.net wrote: On Wed, Jul 16, 2014 at 08:55:15AM -0500, Josh Hoppes wrote: Hello, I've got a few machines I'm setting up which I noticed ACPI0 is generating a lot of constant interrupts which appears to be consuming system time on CPU0 up to 80%. I think other interrupts are still getting time to process, but I'm not sure if it could still cause a performance impact as I'm looking to use these systems to handle filtering and queuing on the edge of our network. Any ideas or suggestions would be appreciated. The systems are Dell R620, dmesg below. We saw (and kettenis@ fixed) a similar issue on this machine in late June. Can you please try a snap from a later date? I'd say at least July 1 or later. -ml OpenBSD 5.5-stable (GENERIC.MP) #3: Sun May 11 18:30:30 CDT 2014 r...@build.kncm.net:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 34295709696 (32706MB) avail mem = 33374154752 (31828MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xcf42c000 (99 entries) bios0: vendor Dell Inc. version 2.2.2 date 01/16/2014 bios0: Dell Inc. PowerEdge R620 acpi0 at bios0: rev 2 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP APIC SPCR HPET DMAR MCFG WD__ SLIC ERST HEST BERT EINJ TCPA PC__ SRAT SSDT acpi0: wakeup devices PCI0(S5) PCI1(S5) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 4 (boot processor) cpu0: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.45 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 2, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 100MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1.0, IBE cpu1 at mainbus0: apid 6 (application processor) cpu1: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 3, package 0 cpu2 at mainbus0: apid 8 (application processor) cpu2: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 4, package 0 cpu3 at mainbus0: apid 16 (application processor) cpu3: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 8, package 0 cpu4 at mainbus0: apid 18 (application processor) cpu4: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu4:
Re: ACPI0 Interrupts and System Time
The change was just in the kernel, but unless you wanted to go and pull out that one patch and apply it to an older tree, you might be better off installing a complete snap. Ok, I was hoping I could just drop in the kernel from a snapshot since it's harder to revert from an full upgrade in a timely fashion.
Failing to receive message with MSG_OOB
Hi folks, I am trying to observe the effect of MSG_OOB while receiving data. I have a small demo program that creates an accepting socket, connect a sending socket to the accepting, closes the accepting socket to keep only the sending and the receiving, forks, and handle receive on the parent and send on the child. No flags of any kinds are set. write(send_sk, (void *)payload, sizeof(payload)) / read(recv_sk, (void *)payload, sizeof(payload)) = no problem. sendto(send_sk, (void *)payload, sizeof(payload), 0, NULL, 0) / recvfrom(recv_sk, (void *)payload, sizeof(payload), 0, NULL, 0) = no problem. sendto(send_sk, (void *)payload, sizeof(payload), MSG_OOB, NULL, 0) / recvfrom(recv_sk, (void *)payload, sizeof(payload), 0, NULL, 0) = fails with errno = 0, and tcpdump shows me the packet with the URG flag set. sendto(send_sk, (void *)payload, sizeof(payload), MSG_OOB, NULL, 0) / recvfrom(recv_sk, (void *)payload, sizeof(payload), MSG_OOB, NULL, 0) = fails with EINVAL on the receiving end, and tcpdump shows me the packet with the URG flag set. Did I miss something on the man pages ? or is it something more sinister ? Thnaks for your time -- Vincent / dermiste [demime 1.01d removed an attachment of type application/pgp-signature]
Re: Failing to receive message with MSG_OOB
On Wed, 16 Jul 2014, Vincent Gross wrote: I am trying to observe the effect of MSG_OOB while receiving data. I have a small demo program that creates an accepting socket, connect a sending socket to the accepting, closes the accepting socket to keep only the sending and the receiving, forks, and handle receive on the parent and send on the child. No flags of any kinds are set. write(send_sk, (void *)payload, sizeof(payload)) / read(recv_sk, (void *)payload, sizeof(payload)) = no problem. sendto(send_sk, (void *)payload, sizeof(payload), 0, NULL, 0) / recvfrom(recv_sk, (void *)payload, sizeof(payload), 0, NULL, 0) = no problem. sendto(send_sk, (void *)payload, sizeof(payload), MSG_OOB, NULL, 0) / recvfrom(recv_sk, (void *)payload, sizeof(payload), 0, NULL, 0) = fails with errno = 0, and tcpdump shows me the packet with the URG flag set. sendto(send_sk, (void *)payload, sizeof(payload), MSG_OOB, NULL, 0) / recvfrom(recv_sk, (void *)payload, sizeof(payload), MSG_OOB, NULL, 0) = fails with EINVAL on the receiving end, and tcpdump shows me the packet with the URG flag set. Did I miss something on the man pages ? or is it something more sinister ? The behavior of MSG_OOB is somewhat subtle; I would strongly recommend UNIX Network Programming, Vol 1, by W. Richard Stevens, which has a good chapter on this. This is something missing from our manpages currently, including an extra meaning for EINVAL return from recv*. In this case, the key item is that TCP MSG_OOB is really an 'urgent' marker which points to a position in the stream. By default, the receiver will save the indicated byte (just one!) in a separate buffer for fetching with MSG_OOB, but only after the non-urgent data before it has been received. If do a MSG_OOB send of multiple bytes, it's really treated as a normal send of all but the final byte, followed by MSG_OOB send of that final byte; recv(MSG_OOB) will fail with error EINVAL until you first read the earlier, non-urgent data. After that, you can use ioctl(SIOCATMARK) to determine whether there's a byte of urgent data to read with recv(MSG_OOB) or just more normal data. An example of how to use SIOCATMARK, recv(MSG_OOB), and POLLRDBAND to detect when the sending side has sent new urgent data can be found in usr.bin/telnet/sys_bsd.c, though it has some historical baggage to handle ancient kernels that you shouldn't copy. Really, the book is the place to go at this point... (sigh, two more items for the todo list: manpage additions and telnet cruft removal) Philip
Re: ACPI0 Interrupts and System Time
Mike, Looks like the July 5th snapshot is working great. Thanks for the help. On Wed, Jul 16, 2014 at 11:54 AM, Mike Larkin mlar...@azathoth.net wrote: On Wed, Jul 16, 2014 at 09:51:12AM -0700, Mike Larkin wrote: On Wed, Jul 16, 2014 at 11:36:21AM -0500, Josh Hoppes wrote: Would there happen to be any pre-built snapshots that are known good? This is a short term event and I don't a lot of time to work since doors open tomorrow morning. Was the fix kernel only and would that work with my existing userland or has there been a significant enough change that I would need to do a full upgrade? Thanks for the help so far! The change was just in the kernel, but unless you wanted to go and pull out that one patch and apply it to an older tree, you might be better off installing a complete snap. I've been told there are older snaps kept here: http://ftp.hostserver.de/archive I'd grab one from between 26 Jun and 6 July. Much later than 6 July and you run the risk of running into the hackathon commits, which sometimes destabilize the tree for a short time. The pair of commits I think you may need were made on 23 Jul and 25 Jul (the 23 Jul diff being the more relevant one for your issue). Should have been 23 Jun and 25 Jun there ... -ml On Wed, Jul 16, 2014 at 11:04 AM, Mike Larkin mlar...@azathoth.net wrote: On Wed, Jul 16, 2014 at 08:55:15AM -0500, Josh Hoppes wrote: Hello, I've got a few machines I'm setting up which I noticed ACPI0 is generating a lot of constant interrupts which appears to be consuming system time on CPU0 up to 80%. I think other interrupts are still getting time to process, but I'm not sure if it could still cause a performance impact as I'm looking to use these systems to handle filtering and queuing on the edge of our network. Any ideas or suggestions would be appreciated. The systems are Dell R620, dmesg below. We saw (and kettenis@ fixed) a similar issue on this machine in late June. Can you please try a snap from a later date? I'd say at least July 1 or later. -ml OpenBSD 5.5-stable (GENERIC.MP) #3: Sun May 11 18:30:30 CDT 2014 r...@build.kncm.net:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 34295709696 (32706MB) avail mem = 33374154752 (31828MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xcf42c000 (99 entries) bios0: vendor Dell Inc. version 2.2.2 date 01/16/2014 bios0: Dell Inc. PowerEdge R620 acpi0 at bios0: rev 2 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP APIC SPCR HPET DMAR MCFG WD__ SLIC ERST HEST BERT EINJ TCPA PC__ SRAT SSDT acpi0: wakeup devices PCI0(S5) PCI1(S5) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 4 (boot processor) cpu0: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.45 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 2, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 100MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1.0, IBE cpu1 at mainbus0: apid 6 (application processor) cpu1: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 3, package 0 cpu2 at mainbus0: apid 8 (application processor) cpu2: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 4, package 0 cpu3 at mainbus0: apid 16 (application processor) cpu3: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 8, package 0 cpu4 at
OpenBSD 5.5 on Nokia IP260
I know it's ancient and minimal hardware, but I've been tinkering with OpenBSD 5.5 on a Nokia IP260 with an 8GB compact flash. The OS was installed on the compact flash using a card reader on a Dell laptop. The OS boots and networking works as long as I specify the MAC using lladdr in hostname.xxx and use duids. If you don't use duids the partitions will not mount when the compact flash is moved from the laptop to the IP260. But I see some errors on an 8GB compact flash that I didn't see with a 1GB compact flash. Could it be the 8GB compact flash is more than what the IP260 supported? Here's the dmesg OpenBSD 5.5-current (GENERIC) #104: Sun May 11 07:51:32 MDT 2014 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Celeron(TM) CPU 400MHz (GenuineIntel 686-class) 401 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PSE36,MMX,FXSR,SSE,PERF real mem = 536379392 (511MB) avail mem = 515194880 (491MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: PC BIOS, date // pcibios at bios0 function 0x1a not configured bios0: ROM list: 0xe/0x1! cpu0 at mainbus0: (uniprocessor) mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82815 Host rev 0x04 intelagp0 at pchb0 agp0 at intelagp0: aperture at 0xf800, size 0x240 ppb0 at pci0 dev 1 function 0 Intel 82815 AGP rev 0x04 pci1 at ppb0 bus 1 ppb1 at pci0 dev 30 function 0 Intel 82801BA Hub-to-PCI rev 0x05 pci2 at ppb1 bus 2 ubsec0 at pci2 dev 0 function 0 Broadcom 5823 rev 0x01: 3DES MD5 SHA1 AES RNG PK, irq 10 cbb0 at pci2 dev 1 function 0 TI PCI1520 CardBus rev 0x01: irq 11, CardBus support disabled cbb1 at pci2 dev 1 function 1 TI PCI1520 CardBus rev 0x01: irq 11, CardBus support disabled fxp0 at pci2 dev 2 function 0 Intel 82559ER rev 0x10, i82551: irq 5, address 00:00:00:00:00:00 inphy0 at fxp0 phy 1: i82555 10/100 PHY, rev. 4 fxp1 at pci2 dev 3 function 0 Intel 82559ER rev 0x10, i82551: irq 6, address 00:00:00:00:00:00 inphy1 at fxp1 phy 1: i82555 10/100 PHY, rev. 4 fxp2 at pci2 dev 4 function 0 Intel 82559ER rev 0x10, i82551: irq 7, address 00:00:00:00:00:00 inphy2 at fxp2 phy 1: i82555 10/100 PHY, rev. 4 fxp3 at pci2 dev 5 function 0 Intel 82559ER rev 0x10, i82551: irq 9, address 00:00:00:00:00:00 inphy3 at fxp3 phy 1: i82555 10/100 PHY, rev. 4 cbb0: bad Vcc request. sock_ctrl 0x400, sock_status 0x3206 cardslot0 at cbb0 slot 0 flags 0 pcmcia0 at cardslot0 cardslot1 at cbb1 slot 1 flags 0 pcmcia1 at cardslot1 ichpcib0 at pci0 dev 31 function 0 Intel 82801BA LPC rev 0x05: PM disabled pciide0 at pci0 dev 31 function 1 Intel 82801BA IDE rev 0x05: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility wd0 at pciide0 channel 0 drive 0: SanDisk SDCFHNJC-008G wd0: 1-sector PIO, LBA48, 7629MB, 15625216 sectors wd1 at pciide0 channel 0 drive 1: FUJITSU MHV2040AS wd1: 16-sector PIO, LBA, 38154MB, 78140160 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 2 pciide0: channel 1 disabled (no drives) ichiic0 at pci0 dev 31 function 3 Intel 82801BA SMBus rev 0x05: irq 9 iic0 at ichiic0 spdmem0 at iic0 addr 0x50: 256MB SDRAM non-parity PC133CL2 spdmem1 at iic0 addr 0x51: 256MB SDRAM non-parity PC133CL2 isa0 at ichpcib0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo com0: console com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard pcppi0 at isa0 port 0x61 spkr0 at pcppi0 lpt0 at isa0 port 0x378/4: polled nsclpcsio0 at isa0 port 0x2e/2: NSC PC87366 rev 9: GPIO VLM TMS gpio0 at nsclpcsio0: 29 pins npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 nvram: invalid checksum vscsi0 at root scsibus1 at vscsi0: 256 targets softraid0 at root scsibus2 at softraid0: 256 targets wd0(pciide0:0:0): timeout type: ata c_bcount: 512 c_skip: 0 pciide0:0:0: bus-master DMA error: missing interrupt, status=0x61 wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying wd0(pciide0:0:0): timeout type: ata c_bcount: 512 c_skip: 0 pciide0:0:0: bus-master DMA error: missing interrupt, status=0x61 wd0: transfer error, downgrading to Ultra-DMA mode 1 wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 1 wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 2 wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying wd0(pciide0:0:0): timeout type: ata c_bcount: 512 c_skip: 0 pciide0:0:0: bus-master DMA error: missing interrupt, status=0x61 wd0: transfer error, downgrading to Ultra-DMA mode 0 wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 0 wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 2 wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn
Re: OpenBSD 5.5 on Nokia IP260
On Wed, Jul 16, 2014 at 20:26, Stan Gammons wrote: I know it's ancient and minimal hardware, but I've been tinkering with OpenBSD 5.5 on a Nokia IP260 with an 8GB compact flash. The OS was installed on the compact flash using a card reader on a Dell laptop. The OS boots and networking works as long as I specify the MAC using lladdr in hostname.xxx and use duids. If you don't use duids the partitions will not mount when the compact flash is moved from the laptop to the IP260. But I see some errors on an 8GB compact flash that I didn't see with a 1GB compact flash. Could it be the 8GB compact flash is more than what the IP260 supported? Here's the dmesg Could be. wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying wd0: soft error (corrected) wd0(pciide0:0:0): timeout type: ata c_bcount: 512 c_skip: 0 pciide0:0:0: bus-master DMA error: missing interrupt, status=0x61 wd0: transfer error, downgrading to PIO mode 4 wd0(pciide0:0:0): using PIO mode 4 wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 2 wd0c: device timeout reading fsbn 65 (wd0 bn 65; cn 0 tn 1 sn 2), retrying wd0: soft error (corrected) root on wd0a (511531c0c5c7c075.a) swap on wd0b dump on wd0b clock: unknown CMOS layout This looks more like pciide controller issues. Either it or the CF aren't playing nice with each other. But once downgraded to PIO mode, it appears everything has been slowed down enough to work again.
Sysmerge problem with xetc56.tgz on July 16 amd64 snapshot
# sysmerge -x xetc56.tgz === Fetching file:///root/xetc56.tgz === Fetching file:///root/SHA256.sig === Verifying xetc56.tgz against /etc/signify/openbsd-56-base.pub === Populating temporary root under /var/tmp/sysmerge.CJzwPVyHXg/temproot tar: WARNING! These patterns were not matched: ./usr/share/sysmerge/xetcsum ERROR: xetc56.tgz: badly formed xetc set, lacks ./usr/share/sysmerge/xetcsum Indeed, there's no /usr at all in the tarball. Clue-stick welcome if I missed some key warning... Thanks, Kent.
Re: OpenBSD 5.5 on Nokia IP260
On 07/16/14 21:26, Stan Gammons wrote: I know it's ancient and minimal hardware, but I've been tinkering with OpenBSD 5.5 on a Nokia IP260 with an 8GB compact flash. The OS was installed on the compact flash using a card reader on a Dell laptop. The OS boots and networking works as long as I specify the MAC using lladdr in hostname.xxx and use duids. If you don't use duids the partitions will not mount when the compact flash is moved from the laptop to the IP260. As expected. on your Dell, it's probably in a USB adapter, and comes up as an sd(4) device; on the IDE bus, it comes up as a wd(4) device. But I see some errors on an 8GB compact flash that I didn't see with a 1GB compact flash. Could it be the 8GB compact flash is more than what the IP260 supported? Here's the dmesg OpenBSD 5.5-current (GENERIC) #104: Sun May 11 07:51:32 MDT 2014 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC ...[snipped, but thanks for providing!]... scsibus2 at softraid0: 256 targets wd0(pciide0:0:0): timeout type: ata c_bcount: 512 c_skip: 0 pciide0:0:0: bus-master DMA error: missing interrupt, status=0x61 wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying ...[and slow, painful downgrade to PIO]... This might help: http://www.openbsd.org/faq/faq12.html#i386flash This will probably really hurt the performance on your hard disk as well, so it may not be worth doing; as it is, your system finds what each can do just fine on its own. But being this is a firewall, reboot time might mean more than disk througput... Nick.
Re: OpenBSD 5.5 on Nokia IP260
On 07/16/14 20:38, Ted Unangst wrote: On Wed, Jul 16, 2014 at 20:26, Stan Gammons wrote: I know it's ancient and minimal hardware, but I've been tinkering with OpenBSD 5.5 on a Nokia IP260 with an 8GB compact flash. The OS was installed on the compact flash using a card reader on a Dell laptop. The OS boots and networking works as long as I specify the MAC using lladdr in hostname.xxx and use duids. If you don't use duids the partitions will not mount when the compact flash is moved from the laptop to the IP260. But I see some errors on an 8GB compact flash that I didn't see with a 1GB compact flash. Could it be the 8GB compact flash is more than what the IP260 supported? Here's the dmesg Could be. I'm wondering if 4GB was the maximum supported since that's what I've seen for the CF for other Nokia IP models made around the same time as the IP260. The technical specs I've seen for the IP260 show 40GB as the maximum hard disk, but it didn't specify a maximum for the CF. 1GB and 8GB are all I have at the moment though. Will have to see if I can find one. wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying wd0: soft error (corrected) wd0(pciide0:0:0): timeout type: ata c_bcount: 512 c_skip: 0 pciide0:0:0: bus-master DMA error: missing interrupt, status=0x61 wd0: transfer error, downgrading to PIO mode 4 wd0(pciide0:0:0): using PIO mode 4 wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 2 wd0c: device timeout reading fsbn 65 (wd0 bn 65; cn 0 tn 1 sn 2), retrying wd0: soft error (corrected) root on wd0a (511531c0c5c7c075.a) swap on wd0b dump on wd0b clock: unknown CMOS layout This looks more like pciide controller issues. Either it or the CF aren't playing nice with each other. But once downgraded to PIO mode, it appears everything has been slowed down enough to work again. The controller probably doesn't like the CF. Is there a way to debug this further to see if that's the case? Stan
INSTALL.macppc link moved
Apple is annoying and likes to shuffle their documentation around every few years. Maybe it's worth linking to archive.org instead. Index: distrib/notes/macppc/prep === RCS file: /cvs/src/distrib/notes/macppc/prep,v retrieving revision 1.22 diff -u -p -r1.22 prep --- distrib/notes/macppc/prep 27 Nov 2013 13:12:48 - 1.22 +++ distrib/notes/macppc/prep 17 Jul 2014 02:04:51 - @@ -31,7 +31,7 @@ up in sequence (similar to KITT from Kni press the System Identifier button until the seventh LED from the right is highlighted on the lower bank. Now hold the System Identifier button for two seconds. For more details, read: -http://docs.info.apple.com/article.html?artnum=75489 +http://support.apple.com/kb/TA26930 dnl XXX Move the boot commands to install in sections (booting from network, dnl XXX booting from cd-rom, etc)
Re: OpenBSD 5.5 on Nokia IP260
On 07/16/14 20:53, Nick Holland wrote: On 07/16/14 21:26, Stan Gammons wrote: I know it's ancient and minimal hardware, but I've been tinkering with OpenBSD 5.5 on a Nokia IP260 with an 8GB compact flash. The OS was installed on the compact flash using a card reader on a Dell laptop. The OS boots and networking works as long as I specify the MAC using lladdr in hostname.xxx and use duids. If you don't use duids the partitions will not mount when the compact flash is moved from the laptop to the IP260. As expected. on your Dell, it's probably in a USB adapter, and comes up as an sd(4) device; on the IDE bus, it comes up as a wd(4) device. Exactly. But I see some errors on an 8GB compact flash that I didn't see with a 1GB compact flash. Could it be the 8GB compact flash is more than what the IP260 supported? Here's the dmesg OpenBSD 5.5-current (GENERIC) #104: Sun May 11 07:51:32 MDT 2014 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC ...[snipped, but thanks for providing!]... scsibus2 at softraid0: 256 targets wd0(pciide0:0:0): timeout type: ata c_bcount: 512 c_skip: 0 pciide0:0:0: bus-master DMA error: missing interrupt, status=0x61 wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying ...[and slow, painful downgrade to PIO]... This might help: http://www.openbsd.org/faq/faq12.html#i386flash This will probably really hurt the performance on your hard disk as well, so it may not be worth doing; as it is, your system finds what each can do just fine on its own. But being this is a firewall, reboot time might mean more than disk througput... Nick. That fixed it. It boots without the errors now. Thanks! Stan
Re: Current snapshot (7/14) has mismatched libc
Theo just announced that 5.6 beta testing is begun: http://marc.info/?l=openbsd-cvsm=140546158205874w=2 So, I downloaded today's snapshot and installed it. But when I try to install any package from the snapshot packages, I get the same mismatched libc errors... Here for example are the errors for installing rsync using PKG_PATH='http://ftp3.usa.openbsd.org/pub/OpenBSD/snapshots/packages/amd64' #pkg_add rsync Ambiguous: choose package for rsync a 0: None 1: rsync-3.1.1 2: rsync-3.1.1-iconv Your choice: quirks-1.147 signed on 2014-07-08T12:48:35Z Can't install rsync-3.1.1 because of libraries |library c.76.0 not found | /usr/lib/libc.so.77.0 (system): bad major Richard Narron - Q: How many Martians does it take to screw in a lightbulb? A: One and a half.
Re: OpenBSD 5.5 on Nokia IP260
I failed to include the new dmesg in the last email User Kernel Config UKC chang wd 53 wd* at wdc0|wdc1|wdc*|wdc*|pciide*|pciide* channel -1 flags 0x0 change (y/n) ? y channel [-1] ? flags [0] ? 0x0ff0 53 wd* changed 53 wd* at wdc0|wdc1|wdc*|wdc*|pciide*|pciide* channel -1 flags 0xff0 UKC quit Continuing... mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: PC BIOS, date // pcibios at bios0 function 0x1a not configured bios0: ROM list: 0xe/0x1! cpu0 at mainbus0: (uniprocessor) mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82815 Host rev 0x04 intelagp0 at pchb0 agp0 at intelagp0: aperture at 0xf800, size 0x240 ppb0 at pci0 dev 1 function 0 Intel 82815 AGP rev 0x04 pci1 at ppb0 bus 1 ppb1 at pci0 dev 30 function 0 Intel 82801BA Hub-to-PCI rev 0x05 pci2 at ppb1 bus 2 ubsec0 at pci2 dev 0 function 0 Broadcom 5823 rev 0x01: 3DES MD5 SHA1 AES RNG PK, irq 10 cbb0 at pci2 dev 1 function 0 TI PCI1520 CardBus rev 0x01: irq 11, CardBus support disabled cbb1 at pci2 dev 1 function 1 TI PCI1520 CardBus rev 0x01: irq 11, CardBus support disabled fxp0 at pci2 dev 2 function 0 Intel 82559ER rev 0x10, i82551: irq 5, address 00:00:00:00:00:00 inphy0 at fxp0 phy 1: i82555 10/100 PHY, rev. 4 fxp1 at pci2 dev 3 function 0 Intel 82559ER rev 0x10, i82551: irq 6, address 00:00:00:00:00:00 inphy1 at fxp1 phy 1: i82555 10/100 PHY, rev. 4 fxp2 at pci2 dev 4 function 0 Intel 82559ER rev 0x10, i82551: irq 7, address 00:00:00:00:00:00 inphy2 at fxp2 phy 1: i82555 10/100 PHY, rev. 4 fxp3 at pci2 dev 5 function 0 Intel 82559ER rev 0x10, i82551: irq 9, address 00:00:00:00:00:00 inphy3 at fxp3 phy 1: i82555 10/100 PHY, rev. 4 cbb0: bad Vcc request. sock_ctrl 0x400, sock_status 0x3206 cardslot0 at cbb0 slot 0 flags 0 pcmcia0 at cardslot0 cardslot1 at cbb1 slot 1 flags 0 pcmcia1 at cardslot1 ichpcib0 at pci0 dev 31 function 0 Intel 82801BA LPC rev 0x05: PM disabled pciide0 at pci0 dev 31 function 1 Intel 82801BA IDE rev 0x05: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility wd0 at pciide0 channel 0 drive 0: SanDisk SDCFHNJC-008G wd0: 1-sector PIO, LBA48, 7629MB, 15625216 sectors wd1 at pciide0 channel 0 drive 1: FUJITSU MHV2040AS wd1: 16-sector PIO, LBA, 38154MB, 78140160 sectors wd0(pciide0:0:0): using PIO mode 4 wd1(pciide0:0:1): using PIO mode 4 pciide0: channel 1 disabled (no drives) ichiic0 at pci0 dev 31 function 3 Intel 82801BA SMBus rev 0x05: irq 9 iic0 at ichiic0 spdmem0 at iic0 addr 0x50: 256MB SDRAM non-parity PC133CL2 spdmem1 at iic0 addr 0x51: 256MB SDRAM non-parity PC133CL2 isa0 at ichpcib0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo com0: console com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard pcppi0 at isa0 port 0x61 spkr0 at pcppi0 lpt0 at isa0 port 0x378/4: polled nsclpcsio0 at isa0 port 0x2e/2: NSC PC87366 rev 9: GPIO VLM TMS gpio0 at nsclpcsio0: 29 pins npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 nvram: invalid checksum vscsi0 at root scsibus1 at vscsi0: 256 targets softraid0 at root scsibus2 at softraid0: 256 targets root on wd0a (511531c0c5c7c075.a) swap on wd0b dump on wd0b clock: unknown CMOS layout Thanks again for the help. Stan
Re: Current snapshot (7/14) has mismatched libc
Theo just announced that 5.6 beta testing is begun: http://marc.info/?l=openbsd-cvsm=140546158205874w=2 That is not an announcement. It is one of a series of steps to renumbering the release, and it means there will be breakage. But when I try to install any package from the snapshot packages, I get the same mismatched libc errors... Here for example are the errors for installing rsync using PKG_PATH='http://ftp3.usa.openbsd.org/pub/OpenBSD/snapshots/packages/amd64' #pkg_add rsync Ambiguous: choose package for rsync a 0: None 1: rsync-3.1.1 2: rsync-3.1.1-iconv Your choice: quirks-1.147 signed on 2014-07-08T12:48:35Z Can't install rsync-3.1.1 because of libraries |library c.76.0 not found | /usr/lib/libc.so.77.0 (system): bad major Yup.
