Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 24 Apr 2008 14:42:36 -0500
From:      Tim Stoddard <tim_stoddard@hotmail.com>
To:        Dan Nelson <dnelson@allantgroup.com>
Cc:        freebsd-stable@freebsd.org
Subject:   RE: auto_nlist failed on cp_time at location 1
Message-ID:  <BAY112-W34049967D88512E9932C84FFE20@phx.gbl>
In-Reply-To: <20080424155706.GB81245@dan.emsphone.com>
References:  <BAY112-W393CA2AD5ACD5E09A6AB17FFE30@phx.gbl> <20080424013421.GF99910@dan.emsphone.com> <BAY112-W14A4215BAA32EA926B6D3BFFE20@phx.gbl> <BAY112-W46FCE6DD0A53179D07B499FFE20@phx.gbl>  <20080424155706.GB81245@dan.emsphone.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Dan,

I reapplied the first patch you send (this time properly) and it fix the is=
sue.  I hope the port maintainer can get your patch committed so other do n=
ot have to go though the same process. =20

Thanks for the help.

--
Tim Stoddard

> Date: Thu, 24 Apr 2008 10:57:07 -0500
> From: dnelson@allantgroup.com
> To: tim_stoddard@hotmail.com
> CC: freebsd-stable@freebsd.org
> Subject: Re: auto_nlist failed on cp_time at location 1
>=20
> In the last episode (Apr 24), Tim Stoddard said:
> > I applied your patch by hand and recompiled/reinstalled net-snmp,
> > however I am still seeing the same error just on a different memory
> > address now.
> >=20
> > Apr 24 10:16:41 shaggy snmpd[73273]: kvm_read(*, 1, 0xbf7fe830, 20) =3D=
 -1: kvm_read: Bad address
> > Apr 24 10:16:41 shaggy snmpd[73273]: auto_nlist failed on cp_time at lo=
cation 1
> > Apr 24 10:16:46 shaggy snmpd[73273]: kvm_read(*, 1, 0xbf7fe830, 20) =3D=
 -1: kvm_read: Bad address
> > Apr 24 10:16:46 shaggy snmpd[73273]: auto_nlist failed on cp_time at lo=
cation 1
> > Apr 24 10:16:51 shaggy snmpd[73273]: kvm_read(*, 1, 0xbf7fe830, 20) =3D=
 -1: kvm_read: Bad address
> > Apr 24 10:16:51 shaggy snmpd[73273]: auto_nlist failed on cp_time at lo=
cation 1
>=20
> Hm.  It looks like net-snmp has two different pieces of code that both
> do the same thing (read CPU and vmstat info).  I wonder which OIDs
> trigger them on your system?  On my system, walking
> enterprises.ucdavis.systemStats uses the cpu_nlist.c code.  Here's a
> patch for the other file (vmstat_freebsd2.c); it's not even compiled on
> my 7-stable system, so I can't verify that it's correct.  I'm not sure
> why my first patch didn't apply; I attached it straight out of my
> net-snmp/files/ directory.
>=20
> --=20
> 	Dan Nelson
> 	dnelson@allantgroup.com

_________________________________________________________________
Express yourself wherever you are. Mobilize!
http://www.gowindowslive.com/Mobile/Landing/Messenger/Default.aspx?Locale=
=3Den-US?ocid=3DTAG_APRIL=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BAY112-W34049967D88512E9932C84FFE20>