From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261411AbVGYS2i (ORCPT ); Mon, 25 Jul 2005 14:28:38 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261420AbVGYS2i (ORCPT ); Mon, 25 Jul 2005 14:28:38 -0400 Received: from ip3e83f6c9.speed.planet.nl ([62.131.246.201]:25535 "EHLO mail.pronexus.nl") by vger.kernel.org with ESMTP id S261411AbVGYS2h (ORCPT ); Mon, 25 Jul 2005 14:28:37 -0400 Message-ID: <20050725202838.2na02hxddmas0o04@intranet.pronexus.nl> Date: Mon, 25 Jul 2005 20:28:38 +0200 From: msmulders@pronexus.nl To: linux-kernel@vger.kernel.org Subject: Re: help! kernel errors? References: <20050725115015.zo345iawcqw0gws0@intranet.pronexus.loc> <42E4C6E7.4060806@namesys.com> <20050725162033.GB23773@harddisk-recovery.com> In-Reply-To: <20050725162033.GB23773@harddisk-recovery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.0.1) X-VirusScanned-By: Pronexus BV X-SpamScanned-By: Pronexus BV Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > And we're only interested in the *first* Oops, not in any later one. > The first Oops is most probably the cause of all other Oopses. The error given was the very first oops. The hundreds (didn't count them ;)) that followed were exactly the same as far as I could see in a glimpse. Any idea from the ksymoops output I sent? - Mark