From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S275016AbTHGAdF (ORCPT ); Wed, 6 Aug 2003 20:33:05 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S275044AbTHGAdA (ORCPT ); Wed, 6 Aug 2003 20:33:00 -0400 Received: from [217.160.218.230] ([217.160.218.230]:35722 "EHLO p15139176.pureserver.info") by vger.kernel.org with ESMTP id S275016AbTHGAaw (ORCPT ); Wed, 6 Aug 2003 20:30:52 -0400 From: Richard Stevens To: linux-kernel@vger.kernel.org Subject: Newbie debugging question Date: Thu, 7 Aug 2003 02:30:48 +0200 User-Agent: KMail/1.5.2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200308070230.49802.mail@richardstevens.de> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi, I've been searching the net for quite some time now without success so I decided to ask the professionals. I'm looking for kernelhacker newbie friendly documentation on how to figure out a little more about a kernel lockup to be able to give the developer of a device driver some more info. The problem is that after a while the machine locks up with Caps Lock and Scroll lock blinking. I don't see any logs and no messages on the console. I found some posts describing similar events and it was said that the kernel is not completely dead in this state. Is there a way to get some more information? Where should I start reading. Please CC me since I'm not subscribed. Thanks, Richard