invalid statistics for 80211node malloc type

Hi, After upgrading from 8-stable to 9-stable I noticed the error in malloc(9) type 80211node counter. From vmstat -m: Type InUse MemUse HighUse Requests Size(s) 80211node 18446744073709551605 18014398509481852K -0 18446744073709551605/18014398509481852 1024.0 184

Re: invalid statistics for 80211node malloc type

... ? Never noticed this before. Is something double-freeing? Adrian On 25 March 2013 00:44, Sergey Kandaurov wrote: > Hi, > > After upgrading from 8-stable to 9-stable I noticed the > error in malloc(9) type 80211node counter. From vmstat -m: > Type InUse MemUse HighUse Requests Siz

Re: invalid statistics for 80211node malloc type

.. please file a PR! Adrian On 25 March 2013 02:02, Adrian Chadd wrote: > ... ? Never noticed this before. Is something double-freeing? > > > > Adrian > > On 25 March 2013 00:44, Sergey Kandaurov wrote: >> Hi, >> >> After upgrading from 8-stable to 9-stable I noticed the >> error in malloc(9)

Re: invalid statistics for 80211node malloc type

On 25 March 2013 13:02, Adrian Chadd wrote: > .. please file a PR! > kern/177366 > > > Adrian > > On 25 March 2013 02:02, Adrian Chadd wrote: >> ... ? Never noticed this before. Is something double-freeing? >> I'd rather say it tries to free never allocated memory? Look at mts_numallocs. (kgdb

Re: FreeBSD 9.1 - openldap slapd lockups, mutex problems

Am 22.01.2013 um 11:19 schrieb Kai Gallasch: > 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

Re: invalid statistics for 80211node malloc type

Can you please find out _where_ that's being called when mts_numallocs is zero? Thanks, Adrian On 25 March 2013 02:33, Sergey Kandaurov wrote: > On 25 March 2013 13:02, Adrian Chadd wrote: >> .. please file a PR! >> > kern/177366 > >> >> >> Adrian >> >> On 25 March 2013 02:02, Adrian Chadd

gptzfsboot: error 4 lba 30

Hi. On one of my fresh installed servers I am seeing the following output during boot: gptzfsboot: error 4 lba 30 gptzfsboot: error 4 lba 31 gptzfsboot: error 4 lba 31 gptzfsboot: error 4 lba 31 gptzfsboot: error 4 lba 30 gptzfsboot: error 4 lba 31 gptzfsboot: error 4 lba 31 gptzfsboot: error 4

Re: gptzfsboot: error 4 lba 30

On Mon, Mar 25, 2013 at 12:52 PM, Kai Gallasch wrote: > Hi. > > On one of my fresh installed servers I am seeing the following output > during boot: > > gptzfsboot: error 4 lba 30 > gptzfsboot: error 4 lba 31 > gptzfsboot: error 4 lba 31 > gptzfsboot: error 4 lba 31 > gptzfsboot: error 4 lba 30 >

Re: [patch] IPMI KCS can drop the lock while servicing a request

On 25.03.2013 02:38, Alexander V. Chernikov wrote: > On 24.03.2013 07:11, Eric van Gyzen wrote: >> At work, we discovered that our application's IPMI thread would often >> use a lot of CPU time. The KCS thread uses DELAY to wait for the BMC, so >> it can run without sleeping for a "long" time with

Re: Virtio and GEOM labels

On Mar 22, 2013, at 8:14 AM, Paul Mather wrote: > I'm running FreeBSD 9-STABLE as a guest under RHEL 6.4 KVM virtualisation. I > have networking and storage in the FreeBSD guest using the Virtio drivers > (with the virtual disk set to "Virtio" in the definition on the host). > Everything is

Re: Virtio and GEOM labels

On Mar 25, 2013, at 1:46 PM, John Nielsen wrote: > On Mar 22, 2013, at 8:14 AM, Paul Mather wrote: > >> I'm running FreeBSD 9-STABLE as a guest under RHEL 6.4 KVM virtualisation. >> I have networking and storage in the FreeBSD guest using the Virtio drivers >> (with the virtual disk set to "

Re: Virtio and GEOM labels

- Original Message - > On Mar 25, 2013, at 1:46 PM, John Nielsen wrote: > > > On Mar 22, 2013, at 8:14 AM, Paul Mather wrote: > > > >> I'm running FreeBSD 9-STABLE as a guest under RHEL 6.4 KVM virtualisation. > >> I have networking and storage in the FreeBSD guest using the Virtio >