Re: time issues and ZFS

Daniel, Have you run tests with the machdep.idle value changed, and fiddling kern.eventtimer.periodic / kern.eventtimer.idletick ? adrian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To

Re: time issues and ZFS

Daniel, Have you run tests with the machdep.idle value changed, and fiddling kern.eventtimer.periodic / kern.eventtimer.idletick ? Adrian, not yet, for several reasons: 1- as I explained, I can't realy force the problem, it happens when we run some zfs scripts, like mirror, but have to wait

Re: Re: kvm vlan virtio problem

Hi! The same warning shows up in our setup: Jan 21 23:40:46 host kernel: WARNING: at net/core/dev.c:1712 skb_gso_segment+0x1df/0x2b0() (Tainted: GW --- ) Jan 21 23:40:46 host kernel: Hardware name: System Product Name Jan 21 23:40:46 host kernel: tun: caps=(0x1b0049, 0x0)

FreeBSD 9.1 - openldap slapd lockups, mutex problems

Hi. (Im am sending this to the stable list, because it maybe kernel related.. ) On 9.1-RELEASE I am witnessing lockups of the openldap slapd daemon. The slapd runs for some days and then hangs, consuming high amounts of CPU. In this state slapd can only be restarted by SIGKILL. # procstat -kk

Best priced Apartments

!--!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN http://www.w3.org/TR/html4/loose.dtd Best Priced Apartments FROM ONLY R639 000 One of South Africa's Premier Lifestyle Estates Lamandine, Burgundy Estate 9 hole Golf Course, School, Shopping Centre, Security, Sport Fields, Tennis

Re: time issues and ZFS

Thus spake Daniel Braniss da...@cs.huji.ac.il: In the meantime here is some info: Intel(R) Xeon(R) CPU E5645: running with no problems LAPIC(600) HPET(450) HPET1(440) HPET2(440) HPET3(440) i8254(100) RTC(0) Intel(R) Xeon(R) CPU X5550: this is the problematic, at least for the moment

Re: time issues and ZFS

On Tue, Jan 22, 2013 at 7:27 AM, Julian Stecklina jstec...@os.inf.tu-dresden.de wrote: Does anyone know why the LAPIC is given a lower priority than HPET in this case? If you have an LAPIC, it should always be prefered to HPET, unless something is seriously wrong with it... On many

busy on all disks that are a part of the ZFS pools without any load

Hello. I have a problem with all diks that are a part of ZFS pools. There is a busy state (6-7%) on all of them in the iostat. But only there! There aren't any load at all on the disks and other system utilities, such as gstat, 'zpool iostat', 'systat -iostat' which are reporting a zero busy

Re: busy on all disks that are a part of the ZFS pools without any load

on 22/01/2013 16:01 Oleksii Tsvietnov said the following: # iostat -xzt da,scsi extended device statistics device r/s w/skr/skw/s qlen svc_t %b da0 12.6 2.5 1248.5 173.20 29.0 7 da1 12.6 2.6 1227.7 173.20 22.6 6 da2

Re: time issues and ZFS

On 01/22/13 07:27, Julian Stecklina wrote: Thus spake Daniel Braniss da...@cs.huji.ac.il: In the meantime here is some info: Intel(R) Xeon(R) CPU E5645: running with no problems LAPIC(600) HPET(450) HPET1(440) HPET2(440) HPET3(440) i8254(100) RTC(0) Intel(R) Xeon(R) CPU X5550: this is the

Re: busy on all disks that are a part of the ZFS pools without any load

These are values since boot, they do not reflect current system load. As I could see these values usually change from 0 to 60 . Why did they freeze on 7%? ___ freebsd-stable@freebsd.org mailing list

Re: busy on all disks that are a part of the ZFS pools without any load

on 22/01/2013 16:47 Oleksii Tsvietnov said the following: These are values since boot, they do not reflect current system load. As I could see these values usually change from 0 to 60 . Why did they freeze on 7%? That's the average value since boot to now? -- Andriy Gapon

Re: busy on all disks that are a part of the ZFS pools without any load

On 01/22/2013 04:51 PM, Andriy Gapon wrote: That's the average value since boot to now? Maybe... Does iostat's busy always show avarage value since boot? ___ freebsd-stable@freebsd.org mailing list

Re: busy on all disks that are a part of the ZFS pools without any load

on 22/01/2013 17:05 Oleksii Tsvietnov said the following: On 01/22/2013 04:51 PM, Andriy Gapon wrote: That's the average value since boot to now? Maybe... Does iostat's busy always show avarage value since boot? Use -w option to see current state (starting from the second screen). Manual

Re: FreeBSD 9.1 - openldap slapd lockups, mutex problems

On 01/22/13 05:19, Kai Gallasch wrote: Hi. (Im am sending this to the stable list, because it maybe kernel related.. ) On 9.1-RELEASE I am witnessing lockups of the openldap slapd daemon. The slapd runs for some days and then hangs, consuming high amounts of CPU. In this state slapd can only

Re: Failsafe on kernel panic

I started investigating ipmi, so far i can configure IP from fbsd to ipmi. My question is how to access it? Can it be done inband attached to one oc the Ibm nics kn the board? or knlh out oc band? In case of oob any knows if the iLO plug is pure rj45 in ibm servers (specially x3250/3550)? Thanks

Re: time issues and ZFS

Hi! As I said before, the problem with non-HLT loops with event-timer in -9 and -head is that it calls the idle function inside a critical section (critical_enter and critical_exit) which blocks interrupts from occuring. The EI;HLT instruction pair on i386/amd64 atomically and correctly handles

Re: kvm vlan virtio problem

Hi, - Original Message - Hi! The same warning shows up in our setup: Jan 21 23:40:46 host kernel: WARNING: at net/core/dev.c:1712 skb_gso_segment+0x1df/0x2b0() (Tainted: GW --- ) Jan 21 23:40:46 host kernel: Hardware name: System Product Name Jan 21

Re: kvm vlan virtio problem

Hi, - Original Message - Hi! The same warning shows up in our setup: Jan 21 23:40:46 host kernel: WARNING: at net/core/dev.c:1712 skb_gso_segment+0x1df/0x2b0() (Tainted: GW --- ) Jan 21 23:40:46 host kernel: Hardware name: System Product Name Jan 21