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

[Keith Chew]

Hi Eric

>
> Historically a lot of issues have had to do with which cpu you are
> entering the bios from.  So you might try pinning your process
> to differen cpus and see if you can make the failure more deterministic.
>

We are using a Celeron 575 uniprocessor, so we do not have the option
to pin on another cpu. I have tried compiling the kernel in both UP
and SMP configuration, but sadly both causes the hang.

>
> Ugh.  The other possibility is that there is an intermittent failure in
> the hardware, that prevents the boot/reboot.  Wrong values on pull-up
> resistors have been known to cause that kind of thing.
>

Thank you very much for this pointer, will feed that back to the
manufacturer and see if it will give them some clues. The original
purpose for this reboot exercise was to ensure the software will
handle a power failure without any OS/data corruptions. With this new
discovery of unreliable reboot, the next worry is "If reboot is not
reliable, is the boot process also susceptible to the same issue?". I
have not rigged up any hardware to simulate a periodic full shutdown
and boot up process, but will be planning to set this up next.

Thanks again, if you have any other suggestions for us to try, I am all ears!

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