From owner-freebsd-current Mon Mar 16 12:42:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17610 for freebsd-current-outgoing; Mon, 16 Mar 1998 12:42:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17586 for ; Mon, 16 Mar 1998 12:42:49 -0800 (PST) (envelope-from karl@Mercury.mcs.net) Received: from Mercury.mcs.net (karl@Mercury.mcs.net [192.160.127.80]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id OAA00440; Mon, 16 Mar 1998 14:42:49 -0600 (CST) Received: (from karl@localhost) by Mercury.mcs.net (8.8.7/8.8.2) id OAA23209; Mon, 16 Mar 1998 14:42:48 -0600 (CST) Message-ID: <19980316144248.56518@mcs.net> Date: Mon, 16 Mar 1998 14:42:48 -0600 From: Karl Denninger To: Sir Mordred Cc: freebsd-current@FreeBSD.ORG Subject: Re: softupdate panic References: <199803162028.MAA00664@mordred.cs.ucla.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199803162028.MAA00664@mordred.cs.ucla.edu>; from Sir Mordred on Mon, Mar 16, 1998 at 12:28:48PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Make sure you have all the patches. I haven't seen a spurious Sig11 since I applied them. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost On Mon, Mar 16, 1998 at 12:28:48PM -0800, Sir Mordred wrote: > >From a kernel which was cvsup'd last night. This appears to happen > when under load. I won't discount bad memory on my machine, but it's > hard to tell... > > Also, FWIW, the new VM patches from last night: I still end up getting > the occaisional spurious sig 11's on sendmail and cron. Restarting the > daemons appears to make them go away -- which diminishes my suspicions > of memory hardware problems. No panics in VM code, though, which is a > good thing. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message