Acer 1314LC doesn't boot using kernel 2.6.32 and acpi=force option

Bug #580807 reported by piviul
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned
linux-meta (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I have just upgrade my acer 1314LC from 9.10 to 10.04. The upgrade was successfull but now the system hangs on boot. If I choose the previous kernel, the 2.6.31, the system boot correctly but I have no splash screen. If I remove the acpi=force from the kernel options of the new 2.6.32 kernel the system boot correctly but the system doesn't shutdown correctly (I have to press the button to shutdown the system)

Have you any suggest to solve the problem?

Thank you very much

Piviul
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: portatile 1061 F.... pulseaudio
CRDA: Error: [Errno 2] Nessun file o directory
Card0.Amixer.info:
 Card hw:0 'V8235'/'VIA 8235 with Cx20468 at 0xe000, irq 5'
   Mixer name : 'Conexant Cx20468 rev 1'
   Components : 'AC97a:43585429'
   Controls : 30
   Simple ctrls : 19
Card1.Amixer.info:
 Card hw:1 'modem'/'VIA 82XX modem at 0xe100, irq 5'
   Mixer name : 'Conexant Cx20468 rev 1'
   Components : 'AC97m:43585429'
   Controls : 2
   Simple ctrls : 2
Card1.Codecs.codec97.0.mc97.0.0:
 0-0/0: Conexant Cx20468 rev 1

 Extended modem ID: codec=0 LIN1
 Modem status : GPIO
 Line1 rate : 48000Hz
DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=UUID=3c52eadd-5050-400d-b3ae-a9c888e8092e
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Lsusb:
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire 1310
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=ed0b727c-69a2-44f5-bf13-98798385b3d7 ro quiet
ProcEnviron:
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Regression: Yes
RelatedPackageVersions: linux-firmware 1.34
Reproducible: Yes
RfKill:

Tags: lucid kconfig regression-release needs-upstream-testing
Uname: Linux 2.6.32-22-generic i686
UserGroups:

dmi.bios.date: 02/12/0320
dmi.bios.vendor: Insyde Software
dmi.bios.version: 3A19
dmi.board.name: Aspire 1310
dmi.board.vendor: Acer
dmi.board.version: 3A19
dmi.chassis.asset.tag: 12345678
dmi.chassis.type: 8
dmi.chassis.vendor: Acer
dmi.chassis.version: 3A19
dmi.modalias: dmi:bvnInsydeSoftware:bvr3A19:bd02/12/0320:svnAcer:pnAspire1310:pvr3A19:rvnAcer:rnAspire1310:rvr3A19:cvnAcer:ct8:cvr3A19:
dmi.product.name: Aspire 1310
dmi.product.version: 3A19
dmi.sys.vendor: Acer

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi piviul,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/ . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 580807

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. 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. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
piviul (piviul) wrote : AlsaDevices.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
piviul (piviul) wrote : AplayDevices.txt

apport information

Revision history for this message
piviul (piviul) wrote : ArecordDevices.txt

apport information

Revision history for this message
piviul (piviul) wrote : BootDmesg.txt

apport information

Revision history for this message
piviul (piviul) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
piviul (piviul) wrote : Card0.Codecs.codec97.0.ac97.0.0.txt

apport information

Revision history for this message
piviul (piviul) wrote : Card0.Codecs.codec97.0.ac97.0.0.regs.txt

apport information

Revision history for this message
piviul (piviul) wrote : Card1.Amixer.values.txt

apport information

Revision history for this message
piviul (piviul) wrote : Card1.Codecs.codec97.0.mc97.0.0.regs.txt

apport information

Revision history for this message
piviul (piviul) wrote : CurrentDmesg.txt

apport information

Revision history for this message
piviul (piviul) wrote : Lspci.txt

apport information

Revision history for this message
piviul (piviul) wrote : PciMultimedia.txt

apport information

Revision history for this message
piviul (piviul) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
piviul (piviul) wrote : ProcInterrupts.txt

apport information

Revision history for this message
piviul (piviul) wrote : ProcModules.txt

apport information

Revision history for this message
piviul (piviul) wrote : UdevDb.txt

apport information

Revision history for this message
piviul (piviul) wrote : UdevLog.txt

apport information

Revision history for this message
piviul (piviul) wrote : WifiSyslog.txt

apport information

Revision history for this message
piviul (piviul) wrote :

I've just installed linux-image-2.6.33-02063304-generic_2.6.33-02 and now the pc hang on boot writing:
ACPI: BIOS age (320) fails cutoff (2000), acpi=force is required to enable ACPI

If I remove acpi=force from the kernel options the system boot.

So the problem persists even in the latest upstream kernel :((

Have a great day

Piviul

tags: removed: apport-collected kj-triage needs-kernel-logs needs-upstream-testing
piviul (piviul)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in linux (Ubuntu):
status: Confirmed → Triaged
tags: added: kernel-acpi kernel-needs-review
Revision history for this message
piviul (piviul) wrote :

Now kernel 2.6.32-22 freeze even if I remove acpi=force... I've tried tried even the 2.6.32-25 but continue to freeze :(( with or without acpi=force options...

Piviul

Revision history for this message
piviul (piviul) wrote :

I've tried the live of maverick (kernel 2.6.35-22) and without the acpi=off option the kernel hang.
Is my acer acpi bugged? Are the kernels from 2.6.32 not compatibile with my acer? There are some kernel compile parameters that permit my acer to 1310 to shutdown correctly?

Thank you very much

Piviul

PS
The kernel 2.6.35-22 works too with acpi=off option but doesn't shutdown correctly.

Brad Figg (brad-figg)
Changed in linux-meta (Ubuntu):
status: New → Confirmed
Brad Figg (brad-figg)
Changed in linux-meta (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
piviul (piviul) wrote :

Why have you changed the status in invalid? If we spend our time to fill bugs report we would like to have some infos more when you change the bug status...

Any way AFAIK the status is not invalid but resolved: I've installed ubuntu 11.04 and the bug has disappeared

Have a great day

Piviul

Revision history for this message
penalvch (penalvch) wrote :

piviul, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/580807/comments/23 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. Please submit any future bugs you may find.

Changed in linux (Ubuntu):
status: Triaged → Invalid
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.