Don't enter the debugger when executing an AML breakpoint instruction
unless ACPI_DEBUG is defined. Users don't typically care about errant breakpoint instructions. The HP Pavilion 7915 has this in its PCI0 _INI method for rev 0x6040000 of the RSDT.
This commit is contained in:
parent
287bbead5a
commit
4bb443a24d
@ -73,8 +73,7 @@ ACPI_STATUS
|
||||
AcpiOsSignal(UINT32 Function, void *Info)
|
||||
{
|
||||
ACPI_SIGNAL_FATAL_INFO *fatal;
|
||||
char *message;
|
||||
|
||||
|
||||
switch (Function) {
|
||||
case ACPI_SIGNAL_FATAL:
|
||||
fatal = (ACPI_SIGNAL_FATAL_INFO *)Info;
|
||||
@ -82,10 +81,11 @@ AcpiOsSignal(UINT32 Function, void *Info)
|
||||
fatal->Type, fatal->Code, fatal->Argument);
|
||||
kdb_enter("AcpiOsSignal");
|
||||
break;
|
||||
|
||||
|
||||
case ACPI_SIGNAL_BREAKPOINT:
|
||||
message = (char *)Info;
|
||||
kdb_enter(message);
|
||||
#ifdef ACPI_DEBUG
|
||||
kdb_enter((char *)Info);
|
||||
#endif
|
||||
break;
|
||||
|
||||
default:
|
||||
|
Loading…
Reference in New Issue
Block a user