Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 11 Dec 2001 14:58:51 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 11 Dec 2001 14:58:41 -0500 Received: from pl475.nas921.ichikawa.nttpc.ne.jp ([210.165.235.219]:62994 "EHLO mbr.sphere.ne.jp") by vger.kernel.org with ESMTP id ; Tue, 11 Dec 2001 14:58:31 -0500 Date: Wed, 12 Dec 2001 04:58:23 +0900 From: Bruce Harada To: Brian Horton Cc: linux-kernel@vger.kernel.org Subject: Re: how to debug a deadlock'ed kernel? Message-Id: <20011212045823.0bf53af9.bruce@ask.ne.jp> In-Reply-To: <3C166540.DC0BDBEE@mail.com> In-Reply-To: <3C166540.DC0BDBEE@mail.com> X-Mailer: Sylpheed version 0.6.5 (GTK+ 1.2.6; i686-pc-linux-gnu) X-Face: $qrUU,Lz=B[A}i%m2Rg^Ik;~V@]$Ay)$S`wUf3:^aZ1UdLf,_;1y7_xbEh=Yv*wB0=Fv]a1hj14_qQsl[f1KX]q4IdhwmSIeP6>Ap@[e$c$G;;ObLI7?YXsq*)M'3Jp wrote: > Anyone got any good tips on how to debug a SMP system that is locked up > in a deadlock situation in the kernel? I'm working on a kernel module, > and after some number of hours of stress testing, the box locks up. None > of the sysrq options show anything on the display, though the reBoot > option does reboot the system. RedHat 6.2 and its 2.2.14 kernel. Doesn't > hang for me on 2.4, so I need to debug it here... > > Any hints? Try using a serial console (activate it in your kernel config and hook up another PC to the serial port - if it's oopsing, you should see the oops over the serial line.) Also, I believe you can use kdb via serial as well (although I've never tried). Bruce - 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/