freeze

Bug #1528880 reported by Harkishan Singh
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
High
Unassigned

Bug Description

it freezes on acer aspire es1 311

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.3.0-2-generic 4.3.0-2.11 [modified: boot/vmlinuz-4.3.0-2-generic]
ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
Uname: Linux 4.3.0-2-generic x86_64
ApportVersion: 2.19.3-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: kishan 1280 F.... pulseaudio
CurrentDesktop: GNOME
Date: Wed Dec 23 23:29:23 2015
HibernationDevice: RESUME=UUID=fc820305-0de5-4c71-9d6f-db63bfd59142
InstallationDate: Installed on 2015-12-21 (2 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151213)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04f2:b469 Chicony Electronics Co., Ltd
 Bus 001 Device 004: ID 04ca:300b Lite-On Technology Corp. Atheros AR3012 Bluetooth
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire ES1-311
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-2-generic.efi.signed root=UUID=8731740f-229c-4571-8986-e59e5e19dc1c ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.3.0-2-generic N/A
 linux-backports-modules-4.3.0-2-generic N/A
 linux-firmware 1.154
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/24/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.10
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Aspire ES1-311
dmi.board.vendor: Acer
dmi.board.version: V1.10
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.10
dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd10/24/2014:svnAcer:pnAspireES1-311:pvrV1.10:rvnAcer:rnAspireES1-311:rvrV1.10:cvnAcer:ct10:cvrV1.10:
dmi.product.name: Aspire ES1-311
dmi.product.version: V1.10
dmi.sys.vendor: Acer

Revision history for this message
Harkishan Singh (kishan9778) 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
Alberto Salvia Novella (es20490446e) wrote :

@ Harkishan Singh

Please:

1. Edit the bug description so it explains when the system freeze.
2. Set this bug status back to confirmed.

Thank you.

Changed in linux (Ubuntu):
importance: Undecided → Critical
importance: Critical → Undecided
status: Confirmed → Incomplete
penalvch (penalvch)
tags: added: bios-outdated-1.17
tags: added: bios-outdated-1.11
removed: bios-outdated-1.17
Changed in linux (Ubuntu):
importance: Undecided → Low
Revision history for this message
Harkishan Singh (kishan9778) wrote :

the output of current sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date ist:
V1.11
10/24/2014

which i believe ist the current one

after updating the BIOS,
out of 2 boots,the laptop crashed once,not much of an improvement i suppose

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

Harkishan Singh, at your earliest convenience, could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue.

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

tags: added: latest-bios-1.11
removed: bios-outdated-1.11
Changed in linux (Ubuntu):
importance: Low → Medium
status: Confirmed → Incomplete
Revision history for this message
Harkishan Singh (kishan9778) wrote :

The mainline kernel did not fix the issue.As i do not know how to add tags:kernel-bug-exists-upstream & kernel-bug-exists-upstream-4.4-rc8,please add those for me.

I have installed the kernel on 15.45 hrs and the system froze around 20.27 hrs,which means that there was an uptime of 5 hours.

another point to note is that i was loading up 3 tabs on chrome,all loading youtube podcasts in 480p.I was watching one of these podcasts when the system froze.

Uninstalling kernel-4.4-rc8 and reverting to kernel 4.3.0.5-generic

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

kernel 4.3.05-generic has the same problem,using kernel 4.1.15-generic without problems now

Revision history for this message
penalvch (penalvch) wrote :

Harkishan Singh, the next step is to fully commit bisect from kernel 4.1 to 4.3 in order to identify the last good kernel commit, followed immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

After the offending commit (not kernel version) has been identified, then please mark this report Status Confirmed.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

tags: added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.4-rc8 needs-bisect regression-release
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Harkishan Singh (kishan9778) wrote :

Sorry,my connection speed is too slow,i could not wait so long to clone the git in the first place,perhaps you can do it,or maybe ask someone else who has the time? Thank you

Revision history for this message
Harkishan Singh (kishan9778) wrote :

or perhaps you can help me to list what commands i have to execute here? i do not wish to read that long manual,i simply have not enough time

Revision history for this message
Harkishan Singh (kishan9778) wrote :

2e2edebefceef201624dcc323a1f7761e0040cf5 is the first bad commit
commit 2e2edebefceef201624dcc323a1f7761e0040cf5
Author: Jani Nikula <email address hidden>
Date: Wed Oct 14 11:29:01 2015 +0300

    Revert "drm/i915: Add primary plane to mask if it's visible"

    This reverts commit 721a09f7393de6c28a07516dccd654c6e995944a.

    There is nothing wrong with the commit per se. We had two versions of
    the commit, one in -next headed for v4.4 and this one for v4.3. Turns
    out we'll need to backport more fixes from -next, and they conflict with
    the v4.3 version. It gets messy. It will be easiest to revert this one,
    and backport all the relevant commits from -next without modifications;
    they apply cleanly after this revert.

    Requested-by: Joseph Yasi <email address hidden>
    References: https://bugs.freedesktop.org/show_bug.cgi?id=91910#c4
    Cc: Maarten Lankhorst <email address hidden>
    Acked-by: Maarten Lankhorst <email address hidden>
    Signed-off-by: Jani Nikula <email address hidden>

:040000 040000 1ac73f0c13e4044254642ab62891431db5414331 22e789206dec0bf4f7a22fbe3326967f3233dbc1 M drivers

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

Harkishan Singh, the issue you are reporting is an upstream one. Could you please report this problem following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing list (TO Jani Nikula, Daniel Vetter, and Maarten Lankhorst CC intel-gfx)?

Please provide a direct URL to your post to the mailing list when it becomes available so that it may be tracked.

Thank you for your understanding.

Changed in linux (Ubuntu):
importance: Medium → High
status: Confirmed → Triaged
Revision history for this message
penalvch (penalvch) wrote :

Harkishan Singh, could you please capture the crash following https://help.ubuntu.com/community/DebuggingSystemCrash ?

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