Blank screen on Aspire one when less than 22% (9 cells) battery

Bug #1041058 reported by Yann Le Doaré
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

After changing my 3 cell battery with 9 cell one, i have this bug :

- when battery is less than 22% charged, there is a blank screen
- restarting into BIOS setup is OK (I can stay a long time)
- restarting with "acpi=off noacpi" option is OK (I can use my comptuter more than an hour)
- restarting without options makes blank screen after one or two minutes.

I think it is an ACPI bug, but how can I do to resolve it ?

Note : I Tried other kernels (3.0, 2.6) and other distros witout success.
---
AcpiTables:

AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu12
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: yann 1267 F.... pulseaudio
CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0x38540000 irq 17'
   Mixer name : 'Realtek ALC268'
   Components : 'HDA:10ec0268,1025015b,00100101'
   Controls : 16
   Simple ctrls : 9
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=0bd71121-4200-4289-b9a6-3e8a54d64747
InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Release i386 (20120423)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Acer AOA110
Package: linux (not installed)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic noacpi acpi=off root=UUID=bb955952-6181-4087-91e7-636f0f1a12c1 ro quiet splash
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-29-generic N/A
 linux-backports-modules-3.2.0-29-generic N/A
 linux-firmware 1.79
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: precise
Uname: Linux 3.2.0-29-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
dmi.bios.date: 10/06/2008
dmi.bios.vendor: Acer
dmi.bios.version: v0.3310
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAcer:bvrv0.3310:bd10/06/2008:svnAcer:pnAOA110:pvr1:rvnAcer:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
dmi.product.name: AOA110
dmi.product.version: 1
dmi.sys.vendor: Acer

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1041058

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Yann Le Doaré (yann-h) wrote : AlsaDevices.txt

apport information

tags: added: apport-collected precise
description: updated
Revision history for this message
Yann Le Doaré (yann-h) wrote : BootDmesg.txt

apport information

Revision history for this message
Yann Le Doaré (yann-h) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
Yann Le Doaré (yann-h) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
Yann Le Doaré (yann-h) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Yann Le Doaré (yann-h) wrote : IwConfig.txt

apport information

Revision history for this message
Yann Le Doaré (yann-h) wrote : Lspci.txt

apport information

Revision history for this message
Yann Le Doaré (yann-h) wrote : PciMultimedia.txt

apport information

Revision history for this message
Yann Le Doaré (yann-h) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Yann Le Doaré (yann-h) wrote : ProcEnviron.txt

apport information

Revision history for this message
Yann Le Doaré (yann-h) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Yann Le Doaré (yann-h) wrote : ProcModules.txt

apport information

Revision history for this message
Yann Le Doaré (yann-h) wrote : PulseList.txt

apport information

Revision history for this message
Yann Le Doaré (yann-h) wrote : UdevDb.txt

apport information

Revision history for this message
Yann Le Doaré (yann-h) wrote : UdevLog.txt

apport information

Revision history for this message
Yann Le Doaré (yann-h) wrote : WifiSyslog.txt

apport information

Revision history for this message
Yann Le Doaré (yann-h) wrote :

Note : Acpi was disabled (noacpi acpi=off) when sending data

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.6 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. Please only remove that one tag and leave the other tags. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-rc3-quantal/

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: needs-upstream-testing
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Yann Le Doaré (yann-h) wrote :

Bug confirmed with 3.6.0-030600rc3-generic kernel

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-bug-exists-upstream
removed: needs-upstream-testing
Revision history for this message
Yann Le Doaré (yann-h) wrote :

In the past, I debuged linux kernel with serial console, nowdays (my aspire one has not serial port) what is the way to try to debug kernel errors ?

Revision history for this message
sm8ps (sm8ps) wrote :

In the hope that the following remarks be helpful: I use an Acer Aspire One 150 with Ubuntu 12.04. I sometimes use a 9-cell battery (11Ah) which used to give me about 10 hours of independence under Ubuntu 10.04. The 3-cell gives me about two hours now on Ubuntu 12.04.

The other day, I hibernated the machine and exchanged the 3-cell with a 9-cell battery (11Ah), intending to get a full day of battery life thereafter. The 3-cell battery had been at a little less than 50%, the 9-cell had been fully charged overnight to 10Ah (90% capacity). For some reason, the battery indicator turned red after less than two hours and soon afterwards the system had to be shut down and could not be revived on that battery.

Today, I needed to do the same but abstained from hiberating the machine and turned it off instead before switching batteries. Nevertheless the battery indicator went down and indicated only 1:30 remaining after less than two hours of usage which cannot be the case.

I was prepared to switch to paper and pencil or bow and arrow or whatever I would find when oll of a sudden the battery indicator jumped back up to 57% with a remaining time of more than 4:30. I captured the screen of the battery statistics showing the time until discharged over the last three hours. This is all with one and the same 9-cell battery.

Soo, what is the deal here? For some reason, the change of battery did not get registered even during the first two hours of usage but only afterwards. I could not tell what triggered it. (Indeed I would know how to trigger a refreshing of that information. -- I did close the lid which only shuts off the screen, come to think of it. I am going to try that next time and see what it does!)

Revision history for this message
Yann Le Doaré (yann-h) wrote :

I installed Windows XP on this comptuter -> same problem !

You can close this bug, which must be an hardware one.

Thanks

Changed in linux (Ubuntu):
status: Confirmed → Fix Released
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.