Ubuntu
linux package

Lenovo G50-30 laptop does not start after rebooting

Bug #1633681 reported by lumiza on 2016-10-15

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Expired	Medium	Unassigned

Bug Description

It happens everytime when I reset my laptop:
1. when I push "Reset" button in Ubuntu UI
2. when I execute command via Terminal

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-22-generic 4.8.0-22.24 [modified: boot/vmlinuz-4.8.0-22-generic]
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/pcmC0D0p: lumiza 2276 F...m pulseaudio
/dev/snd/controlC0: lumiza 2276 F.... pulseaudio
CurrentDesktop: Unity
Date: Sat Oct 15 09:53:54 2016
HibernationDevice: RESUME=UUID=98efa76d-932e-4955-9879-0d96cd54fa0d
InstallationDate: Installed on 2016-10-15 (0 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: LENOVO 80G0
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic root=UUID=bc69e5fe-e021-4aa8-a6c4-9832aff639a0 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.8.0-22-generic N/A
linux-backports-modules-4.8.0-22-generic N/A
linux-firmware 1.161
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/03/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: A7CN48WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Lancer 5A6
dmi.board.vendor: LENOVO
dmi.board.version: NANANANANO DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo G50-30
dmi.modalias: dmi:bvnLENOVO:bvrA7CN48WW:bd08/03/2015:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30:
dmi.product.name: 80G0
dmi.product.version: Lenovo G50-30
dmi.sys.vendor: LENOVO

Tags:

Revision history for this message

lumiza (lumiza) wrote on 2016-10-15:

AlsaInfo.txt Edit (24.7 KiB, text/plain; charset="utf-8")
CRDA.txt Edit (264 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (57.3 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (3.2 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (508 bytes, text/plain; charset="utf-8")
JournalErrors.txt Edit (15.8 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (9.9 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (412 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (3.7 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (109 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (2.3 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (6.8 KiB, text/plain; charset="utf-8")
PulseList.txt Edit (25.1 KiB, text/plain; charset="utf-8")
RfKill.txt Edit (248 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (159.6 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (101.9 KiB, text/plain; charset="utf-8")

Revision history for this message

Brad Figg (brad-figg) wrote on 2016-10-15: Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

penalvch (penalvch) wrote on 2016-10-16:

lumiza, thank you for reporting this and helping make Ubuntu better.

In order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

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.

Also, you don't need to apport-collect further unless specifically requested to do so.

It is most helpful that after testing of the latest upstream kernel is complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test the latest mainline kernel as it becomes available.

Thank you for your help.