linux-kernel - Re: troubleshooting/debugging hard locks

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] [day] [month] [year] [list]

Date:	Tue, 20 May 2008 14:19:03 -0700
From:	"Ray Lee" <ray-lk@...rabbit.org>
To:	"Lee Howard" <faxguy@...ardsilvan.com>
Cc:	"Zan Lynx" <zlynx@....org>, linux-kernel@...r.kernel.org
Subject: Re: troubleshooting/debugging hard locks

On Tue, May 20, 2008 at 1:47 PM, Lee Howard <faxguy@...ardsilvan.com> wrote:
> After further troubleshooting it turns out that the message above was a bit
> of a red herring.  I moved the PCIe modem card from one PCIe slot to another
> so that it would be on a different IRQ (one that wasn't shared with the
> network, ATA, and USB).  The message above does not occur now, however, the
> hard lock is back... and this time with no kernel messages at all.
>
> So, I'm back to square one again... I've got:
>
>  nmi_watchdog=1 idle=poll nohz=off
>
> ... and still I get the hard lockup and no kernel messages.  How do I
> troubleshoot/debug this?  How do I know where to look?

The only thing I can think of is to recompile the latest mainline
kernel with all debugging options enabled in the .config. and then try
to reproduce with that.
--
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/