Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 15 Feb 2001 09:17:07 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 15 Feb 2001 09:16:57 -0500 Received: from nic-31-c31-100.mn.mediaone.net ([24.31.31.100]:35200 "EHLO nic-31-c31-100.mn.mediaone.net") by vger.kernel.org with ESMTP id ; Thu, 15 Feb 2001 09:16:52 -0500 Date: Thu, 15 Feb 2001 08:16:15 -0600 (CST) From: "Scott M. Hoffman" X-X-Sender: Reply-To: To: Subject: 2.4.2-pre3 segfaults and Oops 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 On Wed, 14 Feb 2001, Scott M. Hoffman wrote: > Hello, > See the attached Oops passed through ksymoops 2.3.7(the i386 rpm from > kernel.org). Not sure who should see this... > Is it generally a good idea to reboot the machine after getting one of > these? > I've been trying to see if this was a hardware problem (see my post about memtest86 crashing on me five out of five times at the same point). Even after rebooting from this Oops, I was still getting Segfaults from several programs. Going back to 2.4.1, it seems fine. I ran several tests with bonnie++, first without dma, or irq_unmask enabled for both /dev/hda and /dev/hdb. Then with dma, then with dma and irq_unmask enabled(as usually have it). No Segfaults, no Ooops...yet :) I didn't do any of the above tests in 2.4.2-pre3, as my system just seemed unstable. If there is an indication that it's not my machine being flaky, I'd be glad to test further, in hope of being able to use 2.4.2. Thanks, Scott - 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/