From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 24 Dec 2002 13:48:18 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 24 Dec 2002 13:48:18 -0500 Received: from mail41-s.fg.online.no ([148.122.161.41]:26821 "EHLO mail41.fg.online.no") by vger.kernel.org with ESMTP id ; Tue, 24 Dec 2002 13:48:17 -0500 Date: Tue, 24 Dec 2002 19:56:26 +0100 (MET) Message-Id: <200212241856.TAA14250@mail41.fg.online.no> From: Michael To: linux-kernel@vger.kernel.org Subject: Debugging "cpu freezes" Organization: na X-Mailer: Sylpheed version 0.7.4 (GTK+ 1.2.10; i386-debian-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org I'm wondering what the procedure for debugging instances where the computer freezes completly, when sysRQ doesn't even work. Since I know how to reproduce(and workaround for daily use) a complete system freeze in 2.4.X, don't know if I can explain how, but for example booting the knoppix live-cd to kde would be a perfect way of freezing it(after moving a few windows) (Not using KDE reduces the risk of it freezing greatly)