System crashes on ac power unless acpi=off, but runs on battery

[Rodrigo S. Ferreira]

Although Feisty runs fine in my Sony Vaio PCG-K115z laptop on ac power or batteries, I can only boot to Gusty if the laptop is running on battery.

If I try to boot with ac power the system crashes some seconds after GDM is loaded. And, if I boot on battery and, after the system is loaded, I plug the ac power, the system crashes instantly.

The only way to boot on ac power (or to plug it after boot on battery and keep the system running) is to set acpi=off in the kernel line. I've tried to check the acpi configs and events triggered by the ac power, but could not find any problem. I've also forced the crash plugging the ac power after system load to check system logs for that second, but nothing is registered.

[Hardy Heron Development]
The same model as above, except for me it does not work even if the laptop is run on battery power. However, running with acpi=off/ noacpi affects useful areas like wireless interface.

Note that in my case GDM is able to load when booting with kernel boot option "acpi=ht".

[Rodrigo S. Ferreira (rsferreira)]

This bug was confirmed in a fresh install of Gusty Release Candidate.
lspci -vv results

[Rodrigo S. Ferreira (rsferreira)]

/var/log/acpid log for crash simulated at 12:24h by plugging ac power.

[Rodrigo S. Ferreira (rsferreira)]

syslog for the simulated crash

[Rodrigo S. Ferreira (rsferreira)]

Looks like this is related to power management. When X starts on ac power, or ac power is activated while on X, the system crashes immediately.

[raananb (raanan)]

On Asus F5V (Intel Core 2 Duo):
Gusty will not boot on battery.
When booted on ac, will crash if power cord is disconnected.

[Henrik Nilsen Omma (henrik)]

This bug was nominated for Gutsy but does currently not qualify for a 7.10 stable release update (SRU) and the nomination is therefore declined.
According the the SRU policy, the fix should already be deployed and tested in the current development version before an update to the stable releases will be considered. With 7.10 now released, that policy applies to this bug. See: https://wiki.ubuntu.com/StableReleaseUpdates .
The bug is not being closed as work will continue on fixing it for the next release, Hardy Heron (8.04). If the state of this bug should change such that it qualifies for the SRU process, please contact the person who originally declined it and ask them to re-evaluate it. To help improve the state of this bug see: https://wiki.ubuntu.com/Bugs/HowToTriage .

[Kjell Braden (afflux)]

Rejecting the gnome-power-manager bug as acpi=off fixes the issue, so it's likely to be a acpi bug. Feel free to re-open the gnome-power-manager task if you think that's correct.
Thanks,

[raananb (raanan)]

Re post by Kjell Braden: not being accustomed to this exchange, I am afraid I do not fully understand what the post says.

If acpi=off is the solution, does it mean that acpi should not be used (?!) If this is what it means, then it can only be accepted as a temporary fix.
If this is an acpi bug, then who is responsible for its solution?

[Kjell Braden (afflux)]

raananb: ACPI seems to be the problem, so if you want to use your device, you *currently* need to use acpi=off (or some other option, see https://wiki.ubuntu.com/DebuggingACPI for details). Indeed, this is only a workaround, a fix is still required. I don't know who is responsible for it, since I'm not adept in ACPI bugs.

[Mskadu (mskadu-deactivatedaccount)]

I can confirm that this is the case for me as well.

[Mskadu (mskadu-deactivatedaccount)]

I am on PCG-K115Z too, running Hardy Heron. Whether I connect AC power or not does not seem to matter.

Results of my ACPI debugging as suggested in the above URL:

- No ACPI-based fan
- None of the kernel boot parameters except "acpi=ht" work for me.

I am trying to put together attachments for this bug report (as suggested in: https://wiki.ubuntu.com/DebuggingACPI). However, when I am trying to "cp -r /proc/acpi /tmp" the process gets stuck at trying to copy /proc/acpi/event. I am in recovery mode when I do this. Any workarounds?

[Mskadu (mskadu-deactivatedaccount)]

I am now awaiting help on getting /proc/acpi

[Christofer Bernander (christoferb)]

Hi!

I am running Hardy Heron on an Acer Travelmate 4502WLMi, and am experiencing similar problems. The system will hang within seconds after Gnome login, unless acpi=off or acpi=ht is specified at boot time. I can run Gutsy with ACPI turned on without any problems.

When copying /proc/acpi in recovery mode, the system will stall completely when reading /proc/acpi/battery/BAT0/alarm (battery must then be removed in order for the computer to be turned off!). It will also stall on /proc/acpi/event, but resumes copying when the power button is pressed.

I have noticed that the path /proc/acpi/battery is not present on Gutsy, which initially made me think that the ACPI battery subsystem was the culprit. However, I have tried blacklisting the 'battery', 'ds2760_battery' and 'sbs' modules (which is confirmed by the path /proc/acpi/battery not showing up), but the system will crash nevertheless.

I have also tried removing the blacklisting for acer_acpi (which has been deprecated in Hardy in favor of acer-laptop) and instead blacklisted acer-laptop, but the problem persists.

[Mskadu (mskadu-deactivatedaccount)]

What's the latest on this then? As of now, I am still pretty much unable to use 8.04 on my laptop. I can also confirm that this problem exists with Fedora 9. I tried installing F9 on it and it wont start GDM until I supply acpi=off?

If there's a bug that's been filed with the ACPI team, can someone supply a link to it so we can track it?

[Christofer Bernander (christoferb)]

It seems to me this issue lies in the linux kernel. Every distro I've tried which uses kernel 2.6.24 or later exhibits the same symptoms. I am running Hardy with a custom DSDT which prohibits the system from locking up; however, the battery monitor seems to work only intermittently, and the CPU frequency scaling does not work at all. I am running Gutsy in parallell, using it when I'm running on battery.

I will probably reinstall the computer with Gutsy, then upgrade to Hardy and run on the old (Gutsy) kernel. I've tried the latest Ibex beta and the issue persists, so I have no real hopes this issue will be resolved (anytime soon).

Should probably learn to roll a custom kernel, but I'm too lazy...

[Mskadu (mskadu-deactivatedaccount)]

Hmm. I am getting fustrated with this. I have simply given up. See:

http://mytechieself.blogspot.com/2008/09/see-you-later-linux.html

- Mayuresh

On Fri, Sep 26, 2008 at 11:53 AM, Christofer Bernander <<email address hidden>
> wrote:

> It seems to me this issue lies in the linux kernel. Every distro I've
> tried which uses kernel 2.6.24 or later exhibits the same symptoms. I am
> running Hardy with a custom DSDT which prohibits the system from locking
> up; however, the battery monitor seems to work only intermittently, and
> the CPU frequency scaling does not work at all. I am running Gutsy in
> parallell, using it when I'm running on battery.
>
> I will probably reinstall the computer with Gutsy, then upgrade to Hardy
> and run on the old (Gutsy) kernel. I've tried the latest Ibex beta and
> the issue persists, so I have no real hopes this issue will be resolved
> (anytime soon).
>
> Should probably learn to roll a custom kernel, but I'm too lazy...
>
> --
> [Gusty/ Heron Development] system crashes on ac power unless acpi=off, but
> runs on battery
> https://bugs.launchpad.net/bugs/148637
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Mayuresh

[Thomas Hotz (thotz-deactivatedaccount)]

Your Ubuntu version is EOL. Can you please tell us if this still happens under a supported Ubuntu version? Thank you!

[raananb (raanan)]

Le 07/10/2012 09:46, Thomas Hotz a écrit :
> Your Ubuntu version is EOL. Can you please tell us if this still happens
> under a supported Ubuntu version? Thank you!
>
> ** Changed in: acpi (Ubuntu)
> Status: Confirmed => Incomplete
>
> ** Summary changed:
>
> - [Gusty/ Heron Development] system crashes on ac power unless acpi=off, but runs on battery
> + ystem crashes on ac power unless acpi=off, but runs on battery
>
> ** Summary changed:
>
> - ystem crashes on ac power unless acpi=off, but runs on battery
> + System crashes on ac power unless acpi=off, but runs on battery
>
Now under 12.04 LTS - the problems are solved: (1) System boots on
battery. (2) When on AC and AC unplugged, system remains operational.