linux-kernel - Re: debugging an oops that kills the system

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <adar669okrk.fsf@cisco.com>
Date:	Tue, 21 Oct 2008 11:39:27 -0700
From:	Roland Dreier <rdreier@...co.com>
To:	"Dan Upton" <upton.dan.linux@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: debugging an oops that kills the system

 > I'm hoping for some pointers on debugging an oops that ultimately
 > hangs the system.  I'm doing some scheduler work and I can fairly
 > reliably duplicate the error on my machine, but the output is too
 > large for one screen and the system becomes unresponsive after the
 > crash so I can't scroll the console.  I tried purchasing a  USB->DB9
 > cable to log to a remote terminal, but so far I haven't had any luck
 > getting that to work.  Using kdump/kexec doesn't work either--I got
 > the second kernel to boot successfully using the magic sysrq example
 > in the documentation, but the second kernel doesn't boot with my
 > actual crash.  Any other suggestions for what I might do?

If you have two machines (it sounds like you do) and serial console is
not working for you (could be a setup problem -- do you have a
"console=" line on your kernel command line?), then netconsole might be
a good way to debug: Documentation/networking/netconsole.txt

 - R.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/