gutsy: system freezes in battery mode

Bug #127522 reported by Philipp Ehses
4
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Binary package hint: kubuntu-desktop

I'm running kubuntu gutsy with the latest update and kernel (2.6.22-8-generic) on an Samsung X20 V (pentium M, 1.6 GHz, intel 915gm chipset & graphics)

Since some recent updates my system freezes while running on battery. It seems that the hard disk doesn't come out of standby mode but I'm not sure. Connecting it to the power socket again seems to wake up the hard disk but doesn't help with the freeze. Only a reboot helps.

There is already bug #123463 which may be related. It is only reported for xfce, tough.

Revision history for this message
Matheus Pacheco de Andrade (matheusp-andrade-deactivatedaccount) wrote :

I can confirm this behaviour partially.
Except for mine, connecting the power chord brings back the system normally.
Also, if I press "Silent Mode" button, I goes back to a functioning system.

I run Ubuntu Gutsy with all current upgrades. Gnome, by the way, so it is not Kubuntu-related.

Revision history for this message
Scott Kitterman (kitterman) wrote :

Reassigning to the kernel as it sounds acpi related.

Revision history for this message
Matheus Pacheco de Andrade (matheusp-andrade-deactivatedaccount) wrote :

Some info regarding this behaviour on my laptop:
1. It happens every time I unplug the power chord;
2. It unfreezes normally upon replugging the power chord or disabling "Silent Mode" (a button with the drawing of a fan that should modulate cpu voltage thus diminishing the need for the fan);
3. It also happens on tty1 when I '/etc/init.d/gdm stop';
4. When it 'comes back' it empties the keyboard buffer on the console, ie: shows the keys I pressed during the freeze;
5. It is undefinite, meaning that it doesn't come back until battery runs out;
6. It *doesn't* happen when I boot into safe mode (second Grub option);
6a. If I call startx from safe mode it also doesn't happen.

I will post my dmesg, lspci -vnn, /var/log/apcid and the isolated events events on /var/log/apcid next.

Revision history for this message
Matheus Pacheco de Andrade (matheusp-andrade-deactivatedaccount) wrote :

My dmesg

Revision history for this message
Matheus Pacheco de Andrade (matheusp-andrade-deactivatedaccount) wrote :

lspci -vnn

Revision history for this message
Matheus Pacheco de Andrade (matheusp-andrade-deactivatedaccount) wrote :

Full /var/log/acpid

Revision history for this message
Matheus Pacheco de Andrade (matheusp-andrade-deactivatedaccount) wrote :

/var/log/acpid separated by events.

Revision history for this message
Matheus Pacheco de Andrade (matheusp-andrade-deactivatedaccount) wrote :

One more thing: the system only freezes after some time of inativity (I guess that about 1-2 seconds).
It means that it doesn't freeze if, upon disconnecting the power chord, I keep messing around with the mouse/touchpad.

Revision history for this message
Matheus Pacheco de Andrade (matheusp-andrade-deactivatedaccount) wrote :

And as a partial solution for the problem, passing one of the following options to the kernel make the problem go away, but unknown at what cost:
acpi=off
acpi=noirq
noapic

Changed in linux-source-2.6.22:
assignee: nobody → ubuntu-kernel-acpi
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Matheus Pacheco de Andrade (matheusp-andrade-deactivatedaccount) wrote :

Well, noapic no longer works.
And the options that disable acpi render the notebook unusable.

So... The problem goes on...

Revision history for this message
Matheus Pacheco de Andrade (matheusp-andrade-deactivatedaccount) wrote :

I guess you can close this bug now.
Today I tested it with the new Gutsy updates (as of 091107 at 13:07 NY time) and disconnecting the power chord no longer freezes the notebook. Instead it shows some message from power manager as it should be.

Thank you all.

Revision history for this message
Matheus Pacheco de Andrade (matheusp-andrade-deactivatedaccount) wrote : [REGRESSION] It no longer works
Download full text (3.9 KiB)

I can't precise if it was with september 16 or 17 updates but the laptop is freezing again when in battery mode.

Sep. 16 updates:
Commit Log for Sun Sep 16 09:03:12 2007

Foram atualizados os seguntes pacotes:
acpi-support (0.101) to 0.102
genisoimage (9:1.1.6-1ubuntu1) to 9:1.1.6-1ubuntu2
hotkey-setup (0.1-17ubuntu15) to 0.1-17ubuntu18
kcontrol (4:3.5.7-1ubuntu19) to 4:3.5.7-1ubuntu20
kdebase-bin (4:3.5.7-1ubuntu19) to 4:3.5.7-1ubuntu20
kdebase-data (4:3.5.7-1ubuntu19) to 4:3.5.7-1ubuntu20
kicker (4:3.5.7-1ubuntu19) to 4:3.5.7-1ubuntu20
libkonq4 (4:3.5.7-1ubuntu19) to 4:3.5.7-1ubuntu20
wodim (9:1.1.6-1ubuntu1) to 9:1.1.6-1ubuntu2
xserver-xorg-input-wacom (1:0.7.7.7-0ubuntu1) to 1:0.7.7.7-0ubuntu2

Sep. 17 updates:
Commit Log for Mon Sep 17 17:06:29 2007

Foram atualizados os seguntes pacotes:
capplets-data (1:2.19.92-0ubuntu2) to 1:2.19.92-0ubuntu3
f-spot (0.4.0-0ubuntu1) to 0.4.0-0ubuntu2
gconf-editor (2.18.2-0ubuntu1) to 2.19.92-0ubuntu1
genisoimage (9:1.1.6-1ubuntu2) to 9:1.1.6-1ubuntu3
gnome-control-center (1:2.19.92-0ubuntu2) to 1:2.19.92-0ubuntu3
gnome-keyring-manager (2.18.0-2) to 2.19.92-0ubuntu1
gnome-utils (2.19.92-0ubuntu1) to 2.20.0-0ubuntu1
gtk2-engines-pixbuf (2.11.6-1ubuntu4) to 2.12.0-0ubuntu1
kcontrol (4:3.5.7-1ubuntu20) to 4:3.5.7-1ubuntu21
kdebase-bin (4:3.5.7-1ubuntu20) to 4:3.5.7-1ubuntu21
kdebase-data (4:3.5.7-1ubuntu20) to 4:3.5.7-1ubuntu21
kicker (4:3.5.7-1ubuntu20) to 4:3.5.7-1ubuntu21
language-pack-gnome-pt (1:7.10+20070905) to 1:7.10+20070914
language-pack-pt (1:7.10+20070905) to 1:7.10+20070914
libatk1.0-0 (1.19.6-0ubuntu1) to 1.20.0-0ubuntu1
libatk1.0-dev (1.19.6-0ubuntu1) to 1.20.0-0ubuntu1
libgail-common (1.19.6-0ubuntu1) to 1.20.0-0ubuntu1
libgail-dev (1.19.6-0ubuntu1) to 1.20.0-0ubuntu1
libgail18 (1.19.6-0ubuntu1) to 1.20.0-0ubuntu1
libglib2.0-0 (2.14.0-2ubuntu1) to 2.14.1-1ubuntu1
libglib2.0-dev (2.14.0-2ubuntu1) to 2.14.1-1ubuntu1
libglibmm-2.4-1c2a (2.13.9-0ubuntu2) to 2.14.0-0ubuntu1
libgnome-window-settings1 (1:2.19.92-0ubuntu2) to 1:2.19.92-0ubuntu3
libgnome2-0 (2.19.1-0ubuntu2) to 2.20.0-1ubuntu1
libgnome2-common (2.19.1-0ubuntu2) to 2.20.0-1ubuntu1
libgnome2-dev (2.19.1-0ubuntu2) to 2.20.0-1ubuntu1
libgtk2.0-0 (2.11.6-1ubuntu4) to 2.12.0-0ubuntu1
libgtk2.0-bin (2.11.6-1ubuntu4) to 2.12.0-0ubuntu1
libgtk2.0-common (2.11.6-1ubuntu4) to 2.12.0-0ubuntu1
libgtk2.0-dev (2.11.6-1ubuntu4) to 2.12.0-0ubuntu1
libgtop2-7 (2.19.92-0ubuntu1) to 2.20.0-0ubuntu1
libgtop2-common (2.19.92-0ubuntu1) to 2.20.0-0ubuntu1
libkonq4 (4:3.5.7-1ubuntu20) to 4:3.5.7-1ubuntu21
librarian0 (0.5.8-0ubuntu1) to 0.6.0-0ubuntu1
libtotem-plparser7 (2.19.90-0ubuntu3) to 2.20.0-0ubuntu1
linux-headers-2.6.22-11 (2.6.22-11.32) to 2.6.22-11.33
linux-headers-2.6.22-11-generic (2.6.22-11.32) to 2.6.22-11.33
linux-image-2.6.22-11-generic (2.6.22-11.32) to 2.6.22-11.33
linux-libc-dev (2.6.22-11.32) to 2.6.22-11.33
python-gconf (2.19.2-0ubuntu2) to 2.20.0-0ubuntu1
python-glade2 (2.11.0-0ubuntu1) to 2.12.0-0ubuntu1
python-gnome2 (2.19.2-0ubuntu2) to 2.20.0-0ubuntu1
python-gnome2-desktop (2.19.2-0ubuntu4) to 2.20.0-0ubuntu1
python-gnomecanvas (2.19.2-0ubuntu2) to 2.20.0-0ubuntu1
python-gobject (2.13.2-0ubuntu1) to 2.14.0-0ubuntu1
python-gtk2 (2...

Read more...

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Michele Mangili (mangilimic) wrote :

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find.

Changed in linux:
status: Incomplete → Invalid
Curtis Hovey (sinzui)
Changed in linux-source-2.6.22 (Ubuntu):
assignee: Registry Administrators (registry) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.