From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id 2A6D4679FD for ; Sat, 14 Oct 2006 09:14:45 +1000 (EST) Subject: Re: preempt crash in 2.6.18 From: Benjamin Herrenschmidt To: Vitaly Bordug In-Reply-To: <20061014012105.6ca4ff05@localhost.localdomain> References: <20061014012105.6ca4ff05@localhost.localdomain> Content-Type: text/plain Date: Sat, 14 Oct 2006 09:14:38 +1000 Message-Id: <1160781278.4792.279.camel@localhost.localdomain> Mime-Version: 1.0 Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Sat, 2006-10-14 at 01:21 +0400, Vitaly Bordug wrote: > On Fri, 13 Oct 2006 09:16:52 -0500 > Rune Torgersen wrote: > > > > > This is from a Freescale 8265 running 2.6.18 > > Anyone have any idea what this is and how to fix it? > > > Yes. Actually, I recall alike thing and used to fix with proper spin-locking if the > cascade PCI irq, which apparently does do_irq that seems to confuse preempt counters. > > Just a pure guess. How so ? Cascades shouldn't do do_IRQ with the new irq code anyway unless this is still arch/ppc, they should do either __do_IRQ or better, generic_handle_irq(). Ben.