linux-kernel - Re: Hang on "echo b > /proc/sysrq-trigger"

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]

Date:	Thu, 1 Mar 2012 13:12:38 +1300
From:	Keith Chew <keith.chew@...il.com>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Hang on "echo b > /proc/sysrq-trigger"

Hi Eric

> I would check with your BIOS folks and perhaps play with the kernel
> option.  The most reliable way to peform a reset is to trigger a board
> reset by writing to 0xcf9 or a similar register.  I expect your BIOS
> does that and you can probably get the kernel to do that.  I would
> definitely test to see if you can write to the mostly standard
> 0xcf9 register directly from the kernel and trigger a reset directly.
>
> Once past a reset and with a single cpu all of the failures will be
> happening in the boot path.  So the only possible points of failure
> are in devices that are different between a soft reset and a power on
> reset.
>
> I would check to see if your board perhaps supports post codes or any
> other debugging that will let you see where you are hanging.
>
> It sounds like there is some very rare failure, that is going to be
> a challenge to track down.  I would definitely test more than one
> motherboard to ensure that you can reproduce the problem on more
> than one piece of hardware.  Sometimes hardware is just broken.
>

These are really helpful suggestions, I will try to get to the bottom
on it. Yes, have tried 3 different boards with different RAM, HDD and
CPU. The hang can be reproduced consistently (just not
deterministically at this stage).

Thank you very much again, will update the progress in due course.

Regards
Keith
--
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/