Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263600AbTE0NxO (ORCPT ); Tue, 27 May 2003 09:53:14 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263610AbTE0NxN (ORCPT ); Tue, 27 May 2003 09:53:13 -0400 Received: from 81-2-122-30.bradfords.org.uk ([81.2.122.30]:1409 "EHLO 81-2-122-30.bradfords.org.uk") by vger.kernel.org with ESMTP id S263600AbTE0NxM (ORCPT ); Tue, 27 May 2003 09:53:12 -0400 Date: Tue, 27 May 2003 15:12:44 +0100 From: john@grabjohn.com Message-Id: <200305271412.h4RECibF000738@81-2-122-30.bradfords.org.uk> To: jpo234@netscape.net, pavel@ucw.cz Subject: Re: Dead machine, blinking Keyboard and no Oops on console Cc: linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 487 Lines: 13 > > > Blinking keyboard lights means kernel panic. > > Shouldn't a panic cause some message on the console? > > Does the missing message provide a clue? > I'd go for serial console at this point... ...or the morse code output patch... John. - 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/