Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 12 Apr 2001 20:58:34 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 12 Apr 2001 20:58:24 -0400 Received: from blount.mail.mindspring.net ([207.69.200.226]:36114 "EHLO blount.mail.mindspring.net") by vger.kernel.org with ESMTP id ; Thu, 12 Apr 2001 20:58:16 -0400 Date: Thu, 12 Apr 2001 20:57:40 -0400 (EDT) From: Jon Eisenstein Reply-To: jeisen@mindspring.com To: Rik van Riel cc: linux-kernel@vger.kernel.org Subject: Re: Problem: Random paging request errors In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > > (2) Every so often, I get a non-fatal error on my screen about a > > kernel paging request error. > > If it's usually the same address, we're probably dealing with > a kernel bug. If you always get different addresses, chances > are your RAM is broken (you can test this with memtest86). I tested with memtest86, and luckily found no problems (and good, because this RAM is new!). > Decoding the oops is always useful, especially if you can find > a pattern after you've decoded a few. And if you don't manage > to find any pattern in them, you know the suspicion lies with > the hardware ... I decoded the oops, from /var/log/messages, but I'm not sure how to read it. Do you have any pointers? Where should I be looking for patterns? Do I just wait until the next time it happens, get a second log, and diff them? > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/