after upgrade to kernell 3.13.0-33 system fails to boot properly

Bug #1355624 reported by Grzegorz Śliwiński
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
High
Unassigned

Bug Description

after today's upgrade to newest kernel (07/12/2014 - kernel 3.13.0-33) system at first bot up, but the loading screen flickered heavily, but booted to normal functioning login screen.
I've turned it off - and the flickering continued on turning off screen as well. Another try resulted in my laptop panic signal. I was able to get only to bios for about 10 minutes - couldn't even boot up to ubuntu live from usb.

Right now I booted to 3.13.0-32 kernel.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-33-generic 3.13.0-33.58
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: fizyk 3413 F.... pulseaudio
CurrentDesktop: Unity
Date: Tue Aug 12 08:24:51 2014
HibernationDevice: RESUME=UUID=e2a0dff4-b17e-4303-94ad-386402a8e361
InstallationDate: Installed on 2012-12-15 (604 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=2aed84f7-44fc-4905-ad15-1202251f8e57 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-32-generic N/A
 linux-backports-modules-3.13.0-32-generic N/A
 linux-firmware 1.127.5
SourcePackage: linux
UpgradeStatus: Upgraded to trusty on 2014-04-23 (110 days ago)
dmi.bios.date: 04/01/2010
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 10LI.M008.20100401.KSJ
dmi.board.name: R510/P510
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr10LI.M008.20100401.KSJ:bd04/01/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR510/P510:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR510/P510:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
dmi.product.name: R510/P510
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

Revision history for this message
Grzegorz Śliwiński (fizyk) wrote :
description: updated
Revision history for this message
Grzegorz Śliwiński (fizyk) wrote :
Revision history for this message
Grzegorz Śliwiński (fizyk) 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
Joseph Salisbury (jsalisbury) wrote :

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

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.11.5-trusty/

Changed in linux (Ubuntu):
importance: Undecided → High
Revision history for this message
Grzegorz Śliwiński (fizyk) wrote :

Thanks for the reply. I'll see how it goes after todays upgrade to 3.13.0-34 first...
Problem with previous errorr is that I rebooted to 0-33 later that day, and well.. problem did not occur again.

Revision history for this message
Grzegorz Śliwiński (fizyk) wrote :

Problem haven't reappeared with the new kernel either.

Revision history for this message
penalvch (penalvch) wrote :

Grzegorz Śliwiński, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1355624/comments/7 regarding this being fixed with an 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.

tags: added: needs-full-computer-model
Changed in linux (Ubuntu):
status: Confirmed → 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.