From owner-freebsd-security Thu Jun 1 18:46:31 2000 Delivered-To: freebsd-security@freebsd.org Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by hub.freebsd.org (Postfix) with ESMTP id 0D73837BAD9 for ; Thu, 1 Jun 2000 18:46:25 -0700 (PDT) (envelope-from eugen@svzserv.kemerovo.su) Received: from svzserv.kemerovo.su (kost.svzserv.kemerovo.su [213.184.65.82]) by www.svzserv.kemerovo.su (8.9.3/8.9.3) with ESMTP id JAA32391 for ; Fri, 2 Jun 2000 09:46:22 +0800 (KRAST) (envelope-from eugen@svzserv.kemerovo.su) Message-ID: <39371224.99DCCEBF@svzserv.kemerovo.su> Date: Fri, 02 Jun 2000 09:47:16 +0800 From: Eugene Grosbein Organization: SVZServ X-Mailer: Mozilla 4.7 [en] (Win95; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: "freebsd-security@FreeBSD.ORG" Subject: No strategy for buffer Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello! I post this here because the my problem marked in daily "security check output". After receiving "FreeBSD Security Advisory: FreeBSD-SA-00:19.semconfig" I cvsup'ed my 3.4-STABLE upto last 3-STABLE, rebuilt and reinstalled world and kernel, without problems. 2 days all was fine. But I received in "security check output" this morning: > No strategy for buffer at 0xc200fef8 > : 0xc5c6ad40: type VREG, usecount 4, writecount 0, refcount 0, flags (VOBJBUF) > tag VT_PROCFS, type 12, pid 13862, mode 124, flags 0 > : 0xc5c6ad40: type VREG, usecount 4, writecount 0, refcount 0, flags (VOBJBUF) > tag VT_PROCFS, type 12, pid 13862, mode 124, flags 0 > vnode_pager_getpages: I/O read error > vm_fault: pager read error, pid 20442 (mc) > pid 20442 (mc), uid 0: exited on signal 11 > pid 20462 (cvsupd), uid 2029: exited on signal 10 (core dumped) This computer is not overclocked. This is Celeron 366/64M RAM/256M SWAP. One more, one day before cvsupd died on signal 4. This box was running for 4 months without a problem. Sometimes I upgrade it to latest 3-STABLE. Is it a security or hardware problem and how do I resolve this? Eugene Grosbeign To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message