Bug 6857
| Summary: | poweroff doesn't - A7S333 | ||
|---|---|---|---|
| Product: | ACPI | Reporter: | Icoslau (icoslau) |
| Component: | Power-Off | Assignee: | ykzhao (yakui.zhao) |
| Status: | CLOSED CODE_FIX | ||
| Severity: | normal | CC: | acpi-bugzilla, bunk, dwmw2, eduardo, fdiaza, jeff, protasnb, trasgoescuro |
| Priority: | P2 | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.13 and high | Subsystem: | |
| Regression: | Yes | Bisected commit-id: | |
| Attachments: |
Dmesg
ACPIdump lspci /proc/interrupts lspci /proc/interrupts /var/log/boot.msg log dmesg output of kernel 2.6.24 that fails |
||
|
Description
Icoslau
2006-07-18 09:35:28 UTC
Created attachment 8576 [details]
Dmesg
Created attachment 8577 [details]
ACPIdump
Created attachment 8578 [details]
lspci
Created attachment 8579 [details]
/proc/interrupts
Please add some printk in function acpi_enter_sleep_state to check if acpi_enter_sleep_state works ? Right, but how i can do this? Tks. I think this is a real bug. If i compiling the kernel default of distro, change my processor to Pentium Pro, I have a Atlhon XP 2400+, the machine turns off correctly. If i compiling the kernel, change the processor to Atlhon the problem persist. I think the use of processor to Pentium Pro in kernel slow my machine, but is the only way to "power off" Asus A7S333. Any ideia? Tks cool, you found a compiler related bug. What gcc version you are using? What a surprise! What processor was the distro (SuSE Linux 10.0 and 10.1) compiled for? Please paste the output from gcc -v Please boot the failing and working kernels and disassemble the poweroff routine. We'll be pretty lucky if there is a difference there, but might as well start there... # cd /boot # gdb vmlinux-that-fails /proc/kcore # x/15ai acpi_power_off and do the same when running vmlinux-that-works Please reopen this bug if: - it is still present in kernel 2.6.18 and - you con provide the requested information. i have the same problem, kernel 2.6.18 Created attachment 10534 [details]
lspci
Created attachment 10535 [details]
/proc/interrupts
Created attachment 10536 [details]
/var/log/boot.msg
Created attachment 10537 [details]
log
I use other distros like gnewsense and sabayon, they cant power off my linux too. Does the problem still exists in 2.6.22? ping for update from bug reporter It looks like I can reproduce this with 2.6.22 Any update on this issue please. If someone can reproduce it still, can you provide requested in #9? and please mention the compiler verion too. Thanks. could you please have a test to see if the solution in bug# 6712 helps? At work we have a PC with an A7S333 running Debian Etch, and I can confirm that the bug still happens with kernel 2.6.22 (from backports.org), at least with packages for K7 and 486. I also tried the same kernel version, custom built from the debian sources, but with ACPI_SLEEP unset (as per bug# 6712), without positive results. I don't know if other commenters have seen this symptom, but the computer we have here does not power off when pressing briefly the power button after the "acpi_power_off called" message is displayed, responding only to pressing it for many seconds or unplugging the computer. This bug exists in kernel 2.6.23, the one I'm using. "acpi_power_off called" is the last message I see. In previous kernels I always used apm, but recently it seems to have been removed, meaning I need to press the button to power the PC off. Jeff Muizelaar, Fernando Díaz, Eduardo Bacchi Kienetz: please confirm it still fails with "apm=off" Icoslau and trasgo effectively already did by attaching dmesg: apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac) apm: overridden by ACPI. but we haven't heard from them in a long time -- so you have effectively taken over this bug report with your failure. If it still fails, please attach the complete dmesg -s64000 from the kernel that fails -- preferably a kernel.org kernel. With kernel 2.6.24 (from kernel.org) the PC still doesn't turn off by itself, but now it does respond to pressing (briefly) the power button. Created attachment 14913 [details]
dmesg output of kernel 2.6.24 that fails
I'm sorry Len, I'm unable to test since my desktop computer was left in Brazil and I will be working in Canada for at least 6 months (max a year). As soon as I go back I will test it :| Hi, Eduardo
Will you please try the latest kernel and see whether the problem still exists?
From the acpidump it seems that the S3 object has the same package with the S5 . IMO. It is incorrect. When the system enters the S3 state, the S3 object will be used. When the system is powered off, the S5 object will be used.
> Name (\S_3, Package (0x04)
> {
0x06,
0x00,
0x00,
0x00
})
> Name (\_S5, Package (0x04)
{
> 0x06,
> 0x00,
> 0x00,
0x00
})
I have just tried the 2.6.25-rc9 kernel, and it works. The PC powers off normally. Hi, Fernando
Thanks for the test. It seems that the system can work well.
Is the bios upgraed? If the bios is upgraded, please attach the output of acpidump.
Thanks.
No, the only modification done to the computer is the kernel change, from 2.6.24 (which didn't power off, but at least didn't block the power button as the 2.6.18) to 2.6.25-rc9. Do you need the output of acpidump anyway? It is unnecessary to attach the output of acpidump again. Since the latest kernel(2.6.25-rc9) can make your laptop work well, the bug will be closed. > I have just tried the 2.6.25-rc9, and it works.
> The PC powers off normally.
thanks for testing.
report closed.
|