From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from elvis.franken.de (elvis.franken.de [193.175.24.41]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 023B73368B0; Mon, 6 Apr 2026 12:35:05 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=193.175.24.41 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775478909; cv=none; b=EbIH6A38RaJTOejMV1NIwbLHjpWmOod7yMd66Zxn+WsEv3rZBe52Zm+oUavaJ8M5HPTKkpB5a48pvtE28+LssYJRuUkkqvFf5spjs89FlNZgc+v4V1enhIugJRxX64YyJBhwaTqSpJU+RuDQm+muFE53ZJz6cHpkY4ct5Bj7iGU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775478909; c=relaxed/simple; bh=vBPIg4H+iweXLC+OcCInTHlCM6AOS6qRwvX8vRHnn/Y=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=GXhMh0qUOu6knBz95xqcpcvwwb2naOITNGBu1r6Zl/P7FGsEDVxyGEDXMX9cUQjNfLOGwuddkkexsXxvlESeGOWjrTqERcH0RvFX7csBEtRM1dzmmQAsVnKKnn/Uxw1wXaLKZIThsfbFT6tsNbXsqP1GssN4A6xl/2hJAyZc6Gw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=alpha.franken.de; spf=pass smtp.mailfrom=alpha.franken.de; arc=none smtp.client-ip=193.175.24.41 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=alpha.franken.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=alpha.franken.de Received: from uucp by elvis.franken.de with local-rmail (Exim 3.36 #1) id 1w9jAQ-00040x-00; Mon, 06 Apr 2026 14:34:58 +0200 Received: by alpha.franken.de (Postfix, from userid 1000) id A998EC0EA5; Mon, 6 Apr 2026 14:33:56 +0200 (CEST) Date: Mon, 6 Apr 2026 14:33:56 +0200 From: Thomas Bogendoerfer To: "Maciej W. Rozycki" Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/3] MIPS: DEC: Rate-limit memory errors Message-ID: References: Precedence: bulk X-Mailing-List: linux-mips@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Sat, Mar 28, 2026 at 03:49:52PM +0000, Maciej W. Rozycki wrote: > Hi, > > A recent failure of one of my systems revealed an issue with memory error > logging where the flood of messages produced, which reported corrected ECC > errors, made the system unusable despite the errors themselves having been > recovered from and the messages serving informational purpose only. > > I took the opportunity and actually verified the rate-limiting does its > purpose with the offending system before cleaning memory module contacts, > which has cured the original problem, the third time in ~25 years I've had > the system for -- not too bad, but clearly a recurring issue. > > For consistency I have also updated support for the other two DEC memory > system designs, although they're parity-based and therefore memory errors > are fatal and consequently less likely to cause a message flood, although > in principle still possible where a faulty memory location causes a bus > error exception to kill user processes repeatedly. They seem not to have > the issue with memory contacts though, which use the common SIMM design > rather than 0.1"-pitch PCB connectors. > > Please apply. series applied to mips-next Thomas. -- Crap can work. Given enough thrust pigs will fly, but it's not necessarily a good idea. [ RFC1925, 2.3 ]