Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266330AbUFQBDR (ORCPT ); Wed, 16 Jun 2004 21:03:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266323AbUFQBDR (ORCPT ); Wed, 16 Jun 2004 21:03:17 -0400 Received: from palrel10.hp.com ([156.153.255.245]:4491 "EHLO palrel10.hp.com") by vger.kernel.org with ESMTP id S266330AbUFQBDN (ORCPT ); Wed, 16 Jun 2004 21:03:13 -0400 From: David Mosberger MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16592.60876.886257.165633@napali.hpl.hp.com> Date: Wed, 16 Jun 2004 18:03:08 -0700 To: Balazs Scheidler Cc: linux-kernel@vger.kernel.org Subject: Re: kernel oops on ia64 (2.6.6 + 0521 ia64 patch) In-Reply-To: <1087420973.4345.19.camel@bzorp.balabit> References: <1087420973.4345.19.camel@bzorp.balabit> X-Mailer: VM 7.18 under Emacs 21.3.1 Reply-To: davidm@hpl.hp.com X-URL: http://www.hpl.hp.com/personal/David_Mosberger/ Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 713 Lines: 18 Balazs> I'm encountering more-or-less reproducible oopses on a 2.6.6 Balazs> kernel with 0521 ia64 patch, compiled with gcc 3.3.3 on Balazs> Debian sarge. Balazs> The box is a HP rx2600 with a single processor, kernel is Balazs> compiled in UP mode. Here is the backtrace (saved off froma Balazs> terminal session on the network console, thus the Balazs> formatting, but the info should be correct). Does the oops go away with an SMP kernel? --david - 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/