linux-kernel - 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 for Android: free password hash cracker in your pocket

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

Message-ID: <ba7d8f720810211014g472c3e83oba511c24e1c2eb97@mail.gmail.com>
Date:	Tue, 21 Oct 2008 13:14:02 -0400
From:	"Dan Upton" <upton.dan.linux@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: debugging an oops that kills the system

Hi all,

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?

Thanks,
-dan
--
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/