Acer Aspire E1-572 doesn't shutdown properly

Bug #1245904 reported by Joshua
44
This bug affects 8 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

When I tell my laptop to shutdown, after moving some dots from left to right, the ubuntu shutdown splash screen freezes and the laptop doesn't turn off.
---
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: joshua 1402 F.... pulseaudio
 /dev/snd/controlC1: joshua 1402 F.... pulseaudio
DistroRelease: Ubuntu 13.10
InstallationDate: Installed on 2013-10-29 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Acer Aspire E1-572
MarkForUpload: True
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=de_DE
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic.efi.signed root=UUID=e85a36d6-60a6-470c-b9fd-dc971e0a3466 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-12-generic N/A
 linux-backports-modules-3.11.0-12-generic N/A
 linux-firmware 1.116
Tags: saucy
Uname: Linux 3.11.0-12-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 05/21/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.04
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: EA50_HW
dmi.board.vendor: Acer
dmi.board.version: V2.04
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.04:bd05/21/2013:svnAcer:pnAspireE1-572:pvrV2.04:rvnAcer:rnEA50_HW:rvrV2.04:cvnAcer:ct10:cvrChassisVersion:
dmi.product.name: Aspire E1-572
dmi.product.version: V2.04
dmi.sys.vendor: Acer

Revision history for this message
Joshua (njj) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected saucy
description: updated
Revision history for this message
Joshua (njj) wrote : BootDmesg.txt

apport information

Revision history for this message
Joshua (njj) wrote : CRDA.txt

apport information

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

apport information

Revision history for this message
Joshua (njj) wrote : IwConfig.txt

apport information

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

apport information

Revision history for this message
Joshua (njj) wrote : Lsusb.txt

apport information

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

apport information

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

apport information

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

apport information

Revision history for this message
Joshua (njj) wrote : RfKill.txt

apport information

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

apport information

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

apport information

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

apport information

Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

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

Did this issue occur in a previous version of Ubuntu, or is this a new issue?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.12 kernel[0].

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.12-rc7-saucy/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Joshua (njj) wrote :

It is a fresh saucy install and I haven't tested any previous version of Ubuntu.

tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Joshua, for regression testing purposes, could you please test Precise via http://releases.ubuntu.com/precise/ and advise if this is reproducible?

tags: added: regression-potential
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Jery Wang (jery-wang2002) wrote :

Acer Aspire V5-573, CPU i5 4200U

Tested with previous ubuntu 13.04 (release): it doesn't shutdown properly. Can't use 13.04 since grahics hardware is not supported Intel HD4400

Tested with latest release ubuntu 13.10 (saucy): it doesn't shutdown properly.

Same observation with OP:
after moving some dots from left to right, the ubuntu shutdown splash screen freezes and the laptop doesn't turn off.

I can add: when it freezes, the fan blows hard.

Revision history for this message
penalvch (penalvch) wrote :

Jery Weng, so your hardware may be tracked, could you please file a new report via a terminal:
ubuntu-bug linux

Revision history for this message
Florian Otti (f-otti) wrote :

I've got the same problem on an Acer Aspire V5-573G

I tested it with Gentoo and Mint too and tried almost every "Grub Parameter" fix.

Can't shutdown but reboot works.

Revision history for this message
penalvch (penalvch) wrote :

Florian Otti, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

Revision history for this message
Joshua (njj) wrote :

I can't test a release prior Saucy because they don't boot at all, the haswell based hardware platform seems to be to new.

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

Joshua, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, please just make a comment to this.

tags: added: latest-bios-v2.04
removed: regression-potential
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Joshua (njj) wrote :

Yes, it does occur on trusty too. Kernel version linux-image (3.12.0.2.4). Ubuntu splash screen freezes on shutdown with one dot orange four dots withe. Fan at full speed.

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

Joshua, do any of the following terminal commands WORKAROUND the problem:
sudo shutdown -P now
sudo halt -f -p

tags: added: trusty
tags: added: unable-to-test-regression
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Joshua (njj) wrote :

No, they don't:

sudo shutdown -P now
- same result as normal shutdown (freeze at the ubuntu splash screen)

sudo halt -f -p
- the screen freezes immediately (while showing unity and the terminalwindow)

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

Joshua, could you please test each of the following and advise if you can shutdown:
sync && reboot -f
sync && poweroff -f

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Joshua (njj) wrote :

The following happens:

sudo sync && sudo reboot -f
- works (But reboot "works" too when issued through the GUI. Using "" because it doesn't behave totaly normal, it shuts down but when turning on again it shows the GRUB shell instead of booting)

sudo sync && sudo poweroff -f
 - the screen freezes immediately (while showing unity and the terminalwindow)

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

Joshua, do either of the following kernel parameters used separately provide a WORKAROUND:
reboot=pci
reboot=bios

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-bug-exists-upstream-v3.12-rc7 needs-upstream-testing
removed: kernel-bug-exists-upstream
Revision history for this message
Tarpoon (tarpoon) wrote :

Hi,

I am having the same issue and just tried out the latest daily from http://cdimage.ubuntu.com/daily-live/current/ as boot from USB.
Sadly the problem persists.
Suspend to Ram, Suspend to Disk and Reboots work fine however.

Tarpoon

Revision history for this message
Tarpoon (tarpoon) wrote :

Thanks for your reply Christopher. I did as you asked: Bug #1257338

Revision history for this message
penalvch (penalvch) wrote :

Joshua, given that the lspci, BIOS are verbatim with Tarpoon's report, the CPU models are distinctly different, but we have more debugging information, I would like to duplicate this report to 1257338. However, if it ends up that the fix for it doesn't work for you, we may unduplicate and resume where we left off.

Thank you for your understanding.

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.