public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Keith Chew <keith.chew@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Hang on "echo b > /proc/sysrq-trigger"
Date: Wed, 29 Feb 2012 10:07:00 -0800	[thread overview]
Message-ID: <m1ehtd8qez.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <CAKaWdxZGg-Xpw2E85bAr8BVgWtXxEitwsir=yXp5qS0FMUk1uQ@mail.gmail.com> (Keith Chew's message of "Sat, 18 Feb 2012 11:54:25 +1300")

Keith Chew <keith.chew@gmail.com> writes:

> Hi
>
> To test the reliability of a hardware, I have a script which reboots a
> machine every 15 minutes after boot up. This machine has a dual video
> output, VGA and DVI-D, both driven via an intel GM45 chipset (I am
> using kernel 2.6.39.24 kernel intel drivers).
>
> Some interesting results (which can be reproduced consistently):
> "echo b > /proc/sysrq-trigger" via DVI-D - after 2-3 days, it hangs
> (freezes) before reboot (dmesg only shows "Resetting...", nothing

My blind guess would be that it is the BIOS on the machine that is hung.

> after that, no panic, stack trace, etc)
> "echo b > /proc/sysrq-trigger" via VGA - runs > 1 week
> "reboot -fn" via VGA or DVI-D - runs > 1 week
> "reboot" via VGA or DVI-D - runs > 1 week
>
> I suspect that the intel graphics driver is not happy with the "echo b
>> /proc/sysrq-trigger" when it is still running.
>
> I would like to make the "echo b" successfully reboot the machine, but
> this would appear to be a hardware bug? Is there anything that can be
> done in the kernel to make the "echo b" successfully work 100%?

echo b > /proc/sysrq-trigger triggers the emergency_restart path which
tries but skips some steps so that it has a reasonable chance of working
when the kernel is wedged, it looks like some of those steps it skips
are needed on your hardware.

Eric

  reply	other threads:[~2012-02-29 18:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-17 22:54 Hang on "echo b > /proc/sysrq-trigger" Keith Chew
2012-02-29 18:07 ` Eric W. Biederman [this message]
2012-02-29 18:28   ` Keith Chew
2012-02-29 20:49     ` Eric W. Biederman
2012-02-29 22:06       ` Keith Chew
2012-02-29 23:34         ` Eric W. Biederman
2012-03-01  0:12           ` Keith Chew
2012-03-10 23:45             ` Keith Chew
2012-03-19  6:34               ` Jon Masters
2012-03-19  6:45                 ` Keith Chew
2012-03-24  1:11                   ` Ray Lee
2012-03-28 20:25                     ` Keith Chew

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m1ehtd8qez.fsf@fess.ebiederm.org \
    --to=ebiederm@xmission.com \
    --cc=keith.chew@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox