Acer V5-573G shutdown crash

Bug #1249329 reported by Florian Otti
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

Hello,

my Acer Aspire V5-573G crashes at shutdown. With Splash I just see the Ubuntu Logo, then the dots freeze and nothing happens. The screen stays like that and the fan blows harder periodically.
Without splash the last line I see is "Power down" and then it crashes. Everything works until then and it, "sounds" like it shut down (except for the fan of course)
I tried two other Distributions (Mint and Gentoo) and had the exact same problem.
The workarounds with the shutdown command and various kernel parameters didn't work.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-12-generic 3.11.0-12.19 [modified: boot/vmlinuz-3.11.0-12-generic]
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: outtay 1926 F.... pulseaudio
 /dev/snd/controlC1: outtay 1926 F.... pulseaudio
Date: Fri Nov 8 13:14:15 2013
HibernationDevice: RESUME=UUID=b1801ba2-297c-439f-b47a-ba7c54029d21
InstallationDate: Installed on 2013-11-01 (6 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Acer Aspire V5-573G
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=da9bf51d-201a-41b8-a3d2-9bbd47856713 ro quiet acpi_backlight=vendor apm=power_off acpi_os_name=Linux acpi=force acpi_osi=
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
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/30/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.22
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Dazzle_HW
dmi.board.vendor: Acer
dmi.board.version: Type2 - A01 Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.22:bd09/30/2013:svnAcer:pnAspireV5-573G:pvrTBDbyOEM:rvnAcer:rnDazzle_HW:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire V5-573G
dmi.product.version: TBD by OEM
dmi.sys.vendor: Acer

Revision history for this message
Florian Otti (f-otti) wrote :
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
penalvch (penalvch) wrote :

Florian Otti, could you please capture the call trace via https://help.ubuntu.com/community/DebuggingSystemCrash ?

tags: added: latest-bios-v2.22 needs-crash-log needs-upstream-testing
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Florian Otti (f-otti) wrote :

I had my problems capturing it so I'll just copy it, if there's no problem with that:

Broadcast message from root@outtay-ubuntu
                    (unknown) at 15:03 ...

The system is going down for power off NOW
acpid: exiting
speech-dispatcher disabled: edit /etc/default/speech-dispatcher
                                                                                                       *Aksing all remaining processes to terminate....
nm-dispatcher.action: Caught signal 15, shutting down... [OK]

* Killing all remaining processes [fail]
nm-dispatcher.action: Caught signal 15, shutting down...#
* Deactivating swap... [OK]
*Unmounting local filesystems... [OK]
* Will now halt
[ 28.322393] mei_me 0000:00:16.0: stop
[ 28.323601] reboot: Power down

Revision history for this message
penalvch (penalvch) wrote :

Florian Otti, could you please test the latest upstream kernel available (not the daily folder, but the one all the way at the bottom) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

tags: added: regression-potential
Revision history for this message
Florian Otti (f-otti) wrote :

I tested it with the latest Trusty Kernel 3.12.0-031200 and the bug still occurs.
Another thing I just noticed was, that when I try the workaround shutdown command "sudo halt -f -p" the notebook freezes immediately without taking me to the "shutdown screen".
But it seems that with this kernel, the fan doesn't blow hard while the notebook's stuck.

tags: added: kernel-bug-exists-upstream-3.12
removed: needs-upstream-testing
Florian Otti (f-otti)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Florian Otti (f-otti) wrote :

Since this notebook is only two weeks old, I didn't test any prior version of Ubuntu on it.

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

Yep same problem too. So yes it is easily reproducible on precise as well

penalvch (penalvch)
tags: added: precise
Revision history for this message
Florian Otti (f-otti) wrote :

Lucid seems to work! Surprisingly I don't even have the backlight problem with lucid anymore

Revision history for this message
penalvch (penalvch) wrote :

Florian Otti, the next step is to fully commit bisect from Lucid to Precise, in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

tags: added: regression-release
removed: regression-potential
Revision history for this message
Florian Otti (f-otti) wrote :

I'm trying to commit bisect and found out, that my problem is just like in the wiki entry between Maverick and Natty. So that's convenient. The only problem is that in the kernel folders of amd64 (https://launchpad.net/~canonical-kernel-team/+archive/ppa/+build/3322946) there is no "*all.deb" header file.

Revision history for this message
Bjorn Helgaas (bjorn-helgaas) wrote :

Probably the same as this upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=63861

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

Tried the fix on Gentoo and it works! I'm pretty confident, it will work on Ubuntu as well!

Thanks

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.