Re: 2.6.13-rc3 ACPI regression and hang on x86-64

[Kenneth Parrish]

-=> Mikael Pettersson wrote to All <=-

 MP> With the i386 kernel, 2.6.13-rc3 mostly works, but
 MP> it fails to detect the CPU's C2 state.
This kernel fails to boot, occasionally, stopping at the system BIOS
check successful message, but got C2 back with the recent patch here.
LILO version 22.5.9 and Cyrix/VIA e-machines '99. I might be able to
provide more information.

... Mars' surface air pressure is less than where high-altitude jets fly here.
--- MultiMail/Linux v0.46
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.13-rc3 ACPI regression and hang on x86-64

[Kenneth Parrish]

-= Mikael Pettersson wrote to All =-

 MP With the i386 kernel, 2.6.13-rc3 mostly works, but
 MP it fails to detect the CPU's C2 state.
This kernel fails to boot, occasionally, stopping at the system BIOS
check successful message, but got C2 back with the recent patch here.
LILO version 22.5.9 and Cyrix/VIA e-machines '99. I might be able to
provide more information.

... Mars' surface air pressure is less than where high-altitude jets fly here.
--- MultiMail/Linux v0.46
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

RE: 2.6.13-rc3 ACPI regression and hang on x86-64

[Mikael Pettersson]

On Thu, 14 Jul 2005 15:23:52 -0400, Brown, Len wrote:
>>acpi_ec-0217 [04] acpi_ec_leave_burst_mo: --->status fail
>>
>>on the console, and then the machine is hung hard.
>
>2.6.13-rc3 x86_64 failed, but 
>2.6.13-rc2 x86_64 worked
>
>And both of these revisions in the i386 kernel still work?

With the i386 kernel, 2.6.13-rc2 works perfectly.
With the i386 kernel, 2.6.13-rc3 mostly works, but
it fails to detect the CPU's C2 state.

>Is it possible for you to test the latest ACPI patch?
>http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/release/
>2.6.13/

I was going to, but as it was for -rc2 not -rc3 I decided to
try Venkatesh Pallipadi's C-state FADT regression patch first.

Success! That solved all my ACPI issues with -rc3.

"Yu, Luming" wrote:
>> on the console, and then the machine is hung hard.
>If you didn't press that key,   the machine still hung?

No it worked except for having no power management and an
unusable console due to ACPI having reduced the brightness.

/Mikael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

RE: 2.6.13-rc3 ACPI regression and hang on x86-64

[Mikael Pettersson]

On Thu, 14 Jul 2005 15:23:52 -0400, Brown, Len wrote:
acpi_ec-0217 [04] acpi_ec_leave_burst_mo: ---status fail

on the console, and then the machine is hung hard.

2.6.13-rc3 x86_64 failed, but 
2.6.13-rc2 x86_64 worked

And both of these revisions in the i386 kernel still work?

With the i386 kernel, 2.6.13-rc2 works perfectly.
With the i386 kernel, 2.6.13-rc3 mostly works, but
it fails to detect the CPU's C2 state.

Is it possible for you to test the latest ACPI patch?
http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/release/
2.6.13/

I was going to, but as it was for -rc2 not -rc3 I decided to
try Venkatesh Pallipadi's C-state FADT regression patch first.
http://marc.theaimsgroup.com/?l=linux-kernelm=112135903100520w=2
Success! That solved all my ACPI issues with -rc3.

Yu, Luming wrote:
 on the console, and then the machine is hung hard.
If you didn't press that key,   the machine still hung?

No it worked except for having no power management and an
unusable console due to ACPI having reduced the brightness.

/Mikael
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.13-rc3 ACPI regression and hang on x86-64

[Yu, Luming]

On Thursday 14 July 2005 18:36, Mikael Pettersson wrote:
> On my x86-64 laptop (Targa Visionary 811: Athlon64 + VIA chipset,
> Arima OEM:d HW also sold by eMachines and others), ACPI is broken
> and hangs the x86-64 2.6.13-rc3 kernel.
>
> During boot, ACPI reduces the screen's brightness (it's always
> done this in the x86-64 kernels but not the i386 ones), so I
> have to press a specific key combination (Fn+F8) to increase the
> brightness. This worked up to and including the 2.6.13-rc2 kernel,
> but with 2.6.13-rc3 it causes an error message:
>
> acpi_ec-0217 [04] acpi_ec_leave_burst_mo: --->status fail
This message is a warning.

>
> on the console, and then the machine is hung hard.
If you didn't press that key,   the machine still hung?

>
> With the i386 kernel, both this key combination and the other one
> for reducing the brightness work as expected.
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

RE: 2.6.13-rc3 ACPI regression and hang on x86-64

[Brown, Len]

>acpi_ec-0217 [04] acpi_ec_leave_burst_mo: --->status fail
>
>on the console, and then the machine is hung hard.

2.6.13-rc3 x86_64 failed, but 
2.6.13-rc2 x86_64 worked

And both of these revisions in the i386 kernel still work?

>+evxfevnt-0203 [07] acpi_enable_event : Could not enable
power_button
>event
>+ evxface-0157 [06] acpi_install_fixed_eve: Could not enable fixed
event.
>+acpi_button-0224 [05] acpi_button_add   : Error installing notify
>handler
>+ACPI: Power Button (CM) [PWRB]


We're toast at this point, even before the EC message.

Looks like this failure was reported here
http://bugzilla.kernel.org/show_bug.cgi?id=4534
and is assigned to Luming.

Is it possible for you to test the latest ACPI patch?
http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/release/
2.6.13/

Also, it would be good to confirm the same failure exists with
CONFIG_ACPI_DEBUG=n.

thanks,
-Len

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

2.6.13-rc3 ACPI regression and hang on x86-64

[Mikael Pettersson]

On my x86-64 laptop (Targa Visionary 811: Athlon64 + VIA chipset,
Arima OEM:d HW also sold by eMachines and others), ACPI is broken
and hangs the x86-64 2.6.13-rc3 kernel.

During boot, ACPI reduces the screen's brightness (it's always
done this in the x86-64 kernels but not the i386 ones), so I
have to press a specific key combination (Fn+F8) to increase the
brightness. This worked up to and including the 2.6.13-rc2 kernel,
but with 2.6.13-rc3 it causes an error message:

acpi_ec-0217 [04] acpi_ec_leave_burst_mo: --->status fail

on the console, and then the machine is hung hard.

With the i386 kernel, both this key combination and the other one
for reducing the brightness work as expected.

A diff between the dmesg logs for 2.6.13-rc2 and -rc3 (included below)
indicates that APCI experiences several new errors in rc3.

/Mikael

--- dmesg-2.6.13-rc2-x86_64 2005-07-14 11:59:58.0 +0200
+++ dmesg-2.6.13-rc3-x86_64 2005-07-14 11:59:59.0 +0200
@@ -1,5 +1,5 @@
 Bootdata ok (command line is ro root=/dev/hda7)
-Linux version 2.6.13-rc2 ([EMAIL PROTECTED]) (gcc version 4.0.1) #1 Fri Jul 8 
15:44:53 CEST 2005
+Linux version 2.6.13-rc3 ([EMAIL PROTECTED]) (gcc version 4.0.1) #1 Wed Jul 13 
17:51:48 CEST 2005
 BIOS-provided physical RAM map:
  BIOS-e820:  - 0009f800 (usable)
  BIOS-e820: 0009f800 - 000a (reserved)
@@ -37,46 +37,49 @@
 Initializing CPU#0
 PID hash table entries: 2048 (order: 11, 65536 bytes)
 time.c: Using 1.193182 MHz PIT timer.
-time.c: Detected 1603.693 MHz processor.
+time.c: Detected 1603.705 MHz processor.
 time.c: Using PIT/TSC based timekeeping.
 Console: colour VGA+ 80x25
 Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
 Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
-Memory: 511408k/523200k available (1653k kernel code, 11012k reserved, 941k 
data, 128k init)
-Calibrating delay using timer specific routine.. 3211.68 BogoMIPS 
(lpj=16058428)
+Memory: 511408k/523200k available (1656k kernel code, 11012k reserved, 941k 
data, 128k init)
+Calibrating delay using timer specific routine.. 3211.67 BogoMIPS 
(lpj=16058383)
 Mount-cache hash table entries: 256
 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
 CPU: L2 Cache: 1024K (64 bytes/line)
+mtrr: v2.0 (20020519)
 CPU: Mobile AMD Athlon(tm) 64 Processor 2800+ stepping 0a
- tbxface-0118 [02] acpi_load_tables  : ACPI Tables successfully acquired
+ tbxface-0120 [02] acpi_load_tables  : ACPI Tables successfully acquired
 Parsing all Control 
Methods:
 Table [DSDT](id F005) - 482 Objects with 46 Devices 148 Methods 16 Regions
 Parsing all Control Methods:
 Table [SSDT](id F003) - 3 Objects with 0 Devices 0 Methods 0 Regions
-ACPI Namespace successfully loaded at root 803ac6e0
-evxfevnt-0094 [03] acpi_enable   : Transition to ACPI mode successful
+ACPI Namespace successfully loaded at root 803ad260
+evxfevnt-0096 [03] acpi_enable   : Transition to ACPI mode successful
 Using local APIC timer interrupts.
 Detected 12.528 MHz APIC timer.
 testing NMI watchdog ... OK.
 NET: Registered protocol family 16
+ACPI: bus type pci registered
 PCI: Using configuration type 1
-mtrr: v2.0 (20020519)
-ACPI: Subsystem revision 20050309
-evgpeblk-0979 [06] ev_create_gpe_block   : GPE 00 to 0F [_GPE] 2 regs on int 
0xA
-evgpeblk-0987 [06] ev_create_gpe_block   : Found 7 Wake, Enabled 0 Runtime 
GPEs in this block
+ACPI: Subsystem revision 20050408
+evgpeblk-1016 [06] ev_create_gpe_block   : GPE 00 to 0F [_GPE] 2 regs on int 
0xA
+evgpeblk-1024 [06] ev_create_gpe_block   : Found 7 Wake, Enabled 0 Runtime 
GPEs in this block
 Completing Region/Field/Buffer/Package 
initialization:...
 Initialized 16/16 Regions 0/0 Fields 18/18 Buffers 17/27 Packages (494 nodes)
-Executing all Device _STA and_INI methods:..[ACPI 
Debug] String: [0x24] " AC _STA"
+Executing all Device _STA and_INI methods:..[ACPI 
Debug]  String: [0x24] " AC _STA"
 ...
 49 Devices found containing: 49 _STA, 2 _INI methods
 ACPI: Interpreter enabled
 ACPI: Using IOAPIC for interrupt routing
-nsxfeval-0250 [06] acpi_evaluate_object  : Handle is NULL and Pathname is 
relative
-nsxfeval-0250 [06] acpi_evaluate_object  : Handle is NULL and Pathname is 
relative
-nsxfeval-0250 [06] acpi_evaluate_object  : Handle is NULL and Pathname is 
relative
-nsxfeval-0250 [06] acpi_evaluate_object  : Handle is NULL and Pathname is 
relative
+nsxfeval-0251 [06] acpi_evaluate_object  : Handle is NULL and Pathname is 
relative
+nsxfeval-0251 [06] acpi_evaluate_object  : Handle is NULL and Pathname is 
relative
+nsxfeval-0251 [06] acpi_evaluate_object  : 

2.6.13-rc3 ACPI regression and hang on x86-64

[Mikael Pettersson]

On my x86-64 laptop (Targa Visionary 811: Athlon64 + VIA chipset,
Arima OEM:d HW also sold by eMachines and others), ACPI is broken
and hangs the x86-64 2.6.13-rc3 kernel.

During boot, ACPI reduces the screen's brightness (it's always
done this in the x86-64 kernels but not the i386 ones), so I
have to press a specific key combination (Fn+F8) to increase the
brightness. This worked up to and including the 2.6.13-rc2 kernel,
but with 2.6.13-rc3 it causes an error message:

acpi_ec-0217 [04] acpi_ec_leave_burst_mo: ---status fail

on the console, and then the machine is hung hard.

With the i386 kernel, both this key combination and the other one
for reducing the brightness work as expected.

A diff between the dmesg logs for 2.6.13-rc2 and -rc3 (included below)
indicates that APCI experiences several new errors in rc3.

/Mikael

--- dmesg-2.6.13-rc2-x86_64 2005-07-14 11:59:58.0 +0200
+++ dmesg-2.6.13-rc3-x86_64 2005-07-14 11:59:59.0 +0200
@@ -1,5 +1,5 @@
 Bootdata ok (command line is ro root=/dev/hda7)
-Linux version 2.6.13-rc2 ([EMAIL PROTECTED]) (gcc version 4.0.1) #1 Fri Jul 8 
15:44:53 CEST 2005
+Linux version 2.6.13-rc3 ([EMAIL PROTECTED]) (gcc version 4.0.1) #1 Wed Jul 13 
17:51:48 CEST 2005
 BIOS-provided physical RAM map:
  BIOS-e820:  - 0009f800 (usable)
  BIOS-e820: 0009f800 - 000a (reserved)
@@ -37,46 +37,49 @@
 Initializing CPU#0
 PID hash table entries: 2048 (order: 11, 65536 bytes)
 time.c: Using 1.193182 MHz PIT timer.
-time.c: Detected 1603.693 MHz processor.
+time.c: Detected 1603.705 MHz processor.
 time.c: Using PIT/TSC based timekeeping.
 Console: colour VGA+ 80x25
 Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
 Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
-Memory: 511408k/523200k available (1653k kernel code, 11012k reserved, 941k 
data, 128k init)
-Calibrating delay using timer specific routine.. 3211.68 BogoMIPS 
(lpj=16058428)
+Memory: 511408k/523200k available (1656k kernel code, 11012k reserved, 941k 
data, 128k init)
+Calibrating delay using timer specific routine.. 3211.67 BogoMIPS 
(lpj=16058383)
 Mount-cache hash table entries: 256
 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
 CPU: L2 Cache: 1024K (64 bytes/line)
+mtrr: v2.0 (20020519)
 CPU: Mobile AMD Athlon(tm) 64 Processor 2800+ stepping 0a
- tbxface-0118 [02] acpi_load_tables  : ACPI Tables successfully acquired
+ tbxface-0120 [02] acpi_load_tables  : ACPI Tables successfully acquired
 Parsing all Control 
Methods:
 Table [DSDT](id F005) - 482 Objects with 46 Devices 148 Methods 16 Regions
 Parsing all Control Methods:
 Table [SSDT](id F003) - 3 Objects with 0 Devices 0 Methods 0 Regions
-ACPI Namespace successfully loaded at root 803ac6e0
-evxfevnt-0094 [03] acpi_enable   : Transition to ACPI mode successful
+ACPI Namespace successfully loaded at root 803ad260
+evxfevnt-0096 [03] acpi_enable   : Transition to ACPI mode successful
 Using local APIC timer interrupts.
 Detected 12.528 MHz APIC timer.
 testing NMI watchdog ... OK.
 NET: Registered protocol family 16
+ACPI: bus type pci registered
 PCI: Using configuration type 1
-mtrr: v2.0 (20020519)
-ACPI: Subsystem revision 20050309
-evgpeblk-0979 [06] ev_create_gpe_block   : GPE 00 to 0F [_GPE] 2 regs on int 
0xA
-evgpeblk-0987 [06] ev_create_gpe_block   : Found 7 Wake, Enabled 0 Runtime 
GPEs in this block
+ACPI: Subsystem revision 20050408
+evgpeblk-1016 [06] ev_create_gpe_block   : GPE 00 to 0F [_GPE] 2 regs on int 
0xA
+evgpeblk-1024 [06] ev_create_gpe_block   : Found 7 Wake, Enabled 0 Runtime 
GPEs in this block
 Completing Region/Field/Buffer/Package 
initialization:...
 Initialized 16/16 Regions 0/0 Fields 18/18 Buffers 17/27 Packages (494 nodes)
-Executing all Device _STA and_INI methods:..[ACPI 
Debug] String: [0x24]  AC _STA
+Executing all Device _STA and_INI methods:..[ACPI 
Debug]  String: [0x24]  AC _STA
 ...
 49 Devices found containing: 49 _STA, 2 _INI methods
 ACPI: Interpreter enabled
 ACPI: Using IOAPIC for interrupt routing
-nsxfeval-0250 [06] acpi_evaluate_object  : Handle is NULL and Pathname is 
relative
-nsxfeval-0250 [06] acpi_evaluate_object  : Handle is NULL and Pathname is 
relative
-nsxfeval-0250 [06] acpi_evaluate_object  : Handle is NULL and Pathname is 
relative
-nsxfeval-0250 [06] acpi_evaluate_object  : Handle is NULL and Pathname is 
relative
+nsxfeval-0251 [06] acpi_evaluate_object  : Handle is NULL and Pathname is 
relative
+nsxfeval-0251 [06] acpi_evaluate_object  : Handle is NULL and Pathname is 
relative
+nsxfeval-0251 [06] acpi_evaluate_object  : 

Re: 2.6.13-rc3 ACPI regression and hang on x86-64

[Yu, Luming]

On Thursday 14 July 2005 18:36, Mikael Pettersson wrote:
 On my x86-64 laptop (Targa Visionary 811: Athlon64 + VIA chipset,
 Arima OEM:d HW also sold by eMachines and others), ACPI is broken
 and hangs the x86-64 2.6.13-rc3 kernel.

 During boot, ACPI reduces the screen's brightness (it's always
 done this in the x86-64 kernels but not the i386 ones), so I
 have to press a specific key combination (Fn+F8) to increase the
 brightness. This worked up to and including the 2.6.13-rc2 kernel,
 but with 2.6.13-rc3 it causes an error message:

 acpi_ec-0217 [04] acpi_ec_leave_burst_mo: ---status fail
This message is a warning.


 on the console, and then the machine is hung hard.
If you didn't press that key,   the machine still hung?


 With the i386 kernel, both this key combination and the other one
 for reducing the brightness work as expected.

-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/