From mboxrd@z Thu Jan 1 00:00:00 1970 From: ANNIE LI Subject: Re: bug in windows "on_reboot = 'preserve'" Date: Fri, 30 Oct 2009 10:03:03 +0800 Message-ID: <4AEA4957.6060703@oracle.com> References: <19176.30378.266644.958440@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1757394802==" Return-path: In-Reply-To: <19176.30378.266644.958440@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Jackson Cc: James Harper , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org This is a multi-part message in MIME format. --===============1757394802== Content-Type: multipart/alternative; boundary="------------070701080002060303060704" This is a multi-part message in MIME format. --------------070701080002060303060704 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Following is a way to make system crash from keyboard. Thanks Annie. Forcing a System Crash from the Keyboard A system crash can be directly caused from most keyboards. In Windows XP, this feature is available on i8042prt ports (PS/2 keyboards), while in Windows Vista and later, it is available on USB keyboards as well. It can also be fully configured to accommodate various keyboards using the registry key settings. Two preparations must be made before this can be done: 1. If you wish a crash dump file to be written, you must enable such dump files, choose the path and file name, and select the size of the dump file. For details, see Enabling a Kernel-Mode Dump File . 2. With PS/2 keyboards, you must enable the keyboard-initiated crash in the registry. In the registry key *HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\i8042prt\Parameters*, create a value named *CrashOnCtrlScroll*, and set it equal to REG_DWORD 0x1 (or any nonzero value). 3. With USB keyboards, you must set the registry key *HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\kbdhid\Parameters* and create a value named *CrashOnCtrlScroll*, and set it equal to REG_DWORD 0x1 (or any nonzero value). *Note* There is a limitation with the /Kbdhid.sys/ driver that allows you to generate the memory dump process by using a USB keyboard. The CTRL+SCROLL LOCK+SCROLL LOCK keyboard shortcut does not work if the computer stops responding at a high interrupt request level (IRQL). This limitation exists because the /Kbdhid.sys/ driver operates at a lower IRQL than the i8042prt.sys driver. For more information on using this feature with the USB keyboards, refer to the article Generate a memory dump file by using the keyboard . The system must be rebooted before these changes will take effect. After this has been done, the keyboard crash can be initiated as follows. Hold down the /rightmost /CTRL key, and press the SCROLL LOCK/ /key twice. It is possible for a system to freeze in such a way that this CTRL+SCROLL LOCK+SCROLL LOCK sequence will not work. However, this should be a very rare occurrence. The CTRL+SCROLL LOCK+SCROLL LOCK crash initiation will work even in many instances where CTRL+ALT+DELETE does not work. The system then calls *KeBugCheck* and issues bug check 0xE2 (MANUALLY_INITIATED_CRASH). Unless crash dumps have been disabled, a crash dump file is written at this point. If a kernel debugger is attached to the frozen machine, the machine will break into the kernel debugger after the crash dump file has been written. --------------070701080002060303060704 Content-Type: multipart/related; boundary="------------020805080302070108010507" --------------020805080302070108010507 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Following is a way to make system crash from keyboard.

Thanks
Annie.

Forcing a System Crash from the Keyboard

A system crash can be directly caused from most keyboards. In Windows XP, this feature is available on i8042prt ports (PS/2 keyboards), while in Windows Vista and later, it is available on USB keyboards as well. It can also be fully configured to accommodate various keyboards using the registry key settings.

Two preparations must be made before this can be done:

  1. If you wish a crash dump file to be written, you must enable such dump files, choose the path and file name, and select the size of the dump file. For details, see Enabling a Kernel-Mode Dump File.
  2. With PS/2 keyboards, you must enable the keyboard-initiated crash in the registry. In the registry key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\i8042prt\Parameters, create a value named CrashOnCtrlScroll, and set it equal to REG_DWORD 0x1 (or any nonzero value).
  3. With USB keyboards, you must set the registry key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\kbdhid\Parameters and create a value named CrashOnCtrlScroll, and set it equal to REG_DWORD 0x1 (or any nonzero value).

    Note  There is a limitation with the Kbdhid.sys driver that allows you to generate the memory dump process by using a USB keyboard. The CTRL+SCROLL LOCK+SCROLL LOCK keyboard shortcut does not work if the computer stops responding at a high interrupt request level (IRQL). This limitation exists because the Kbdhid.sys driver operates at a lower IRQL than the i8042prt.sys driver. For more information on using this feature with the USB keyboards, refer to the article  Generate a memory dump file by using the keyboard.

The system must be rebooted before these changes will take effect.

After this has been done, the keyboard crash can be initiated as follows. Hold down the rightmost CTRL key, and press the SCROLL LOCK key twice.

It is possible for a system to freeze in such a way that this CTRL+SCROLL LOCK+SCROLL LOCK sequence will not work. However, this should be a very rare occurrence. The CTRL+SCROLL LOCK+SCROLL LOCK crash initiation will work even in many instances where CTRL+ALT+DELETE does not work.

The system then calls KeBugCheck and issues bug check 0xE2 (MANUALLY_INITIATED_CRASH). Unless crash dumps have been disabled, a crash dump file is written at this point.

If a kernel debugger is attached to the frozen machine, the machine will break into the kernel debugger after the crash dump file has been written.

--------------020805080302070108010507 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-ID: Content-Base: "http://internet_link_sm.gif/" Content-Location: "http://internet_link_sm.gif/" 502 Bad Gateway

Bad Gateway

The following error occurred:

[code=DNS_HOST_NOT_FOUND] The host name was not found during the DNS lookup. Contact your system administrator if the problem is not found by retrying the URL.

Please contact the administrator. --------------020805080302070108010507-- --------------070701080002060303060704-- --===============1757394802== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============1757394802==--