From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753981AbXDWQTD (ORCPT ); Mon, 23 Apr 2007 12:19:03 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754006AbXDWQTD (ORCPT ); Mon, 23 Apr 2007 12:19:03 -0400 Received: from mx1.redhat.com ([66.187.233.31]:40142 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753981AbXDWQTB (ORCPT ); Mon, 23 Apr 2007 12:19:01 -0400 Date: Mon, 23 Apr 2007 12:18:48 -0400 From: Dave Jones To: Alan Cox Cc: Linux Kernel , Antonino Daplas Subject: Re: Prevent softlockup triggering in nvidiafb Message-ID: <20070423161848.GA27649@redhat.com> Mail-Followup-To: Dave Jones , Alan Cox , Linux Kernel , Antonino Daplas References: <20070423151053.GA5653@redhat.com> <20070423165505.4aecd186@the-village.bc.nu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070423165505.4aecd186@the-village.bc.nu> User-Agent: Mutt/1.4.2.2i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Apr 23, 2007 at 04:55:05PM +0100, Alan Cox wrote: > On Mon, 23 Apr 2007 11:36:30 -0400 > Dave Jones wrote: > > > If the chip locks up, we get into a long polling loop, > > where the softlockup detector kicks in. > > See https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=151878 > > for an example. > > Surely in this situation the softlockup report and trap out is precisely > what should be occurring. We can't do anything useful with the trace. It already prints out info that the hardware locked up. Dave -- http://www.codemonkey.org.uk