[Acer Aspire ES1-411] Ubuntu freezes occasionally

[Dennis J. Naranjo]

Last time I was only viewing a Youtube video using Firefox and it freezes. Similar report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509723

WORKAROUND: Use kernel parameter:
intel_idle.max_cstate=1

The following sequence doesn't work, I have to power down manually:
1. ALT + F2, type xkill + ENTER.
2. Press Alt+Ctrl+F1.
3. While holding Alt and the SysReq (Print Screen) keys, type REISUB.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-24-generic 4.4.0-24.43
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: dnaranjor 1503 F.... pulseaudio
CurrentDesktop: Unity
Date: Thu Jun 16 09:00:34 2016
HibernationDevice: RESUME=UUID=5023d49a-acd1-475f-8593-d3da289e4859
InstallationDate: Installed on 2016-06-02 (13 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Acer Aspire ES1-411
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic root=UUID=e6ddc4d0-aaa8-4e28-9d68-6b37358246b6 ro quiet splash reboot=pci vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-24-generic N/A
 linux-backports-modules-4.4.0-24-generic N/A
 linux-firmware 1.157
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/10/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.08
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: EA42_BM
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.:bvrV1.08:bd12/10/2014:svnAcer:pnAspireES1-411:pvrV1.08:rvnAcer:rnEA42_BM:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire ES1-411
dmi.product.version: V1.08
dmi.sys.vendor: Acer

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.7-rc1 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'.

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/v4.7-rc3-yakkety/

[Dennis J. Naranjo (dnaranjor)]

@ Joseph Salisbury:

I am able to test the latest upstream kernel, but I'm concerned about if the following is applicable in my current scenario:

========================================
Preparing to install an upstream kernel

First, if one is using select proprietary or out-of-tree modules (ex. vitualbox, nvidia, fglrx, bcmwl, etc.) unless there is an extra package available for the version you are testing, you will need to uninstall the module first, in order to test the mainline kernel. If you do not uninstall these modules first, then the upstream kernel more than likely will not boot.
========================================

I'm using manually installed proprietary drivers for my WiFi card (attached screenshot), since this is the only way I can connect to the Internet at this time.

Do you think is it possible not to uninstall this drivers first?

[Dennis J. Naranjo (dnaranjor)]

I could not wait for advise any longer and decided to perform the Kernel upgrade. Sadly it finished with errors.

Here are the results:

===============================================================================
dnaranjor@maggie:~/Desktop$ sudo dpkg -i *.deb
(Reading database ... 270832 files and directories currently installed.)
Preparing to unpack linux-headers-4.7.0-040700rc1-generic_4.7.0-040700rc1.201606100619_amd64.deb ...
Unpacking linux-headers-4.7.0-040700rc1-generic (4.7.0-040700rc1.201606100619) over (4.7.0-040700rc1.201606100619) ...
Preparing to unpack linux-image-4.7.0-040700rc1-generic_4.7.0-040700rc1.201606100619_amd64.deb ...
Examining /etc/kernel/preinst.d/
run-parts: executing /etc/kernel/preinst.d/intel-microcode 4.7.0-040700rc1-generic /boot/vmlinuz-4.7.0-040700rc1-generic
Done.
Unpacking linux-image-4.7.0-040700rc1-generic (4.7.0-040700rc1.201606100619) over (4.7.0-040700rc1.201606100619) ...
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.7.0-040700rc1-generic /boot/vmlinuz-4.7.0-040700rc1-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.7.0-040700rc1-generic /boot/vmlinuz-4.7.0-040700rc1-generic
dpkg: dependency problems prevent configuration of linux-headers-4.7.0-040700rc1-generic:
 linux-headers-4.7.0-040700rc1-generic depends on linux-headers-4.7.0-040700rc1; however:
  Package linux-headers-4.7.0-040700rc1 is not installed.

dpkg: error processing package linux-headers-4.7.0-040700rc1-generic (--install):
 dependency problems - leaving unconfigured
Setting up linux-image-4.7.0-040700rc1-generic (4.7.0-040700rc1.201606100619) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Not updating initrd symbolic links since we are being updated/reinstalled
(4.7.0-040700rc1.201606100619 was configured last, according to dpkg)
Not updating image symbolic links since we are being updated/reinstalled
(4.7.0-040700rc1.201606100619 was configured last, according to dpkg)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.7.0-040700rc1-generic /boot/vmlinuz-4.7.0-040700rc1-generic
run-parts: executing /etc/kernel/postinst.d/dkms 4.7.0-040700rc1-generic /boot/vmlinuz-4.7.0-040700rc1-generic
ERROR (dkms apport): kernel package linux-headers-4.7.0-040700rc1-generic is not supported
Error! Bad return status for module build on kernel: 4.7.0-040700rc1-generic (x86_64)
Consult /var/lib/dkms/broadcom-sta/6.30.223.271/build/make.log for more information.
ERROR (dkms apport): kernel package linux-headers-4.7.0-040700rc1-generic is not supported
Error! Bad return status for module build on kernel: 4.7.0-040700rc1-generic (x86_64)
Consult /var/lib/dkms/wireless-bcm43142/6.20.55.19/build/make.log for more information.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.7.0-040700rc1-generic /boot/vmlinuz-4.7.0-040700rc1-generic
update-initramfs: Generating /boot/initrd.img-4.7.0-040700rc1-generic
W: Possible missing firmware /lib/firmware/i915/skl_guc_ver6.bin for module i915
run-parts: executing /etc/kernel/postinst.d/pm-utils 4.7.0-040700rc1-generic /boot/vmlinuz-4.7.0-040700rc1-gener...

[Dennis J. Naranjo (dnaranjor)]

@ Joseph Salisbury:

As expected due to the results during Kernel install, the machine booted OK but without Wifi. So, it is not possible for me at this time to perform any further tests with 4.7.0-040700rc1-generic.

Now I'm back to the old 4.4.0-24, and just applied the following workaround:

==================================
1. sudo nano /etc/default/grub
2. There is a line in that: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" (like this), replace with: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_idle.max_cstate=1"
Save it (CTRL+O)
3. sudo update-grub
4. sudo reboot
==================================

I'll be back with the results in a couple of day, or maybe sooner if it freezes again.

[Dennis J. Naranjo (dnaranjor)]

Until now, the machine has stabilized its behaviour and no longer freezes after the workaround applied.

Sadly, the suspend and shutdown functions remain in trouble, since when the laptop lid is closed it remains turned on and unresponsive; and when the equipment is instructed to shutdown, it keeps in an infinite loop trying to power down without success.

In both cases, a hard shut down (a.k.a. keep pressing power button until turned off) is needed.

[penalvch (penalvch)]

Dennis J. Naranjo, to see if this addressed upstream, could you please test the latest mainline kernel (4.7-rc5) and advise to the results?

If this is still reproducible, please then test drm-intel-nightly.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]