Black screen of death: system suddenly stopped working soon after upgrade to kernel 3.16.0.34-generic

Bug #1443764 reported by pramathesh ambasta
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I update the kernel images from update-manager this morning on my Ubuntu 14.10 system running on my laptop.

I had started backintime-gnome to take a backup of my home directory on an external seagate drive connected to a 4 port USB hub. This is something I do almost daily

I was editing a desktop shortcut on nano when suddenly I saw a black screen with a lot of dumps and messages from the kernel (or what seemed like the kernel). The screen was frozen - no mouse movement or keyboard movement would restore it. I had to force a restart using the power button.

This is the first time I have encountered something like this.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-34-generic 3.16.0-34.47
ProcVersionSignature: Ubuntu 3.16.0-34.47-generic 3.16.7-ckt8
Uname: Linux 3.16.0-34-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: pramathesh 2166 F.... pulseaudio
 /dev/snd/controlC0: pramathesh 2166 F.... pulseaudio
CurrentDesktop: Unity
Date: Tue Apr 14 10:58:03 2015
HibernationDevice: RESUME=UUID=857060c8-98ed-40ca-8d9e-a1887edd968c
MachineType: Hewlett-Packard HP ProBook 430 G2
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-34-generic root=/dev/mapper/ubuntu--vg-root ro priority=low quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-34-generic N/A
 linux-backports-modules-3.16.0-34-generic N/A
 linux-firmware 1.138.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/07/2014
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: M74 Ver. 01.03
dmi.board.name: 2246
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 67.22
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvrM74Ver.01.03:bd07/07/2014:svnHewlett-Packard:pnHPProBook430G2:pvrA3008CD10003:rvnHewlett-Packard:rn2246:rvrKBCVersion67.22:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ProBook 430 G2
dmi.product.version: A3008CD10003
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
pramathesh ambasta (pramathesh-ambasta) 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
pramathesh ambasta (pramathesh-ambasta) wrote :

It happened again!

I rebooted and I was working with not problems. Then I plugged in my external drive to my 4-port hub and started running backintime-gnome. A few seconds later the BSOD appeared again. It said that there was a kernel panic and an unhandled exception in one of the interrupts. Also some message about usb-ehcd (?).

I hard rebooted again. This time I have attached my external drive to a USB port *on* my laptop. No problem so far!

Could it be due to the 4-port hub then? Maybe!

Please note that the 4-port hub is still attached to the computer and an external keyboard is plugged into it. So I am guessing that attaching the seagate drive to the port creates the problem.

penalvch (penalvch)
tags: added: bios-outdated-1.09
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
importance: Undecided → Low
Revision history for this message
pramathesh ambasta (pramathesh-ambasta) wrote :

Thanks a lot Christopher M. Penalver, especially for the really prompt response

I upgraded the BIOS like you said. And I think it has worked!

After upgrade, I booted up system as normal, plugged in the 4-port USB hub and plugged in the Seagate expansion drive into the hub. I then started backintime for a backup and started doing my work.

It has been nearly 20 minutes since then. Backup has completed without a problem. The system is still alive and kicking.

Thanks once again. Huge relief

penalvch (penalvch)
Changed in linux (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
pramathesh ambasta (pramathesh-ambasta) wrote : Re: [Bug 1443764] Re: Black screen of death: system suddenly stopped working soon after upgrade to kernel 3.16.0.34-generic

Hi

I think we will need to reopen this. Since I experienced the same issue
again just now.

If the report is closed how do I re-open?

Pramathesh
On Tue, 2015-04-14 at 22:34 +0000, Christopher M. Penalver wrote:

> pramathesh ambasta, this bug report is being closed due to your last
> comment
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1443764/comments/5
> regarding this being fixed with a BIOS 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: Incomplete => Invalid
>

Revision history for this message
pramathesh ambasta (pramathesh-ambasta) wrote :

Hi.

the output of the commands

sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

is:

M74 Ver. 01.09
01/26/2015

What was I doing?
****************

I was working on Caligra Flow to create a flow chart.

Backintime was running a backup of my home directory on an external 1 TB Seagate storage drive (USB) connected to my laptop via a 4-port USB hub.

I was moving the mouse to position an object on the flow chart when the black screen of death occurred again.

Please let me know what other information I need to provide.

Revision history for this message
penalvch (penalvch) wrote :

pramathesh ambasta, could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test 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 bug 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-3.XY-rcZ

Where XY and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-3.XY-rcZ

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.

Changed in linux (Ubuntu):
importance: Low → Medium
status: Invalid → Incomplete
tags: added: latest-bios-1.09
removed: bios-outdated-1.09
Revision history for this message
pramathesh ambasta (pramathesh-ambasta) wrote :

Thanks once again. I have installed the latest mainline kernel.

uname -r:

4.0.0-040000-generic

from the link you have provided.

System has booted fine with this kernel.

Testing. Will keep you posted

penalvch (penalvch)
tags: added: needs-crash-log
tags: added: kernel-fixed-upstream kernel-fixed-upstream-4.0.0-040000-generic
Revision history for this message
pramathesh ambasta (pramathesh-ambasta) wrote :

The system is working now. I have been taking backups on the external drive connected to the 4-port hub it since yesterday. The backup (a large one) ran for several hours until late at night without a hitch. Since this morning the system has booted fine and has not shown any sign of crashing.

Thanks to Christophe Penalver for his detailed instructions on how to upgrade the kernel, I upgraded to a mainline kernel. The kernel is linux-kernel-4.0.0-040000-generic.

I am marking the status of this bug as "CONFIRMED".

I have also added the tags as suggested by Christophe.

Thanks once again for all the inputs

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

pramathesh ambasta, the next step is to fully reverse commit bisect from kernel 3.16 to 4.0 in order to identify the last bad commit, followed immediately by the first good one. Once this commit has been identified, then it may be reviewed as a candidate for backporting into your release. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

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

Thank you for your understanding.

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

tags: added: kernel-fixed-upstream-4.0
removed: kernel-fixed-upstream-4.0.0-040000-generic
tags: added: needs-reverse-bisect
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: regression-update
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

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