Also, I have the latest available BIOS on this machine:

BIOS Version: 79ETE1WW (2.21 )

Thomas, does it help to play around with /proc/acpi/debug_{layer,level} for debugging this?  Unfortunately I don't have a ThinkPad which shows this bug.  Otherwise I'd be glad to help to find the culprit...

Just a guess, but can you try with the very latest kernel from here:
ftp://ftp.suse.com/pub/projects/kernel/kotd/HEAD/i386/kernel-default.rpm
(or x86_64, but this is still a i386 machine I expect?)

acpi_root_table=rsdt

Please also attach dmesg output.

I won't be able to look at this further before 11.0 comes out.

very different hardware but same issue #391821 

Thanks for paying attention Daniele.  Let's see if turns out to be the same issue before we're starting to duplicate this or the other report.

Danielle: it would probably be interesting to know if you have the same result for the tests I listed in the summary.

Your bug describes "^@" being inserted into /var/log/acpid -- I don't get anything at all here.

> does it help to play around with /proc/acpi/debug_{layer,level}
Good idea, Timo. Things moved to sys...:

echo 0x21F >/sys/module/acpi/parameters/debug_level
"hit the power button"
echo 0xF >/sys/module/acpi/parameters/debug_level

and then send dmesg output (best cut down to the acpi debug output, could also reveal something important.

Created attachment 216983 [details]
dmesg output when booting KOTD with acpi_root_table option

(In reply to comment #3 from Thomas Renninger)
> Just a guess, but can you try with the very latest kernel from here:
> ftp://ftp.suse.com/pub/projects/kernel/kotd/HEAD/i386/kernel-default.rpm
> (or x86_64, but this is still a i386 machine I expect?)
> 
> acpi_root_table=rsdt
> 
> Please also attach dmesg output.
> 

Attached the dmesg output above, no change in behavior AFAICT.

Created attachment 216985 [details]
dmesg with relevant acpi debug info

evtest /dev/input/event4
Input driver version is 1.0.0
Input device ID: bus 0x19 vendor 0x0 product 0x1 version 0x0
Input device name: "Power Button (CM)"
Supported events:
  Event type 0 (Sync)
  Event type 1 (Key)
    Event code 116 (Power)
Testing ... (interrupt to exit)

"^@" appear when pressing power button.

pre/after changing "debug_level", dmesg show nothing about ACPI when button is
pressed, and again, "^@" in /var/log/message

xev output:

KeyPress event, serial 34, synthetic NO, window 0x4600001,
    root 0x188, subw 0x0, time 3904942, (670,683), root:(675,708),
    state 0x10, keycode 222 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x4600001,
    root 0x188, subw 0x0, time 3904942, (670,683), root:(675,708),
    state 0x10, keycode 222 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

dmesg output is attached to #391821 (there's no differences..)

I'll try KOTD soon...

more info:
installed KOTD, all the same but power button doesn't works _only_ if X is running ! It 's ok under console!

*** Bug 391821 has been marked as a duplicate of this bug. ***

I am using a MacBook and get the following:

running acpi_listen I get the following output with running X:
# acpi_listen
button/power PWRF 00000080 00000008
^@button/power PWRF 00000080 00000009
^@button/power PWRF 00000080 0000000a
^@button/lid LID0 00000080 00000001
button/lid LID0 00000080 00000002
button/lid LID0 00000080 00000003
button/lid LID0 00000080 00000004

xev gives the following:
KeyPress event, serial 31, synthetic NO, window 0x4000001,
    root 0x71, subw 0x4000002, time 10745683, (25,33), root:(30,58),
    state 0x0, keycode 222 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 31, synthetic NO, window 0x4000001,
    root 0x71, subw 0x4000002, time 10745683, (25,33), root:(30,58),
    state 0x0, keycode 222 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

So my problem is like Danieles, but not like James. 
In textmode the powerbutton does initiate a shutdown. Maybe I just have a kpowersave issue? Will look into it...

yeah, it seems a kpowersave bug.. removed kpowersave and now shutdown works!
Call to kde team is needed, I think..

The ^@ appears for me just in konsole. It does not appear in xterm. If I start acpi_listen in xterm in xterm and then in konsole I do not get a "^@" in either place. ;)

I think the duplication of comment #14 is wrong. Daniele and I do get ACPI events for our power buttons there is just no reaction from kpowersave and there are "^@" appearing in acpi_listen.

Therefore I think Daniele and me have a kpowersave bug.

Danny could you please comment. ;)

What do you get if you start 'lshal -m' and press the power button then?

Pressing the powerbutton again and again I get the following:

# lshal -m

Start monitoring devicelist:
-------------------------------------------------
^@16:03:32.217: computer_logicaldev_input condition ButtonPressed = power
16:03:38.670: computer_logicaldev_input condition ButtonPressed = power
^@^@16:03:41.318: computer_logicaldev_input condition ButtonPressed = power
^@16:03:43.509: computer_logicaldev_input condition ButtonPressed = power
^@16:03:44.470: computer_logicaldev_input condition ButtonPressed = power
16:03:45.007: computer_logicaldev_input condition ButtonPressed = power
^@^@16:03:46.142: computer_logicaldev_input condition ButtonPressed = power
^@16:03:46.679: computer_logicaldev_input condition ButtonPressed = power
^@16:03:47.131: computer_logicaldev_input condition ButtonPressed = power
16:03:47.544: computer_logicaldev_input condition ButtonPressed = power

And the problem is now that KPowersave don't react on the button event, or what's the problem?

Please try the latest hal and kpowersave packages from here:
http://download.opensuse.org/repositories/home://dkukawka/openSUSE_11.0

I installed:
kpowersave-0.7.3_svn3163-1.14                 So 27 Jul 2008 17:30:37 CEST
kpowersave-lang-0.7.3_svn3163-1.14            So 27 Jul 2008 17:30:40 CEST
libsmbios2-2.0.2-7.1                          So 27 Jul 2008 17:33:30 CEST
hal-0.5.11-33.2                               So 27 Jul 2008 17:33:36 CEST

did 
# killall kpowersave; kpowersave 
and a rchal restart, but kpowersave still does not react to the powerbutton ...

I am running KDE 4 ...

The "^@" are still there too.

And what did you config on the power button? What should happen?

Hm interesting.

Setting kpowersave to "suspend to ram" on pressing the powerbutton does work.

However setting it to display the "log out menu" or to shut the machine down does nothing it seems.

If all of you use KDE4, then this bug is a duplicate of bug #385312

Yes, kde4.1 for me.
Setting power button to shutdown/logout window, does nothing.
Suspend to disk/RAM: #385312

*** This bug has been marked as a duplicate of bug 385312 ***