Re: Load average changed in 6.1?
On Mon, Apr 24, 2017 at 11:09:37 +0200, Andreas Kusalananda Kähäri wrote: > On Mon, Apr 24, 2017 at 10:42:16AM +0200, Christoph Borsbach wrote: > > Hello everyone, > > first off: I know that the topic of "load" has been discussed numerous > > times, and been a topic on undeadly [1]. I know that this number is not that > > important. > > > > However: > > After upgrading 3 of my systems to 6.1 (from 6.0) I noticed the load average > > (15min value) has gone up by roughly 1.0, both in the output of daily(8) > > over some days now and when checking manually with w, top, or uptime. > > Yes. If I understand correctly, this is because the kernel threads are > now counted towards the load average. An OpenBSD system at rest should > now have a load average of about 1. Thanks, that makes sense and explains it! Christoph > > Regards, > Kusalananda
Load average changed in 6.1?
Hello everyone, first off: I know that the topic of "load" has been discussed numerous times, and been a topic on undeadly [1]. I know that this number is not that important. However: After upgrading 3 of my systems to 6.1 (from 6.0) I noticed the load average (15min value) has gone up by roughly 1.0, both in the output of daily(8) over some days now and when checking manually with w, top, or uptime. The systems in question differ a bit: - amd64 MP (KVM-Guest, dmesg [2], load-example [3]) - amd64 SP (VMware Guest, dmesg and examples not handy right now) - i386 SP (Alix, dmesg [4], load examples [5]) All were upgraded last week with bsd.rd to 6.1-RELEASE. The systems perform as well as ever and nothing was changed aside from upgrading system and packages. I'm just interested what could change the behavior. A quick check of src/sys/uvm/uvm_meter.c does not show me any changes recently. Has anybody observed this as well and has an explanation for this? Thanks, Christoph [1] http://undeadly.org/cgi?action=article&sid=20090715034920&mode=flat [2] OpenBSD 6.1 (GENERIC.MP) #20: Sat Apr 1 13:45:56 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 6425526272 (6127MB) avail mem = 6226112512 (5937MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf69e0 (11 entries) bios0: vendor SeaBIOS version "1.9.3-20161116_142049-atsina" date 04/01/2014 bios0: QEMU Standard PC (i440FX + PIIX, 1996) acpi0 at bios0: rev 0 acpi0: sleep states S3 S4 S5 acpi0: tables DSDT FACP APIC HPET acpi0: wakeup devices acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Westmere E56xx/L56xx/X56xx (Nehalem-C), 2494.15 MHz cpu0: FPU,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,PCLMUL,SSSE3,CX16,SSE4.1,SSE4.2,x2APIC,POPCNT,AES,HV,NXE,LONG,LAHF cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu0: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped cpu0: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 1000MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Westmere E56xx/L56xx/X56xx (Nehalem-C), 2493.77 MHz cpu1: FPU,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,PCLMUL,SSSE3,CX16,SSE4.1,SSE4.2,x2APIC,POPCNT,AES,HV,NXE,LONG,LAHF cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu1: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped cpu1: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped cpu1: smt 0, core 0, package 1 ioapic0 at mainbus0: apid 0 pa 0xfec0, version 11, 24 pins acpihpet0 at acpi0: 1 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpicpu0 at acpi0: C1(@1 halt!) acpicpu1 at acpi0: C1(@1 halt!) "ACPI0006" at acpi0 not configured "PNP0303" at acpi0 not configured "PNP0F13" at acpi0 not configured "PNP0700" at acpi0 not configured "PNP0501" at acpi0 not configured "PNP0A06" at acpi0 not configured "PNP0A06" at acpi0 not configured "PNP0A06" at acpi0 not configured "QEMU0002" at acpi0 not configured pvbus0 at mainbus0: KVM pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02 pcib0 at pci0 dev 1 function 0 "Intel 82371SB ISA" rev 0x00 pciide0 at pci0 dev 1 function 1 "Intel 82371SB IDE" rev 0x00: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility pciide0: channel 0 disabled (no drives) atapiscsi0 at pciide0 channel 1 drive 0 scsibus1 at atapiscsi0: 2 targets cd0 at scsibus1 targ 0 lun 0: ATAPI 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, DMA mode 2 uhci0 at pci0 dev 1 function 2 "Intel 82371SB USB" rev 0x01: apic 0 int 11 piixpm0 at pci0 dev 1 function 3 "Intel 82371AB Power" rev 0x03: apic 0 int 9iic0 at piixpm0 vga1 at pci0 dev 2 function 0 "Cirrus Logic CL-GD5446" rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) em0 at pci0 dev 3 function 0 "Intel 82540EM" rev 0x03: apic 0 int 11, address XX:XX:XX:XX:XX:XX virtio0 at pci0 dev 4 function 0 "Qumranet Virtio Storage" rev 0x00 vioblk0 at virtio0 scsibus2 at vioblk0: 2 targets sd0 at scsibus2 targ 0 lun 0: SCSI3 0/direct fixed sd0: 119808MB, 512 bytes/sector, 245366784 sectors virtio0: msix shared virtio1 at pci0 dev 5 function 0 "Qumranet Virtio Memory" rev 0x00 viomb0 at virtio1 virtio1: apic 0 int 10 isa0 at pcib0 isadma0 at isa0 fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 fd0 at fdc0 drive 1: density unknown com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pckbc0 at isa0 port 0x60/5 irq 1 irq 12 pckbd0 at pckbc0 (kbd slot) wskbd0 at pckbd0: console keyboard, using wsdis
Re: Symon on 5.6
On Thu, Jan 15, 2015 at 10:56:35 +0200, karlis.mikels...@lf.lv wrote:
> Hello,
>
> >for me, it didn't work as well. I (think I) did everything needed,
> >including
> >rrdtool-chroot enable, and I had the same effect as you - no graphs. Only
> >after copying /bin/sh the graphs started working. I didn't do much
> >investigation though.
> >Oh and: I'm running nginx, if that matters.
> Can you please share your nginx.conf? I couldn't get Syweb to work with
> Nginx no matter what I've tried.
I don't think it's the nginx.conf, the only thing I did was uncomment this
section...:
--8<---
# pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
#
location ~ \.php$ {
root /var/www/htdocs;
fastcgi_pass 127.0.0.1:9000;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME \
$document_root$fastcgi_script_name;
includefastcgi_params;
}
->8-
...after installing PHP.
Good luck,
Christoph
Re: Symon on 5.6
On Wed, Jan 14, 2015 at 21:24:15 -0500, Steve Shockley wrote: > On 1/14/2015 9:47 AM, Predrag Punosevac wrote: > >>and I ran > >>the chroot enable script from rrdtool. > > >As documented in the rrdtool pkg-readme, you must do: > >/usr/local/share/examples/rrdtool/rrdtool-chroot enable > > > >You should look under /usr/local/share/doc/pkg-readmes/, it comes with a > >*lot* of OpenBSD specific information.. > > Thanks. I did run rrd-chroot enable, and changed rrdtool_path in setup.inc > to /usr/local/bin/rrdtool (which is where rrdtool-chroot copies it in the > chroot). Even with that, nothing worked until I coincidentally copied > /bin/sh to the chroot. > > Maybe $this->exec($cmdline) in php (class_rrdtool.inc line 103) requires sh? > But that wouldn't explain if it works for everyone else. Hi, for me, it didn't work as well. I (think I) did everything needed, including rrdtool-chroot enable, and I had the same effect as you - no graphs. Only after copying /bin/sh the graphs started working. I didn't do much investigation though. Oh and: I'm running nginx, if that matters. Thanks and regards, Christoph
Re: debugging vio issue?
On Fri, Jun 06, 2014 at 11:23:12 -0300, Giancarlo Razzolini wrote: > Em 06-06-2014 09:31, Christoph Borsbach escreveu: > > Hello everyone, > > I just wanted to report that I too had this problem (sporadic hangs of the > > vio0-Interface) with 5.5-stable/amd64 in a KVM-VM. I tried the solution > > described by Philip Guenther and voilá, the problems are gone. I did no > > tests > > with regard to the performance, it seems alright. > > > > $ dmesg |grep vio > > vio0 at virtio0: RingEventIdx disabled by UKC: address > What is your underlying network in QEMU/KVM. I never had issues with vio > and I'm running 5.5 stable/amd64. I use it with macvtap on the host. And > some of them are isolated networks, where there is no hardware > interaction, it's all software based. I guess I'm lucky. Hi, sorry, I don't know that, it's a VM at a hoster. I have no acces to the underlying host. Regards, Christoph
Re: debugging vio issue?
On Wed, May 28, 2014 at 11:37:54 -0700, Philip Guenther wrote: > On Wed, May 28, 2014 at 11:26 AM, Adam Thompson wrote: > > > Don't have a good answer for you, but I have similar problems with vio(4). > > Switching to e1000 on the KVM side solved my random hangs completely. > > > > The vio(4) manpage mentions > Setting flags to 0x02 disables the RingEventIndex feature. This can be > tried as a workaround for possible bugs in host implementations or vio > at > the cost of slightly reduced performance. > > Have any of you tested that to see whether it improves the situation? Hello everyone, I just wanted to report that I too had this problem (sporadic hangs of the vio0-Interface) with 5.5-stable/amd64 in a KVM-VM. I tried the solution described by Philip Guenther and voilá, the problems are gone. I did no tests with regard to the performance, it seems alright. $ dmesg |grep vio vio0 at virtio0: RingEventIdx disabled by UKC: address Thanks and have a nice day, Christoph
Re: Multi-tabbed Terminal
Hi, On Fri, Aug 04, 2006 at 10:02:50 -0700, Clint Pachl wrote: > Can anyone recommend a light-weight multi-tabbed terminal for OBSD 3.9? > I looked through the i386 packages, but didn't notice any. I'm using FVWM2. You might want to check out "Terminal", http://www.os-cillation.de/index.php?id=42&L=5 . Don't know if its "lightweight" enough for you, as it comes with a few dependencies you wouldn't need as a fvwm2 user. Chris
