Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761191AbXFBPM6 (ORCPT ); Sat, 2 Jun 2007 11:12:58 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758901AbXFBPMv (ORCPT ); Sat, 2 Jun 2007 11:12:51 -0400 Received: from heineken.digium.com ([216.207.245.2]:54660 "EHLO heineken.digium.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754588AbXFBPMu (ORCPT ); Sat, 2 Jun 2007 11:12:50 -0400 Date: Sat, 2 Jun 2007 10:12:46 -0500 (CDT) From: Matt Fredrickson To: Daniel J Blueman Cc: Lee Revell , Linux Kernel , hpa@zytor.com Message-ID: <15604445.159241180797166445.JavaMail.root@jupiler.digium.com> In-Reply-To: <12467610.159201180797054019.JavaMail.root@jupiler.digium.com> Subject: Re: Device Driver Etiquette MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [68.62.219.187] Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1589 Lines: 31 ----- "Daniel J Blueman" wrote: > On 1 Jun, 19:40, "Lee Revell" wrote: > > On 6/1/07, Matthew Fredrickson wrote: > > > > > is it acceptable (although > > > not nice) to simply fix it this way, by disabling irqs while it > loads > > > the firmware? > > > > I would say to just disable IRQs while loading firmware. Almost > every > > server I maintain has some vendor driver which generates a "many > lost > > ticks!" message on load. As long as it's only done at module load > > time it should be fine. > > For anything ~10s or more, you'll probably also need to call the > timer > update function to prevent soft lockup warning being generated. Ahhh... so there is a way to get rid of that cursed message. I forgot to mention this in my original message, the only place that I had seen this problem is on a certain machine (Dell 2950) with a certain distribution (FC6) kernel. I had trimmed the code down to fit in 4K stacks already quite a bit. I believe what actually made it crash and overflow the stack (the straw that breaks the camels back, so to speak) was the intermittent triggering of the softlockup detector. I think if I can disable that while the firmware is loading that will fix the stack overflow issues and correct my problem. Matthew Fredrickson - 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/