RE: auto_nlist failed on cp_time at location 1

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@xxxxxxxxxxxxxxx
To: tim_stoddard@xxxxxxxxxxx
CC: freebsd-stable@xxxxxxxxxxx
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@xxxxxxxxxxxxxxx

_________________________________________________________________
Express yourself wherever you are. Mobilize!
http://www.gowindowslive.com/Mobile/Landing/Messenger/Default.aspx?Locale=en-US?ocid=TAG_APRIL_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: auto_nlist failed on cp_time at location 1
    ... In the last episode, Tim Stoddard said: ... however I am still seeing the same error just on a different memory ... why my first patch didn't apply; I attached it straight out of my ... CPU usage ...
    (freebsd-stable)
  • Re: [PATCH] - Fix memory ordering problem in wake_futex()
    ... This patch is identical to the first patch except I used smp_wmbinstead ... Here is a fix for a ugly race condition that occurs in wake_futexon IA64. ... preceding "stores" are visible before the lock is released but does NOT prevent ... it ran 16 hours without a failure. ...
    (Linux-Kernel)
  • Re: [PATCH 0/5] powerpc: dynamic ftrace port
    ... There is one exception and that is for the first patch. ... in mainline for PowerPC. ... that first patch is really a bug fix. ...
    (Linux-Kernel)
  • Re: [PATCH -mm] char, moxa: Make isabrds variable global.
    ... Sorry I had no time to look into the first patch. ... The driver is unusable on!MODULE &&!PCI. ... So better fix is to disallow ... Hi Jiri, thanks for your care. ...
    (Linux-Kernel)
  • [PATCH 0/1] swsusp: fix breakage with swap on LVM
    ... In the following two replies to this message there are two versions of ... the same fix, one of which applies to 2.6.16-rc3 and the second to the recent ... in the default Fedora setup where the swap partition is on an LVM. ... I consider the first patch, against 2.6.16-rc3, as an urgent fix that should ...
    (Linux-Kernel)