auto_nlist failed on cp_time at location 1

[Tim Stoddard]

Dan,

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

Thanks for the help.

--
Tim Stoddard

> Date: Thu, 24 Apr 2008 10:57:07 -0500
> From: dnelson at allantgroup.com
> To: tim_stoddard at hotmail.com
> CC: freebsd-stable at freebsd.org
> Subject: Re: auto_nlist failed on cp_time at location 1
> 
> 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.
> > 
> > Apr 24 10:16:41 shaggy snmpd[73273]: kvm_read(*, 1, 0xbf7fe830, 20) = -1: kvm_read: Bad address
> > Apr 24 10:16:41 shaggy snmpd[73273]: auto_nlist failed on cp_time at location 1
> > Apr 24 10:16:46 shaggy snmpd[73273]: kvm_read(*, 1, 0xbf7fe830, 20) = -1: kvm_read: Bad address
> > Apr 24 10:16:46 shaggy snmpd[73273]: auto_nlist failed on cp_time at location 1
> > Apr 24 10:16:51 shaggy snmpd[73273]: kvm_read(*, 1, 0xbf7fe830, 20) = -1: kvm_read: Bad address
> > Apr 24 10:16:51 shaggy snmpd[73273]: auto_nlist failed on cp_time at location 1
> 
> 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.
> 
> -- 
> 	Dan Nelson
> 	dnelson at allantgroup.com

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