White Screen Black Screen Crash after Upgrade to Linux version 4.4.0-47-generic

Bug #1644022 reported by Piraten-Kris Pseudonym
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
High
Unassigned
Xenial
Invalid
High
Unassigned

Bug Description

This Bug is about Linux version 4.4.0-47-generic,
NOT about Linux version 4.4.0-45-generic, which worked, so i could file this Bug-Report:
> Terminal > ubuntu-bug linux
(So there may appear the wrong Kernel-Version in the automatic Data)
---
Description:
After (in German: )> Aktualisierungsverwaltung > "Teilweise Systemaktualisierung" the System upgraded to Linux version 4.4.0-47-generic. Booting with this Kernel leads to a Screen with a brown and white Oval getting smaller within the black Frame. The System is totally crashed, CTRL+ALT+F2 does not work. I reproduced this Error.
---
When i boot with Grub-2: "Erweiterte Optionen für Ubuntu" and chose one Kernel-Version down:
"Ubuntu, mit Linux 4.4.0-45-generic" my System starts normally.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-45-generic 4.4.0-45.66
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: admin-user 1558 F.... pulseaudio
CurrentDesktop: Unity
Date: Tue Nov 22 22:21:18 2016
HibernationDevice: RESUME=UUID=dd015f17-7b6c-4dfb-ac57-823edbd74f8c
InstallationDate: Installed on 2015-04-13 (588 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
MachineType: Sony Corporation VGN-CR42S_P
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic root=UUID=fef1de2d-e465-46d6-8613-fbba6a7601d4 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-45-generic N/A
 linux-backports-modules-4.4.0-45-generic N/A
 linux-firmware 1.157.5
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/27/2008
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: R3040Q0
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR3040Q0:bd02/27/2008:svnSonyCorporation:pnVGN-CR42S_P:pvrC102JR5R:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VGN-CR42S_P
dmi.product.version: C102JR5R
dmi.sys.vendor: Sony Corporation

Revision history for this message
Piraten-Kris Pseudonym (piraten-kris) 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
Piraten-Kris Pseudonym (piraten-kris) wrote :

Further Info about System-History (Just in Case it may be relevant)
- Fresh Install Ubuntu-14.04-LTS on HP-655
- Upgrade to Ubuntu-16.04-LTS on HP-655
- Changed Hardware: Sony VAIO VGN-CR42S-P
- Boot of old HDD Attached to USB-Sata as External-USB-HDD
=> System started normally
> Update/Upgrade > Restart
=> Crash Blank-Black-White-Screen (with Standard-Kernel Linux 4.4.0-47-generic)
> Grub-2-Boot: "Ubuntu, mit Linux 4.4.0-45-generic"
=> System starts normally
> Update/Upgrade "Aktualisierungsverwaltung" => Up-to-Date
> Update/Upgrade "Ubuntu-Software" (Gnome) => Up-to Date
> sudo apt-get update && sudo apt-get dist-upgrade => some Changes
> Reboot (without any different Boot-Options) (with Standard-Kernel Linux 4.4.0-47-generic)
=> Crash Blank-Black-White-Screen

Revision history for this message
Piraten-Kris Pseudonym (piraten-kris) wrote :

Further Info about System-History (Just in Case it may be relevant):
The Changed Hardware: Sony VAIO VGN-CR42S-P
has some Partitions with Windows-Vista and Xubuntu-16.04 on the internal HDD (sda), but this was not mounted. But when Grub-2 was automatically updated, it added all Entries found on the internal HDD (sda) to the Grub-2-Menu on the external USB-HDD (sdb).

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

I'd like to perform a bisect to figure out what commit caused this regression. We need to identify the earliest kernel where the issue started happening as well as the latest kernel that did not have this issue.

Can you test the following kernels and report back? We are looking for the first kernel version that exhibits this bug:

4.4.21: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.21
4.4.22: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.22
4.4.23: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.23
4.4.24: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.24

You don't have to test every kernel, just up until the kernel that first has this bug.

Thanks in advance!

Changed in linux (Ubuntu):
importance: Undecided → High
tags: added: performing-bisect regression-update
Changed in linux (Ubuntu Xenial):
importance: Undecided → High
status: New → Incomplete
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Piraten-Kris Pseudonym (piraten-kris) wrote :

I already did the Following, which resolved the Error:

> Boot Ubuntu-16.04 from external USB-HDD (sdb) => Grub-2
> "Erweiterte Optionen für Ubuntu" > "Ubuntu, mit Linux 4.4.0-45-generic"
=> System starts normally
> Terminal >
sudo apt --purge autoremove
sudo apt autoremove
sudo apt autoclean
sudo apt clean
sudo apt update
sudo apt-get check
sudo apt upgrade
sudo apt full-upgrade
> Restart (normal automatic Options)
=> OK => System starts without Error on Kernel: Linux version 4.4.0-47-generic
> I also tried > Shutdown > Power-Off > Start
=> OK

So, i guess, the Error must have been somewhere else, but not in the Linux-Kernel.

Revision history for this message
Piraten-Kris Pseudonym (piraten-kris) wrote :

But if it will be useful for you even so, i will try to test these Kernels on my System, if you can give me detailed Step-for-Step-Instructions, how to install, test and uninstall them later.
(I have no experience in doing that :-))

Revision history for this message
Piraten-Kris Pseudonym (piraten-kris) wrote :

Because the Problem was resolved under the same Kernel, i think it was *not* a Bug in the Linux-Kernel. As no contrary Answer followed, i closed as invalid.

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