Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932650AbVLQSjs (ORCPT ); Sat, 17 Dec 2005 13:39:48 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932653AbVLQSjs (ORCPT ); Sat, 17 Dec 2005 13:39:48 -0500 Received: from mustang.oldcity.dca.net ([216.158.38.3]:26819 "HELO mustang.oldcity.dca.net") by vger.kernel.org with SMTP id S932650AbVLQSjs (ORCPT ); Sat, 17 Dec 2005 13:39:48 -0500 Subject: Re: Dianogsing a hard lockup From: Lee Revell To: Jan Engelhardt Cc: Linux Kernel Mailing List In-Reply-To: References: Content-Type: text/plain Date: Sat, 17 Dec 2005 13:41:23 -0500 Message-Id: <1134844883.11227.11.camel@mindpipe> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 897 Lines: 28 On Sat, 2005-12-17 at 17:09 +0100, Jan Engelhardt wrote: > Hi list, > > > some time after I load drivers (any, rt2500 or via ndiswrap) for a > rt2500-based wlan card, the box locks up hard. Sysrq does not work, so I > suppose it is during irq-disabled context. How could I find out where this > happens? First, stick to rt2500 as you won't get help with binary only drivers here. Try to reproduce the problem from the console, you're more likely to get a usable Oops. Check the driver code & make sure it can't get stuck looping in the interrupt handler due to an unhandled IRQ. Add printks. Finally report it to the rt2500 maintainer. Lee - 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/