After upgrading to 4.2.0.30 there's no desktop

[Albert Cutrona]

Hi,

This morning I've updated my Ubuntu 15.10 to kernel 4.2.0.30 and now can't enter to the desktop. In fact, the laptop freezes after grub screen.

If start from the recovery, from "upstart" option I get a message like "upstart: broken pipe". And I enter to "recovery mode" options and after resume with the normal start the desktop loads but only with 1024x768 or 800x600

I've have to start with the previous kernel, the 4.2.0.27. Then all works as expected and I log to my desktop as usual.

Thank you very much.
---
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: albert 2638 F.... pulseaudio
 /dev/snd/controlC1: albert 2638 F.... pulseaudio
DistroRelease: Ubuntu 15.10
HibernationDevice: RESUME=UUID=3ea73c4c-4dc5-4f7f-8c97-d2f477414305
InstallationDate: Installed on 2016-01-20 (34 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Hewlett-Packard HP G62 Notebook PC
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=es_ES
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic root=UUID=e34b1243-4d35-4e1d-ab47-19304b7c369b ro recovery nomodeset
ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-30-generic N/A
 linux-backports-modules-4.2.0-30-generic N/A
 linux-firmware 1.149.3
Tags: wily
UdevLog: Error: [Errno 2] No existe el archivo o el directorio: '/var/log/udev'
Uname: Linux 4.2.0-30-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 03/15/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.29
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 143C
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 62.3D
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.29:bd03/15/2011:svnHewlett-Packard:pnHPG62NotebookPC:pvr0594110000252710001020100:rvnHewlett-Packard:rn143C:rvr62.3D:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP G62 Notebook PC
dmi.product.version: 0594110000252710001020100
dmi.sys.vendor: Hewlett-Packard

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1548867

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Albert Cutrona (acutbal)]

apport information

[Albert Cutrona (acutbal)]

apport information

[Albert Cutrona (acutbal)]

apport information

[Albert Cutrona (acutbal)]

apport information

[Albert Cutrona (acutbal)]

apport information

[Albert Cutrona (acutbal)]

apport information

[Albert Cutrona (acutbal)]

apport information

[Albert Cutrona (acutbal)]

apport information

[Albert Cutrona (acutbal)]

apport information

[Albert Cutrona (acutbal)]

apport information

[Albert Cutrona (acutbal)]

apport information

[Albert Cutrona (acutbal)]

apport information

[Albert Cutrona (acutbal)]

apport information

[Albert Cutrona (acutbal)]

Hi,

As you suggested I've ran "apport-collect 1548867" command, a popup appeared recollecting info and sended it. I suppose you will receive the info. Just in case, is it possible to retrieve this log and attach here?

Thank you very much.

[Joseph Salisbury (jsalisbury)]

I'd like to perform a kernel bisect to figure out which commit caused this regression. We need to identify the earliest kernel that did not exhibit the bug and the first kernel that did exhibit the bug.

Can you test the following kernels and post back?

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2.8-ckt1-wily/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2.8-ckt2-wily/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2.8-ckt3-wily/

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

Thanks in advance!

[Dirk Porezag (dirk-porezag)]

Same issue here. My system is "just" a Xubuntu 15.10 VM running in VMware Player that I use for testing purposes. Everything fine w/ kernel 4.2.0-27 bus issue occurs with 4.2.30. System will boot kernel 4.2.0-30 without graphics but freezes when starting X. I'll attach the two Xorg log files:

Xorg.log.0 - working w/ kernel 4.2.0-27
Xorg.log.0.old - freeze w/kernel 4.2.0-30

Maybe comparing the two X startup logs will provide some extra info.
I'm happy to support debugging later on w/ bisecting etc. but need to get some beauty rest now ;-).

[Aoxo (stonedavenger)]

Yikes, I thought I broke my VMware VM!
I've never had to revert to an older kernel before, but I'm glad I had them still.
I removed 4.2.0-30 and I'm booting normally again.

[Taihwan Hah (hah)]

I'd got same issue, But after upgrade (apt-get upgrade, Feb 27) probs had gone.
Now, 4.2.0.-30 works fine.

[Albert Cutrona (acutbal)]

The last update 4.2.0.36 doesn't fix my issue, still have to use 4.2.0.27 to enter my desktop.

@jsalisbury suggested to test some kernel but I'm noob dealing with this kind of stuff. Please, could someone tell me how to test a kernel?

Thank you very much!! :)

[Daniel Jowett (daniel-jowettenterprises)]

I removed the duplicate status of this bug - as the OP's issue does not appear to be related to VMWare. @acutbal can you confirm?

1548587 is a bug related to VMWare - I posted "Me too" on that, but was told (along with others - see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1548587/comments/45) to raise another bug for non-VMWare issue. ( @dirk-porezag you are probably more interested in that bug.)

But actually I found that my experience is the same issue as reported here. My experience being...

"I also have trouble with the 4.2.0-30 kernel directly on my laptop.
- it freezes about 40 seconds after login screen (whether I login or not), I can only work around this by using 4.2.0-27 kernel."

Others who seem to have a "non-WMWare issue" from bug 1548587, would you like to confirm? @marwir @amaguran @nicocarbone

[Albert Cutrona (acutbal)]

Yes, I confirm that my issue isn't related with WMWare software, I never installed nor used it.

Thanks and best regards!!

[Marco van Zwetselaar (zwets)]

Confirming this bug: up to date plain vanilla 15.10, not on VMWare. Kernel 4.2.0-27 was and is fine. Kernel 4.2.0-30:
- hangs after typing password in graphical login, no response to keyboard or mouse (haven't checked ssh, but machine seems to be still alive)
-can login on text console via Ctl-Alt-F1 on graphical login, but hangs when returning to graphical screen with Alt-F7.

[Marcin (marsprivate+web)]

I have marked my Bug #1548867 as a duplicate of this. I also experience the same issue.
If I performed kernel bisect right the last working version was ckt2.

[sunweb (sunweb)]

I also have the same bug on a notebook with Kbubutnu 14.04.4.
Intel and AMD graphics. I can't even boot properly.
"gpu-manager blocked for more than 120 seconds" After this message appears in console even tty1 won't work. Using 4.2.0-27 boots fine.

[Joseph Salisbury (jsalisbury)]

@Marcin and anyone else that tested the kernels from comment #17. Just to confirm v4.2.8-ckt2 works, but v4.2.8-ckt3 does not?

[Marcin (marsprivate+web)]

@jsalisbury
Yes. v4.2.8-ckt2 works. And on v4.2.8-ckt3 it's stuck on a black screen with a prompt. That looks the same just like in other linked versons.
Something like:
"fsck from util-linux [...]
/dev/sda6: clean [...]
[...] kvm: disabled by bios"

[dmylnikov (altsiona)]

I have Ubuntu 15.10 and Intel/AMD hybrid graphics. With 4.2.0.30-36 kernel I'm able to boot into graphical mode if I set "Graphic mode=Discrete" in BIOS. But GUI fails to start with BIOS option "Graphic mode=Switchable". Last boot messages are:

(1 of 2) A start job is running for Detect the available GPUs and deal with any system changes
(2 of 2) A start job is running for Wait for Plymouth Boot Screen to Quit

[Joseph Salisbury (jsalisbury)]

I started a kernel bisect between v4.2.8-ckt2 and v4.2.8-ckt3. The kernel bisect will require testing of about 7-10 test kernels.

I built the first test kernel, up to the following commit:
37d9ba08a0fe9735d42ec93e96d6b99484aca0c2

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1548867

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

[Nworbnhoj (nworbnhoj)]

I can confirm that a Lenovo T400 experiencing this problem with "Graphic mode=Switchable" was resolved with "Graphic mode=Discrete".
Note that I also needed to set "OS Detection for Switchable Graphics=Disabled"

[Marcin (marsprivate+web)]

@Joseph There's nothing under that link.

[Marco van Zwetselaar (zwets)]

@jsalisbury I think you copied the files to the wrong directory. I guessed from timestamps that they might be in http://kernel.ubuntu.com/~jsalisbury/lp1498667/ . I am now running without issues on kernel 4.1.0-040100.201603021615 from that directory. However I didn't install the headers deb so I guess that I'm running with any DKMS modules.

[Marco van Zwetselaar (zwets)]

Ah, spotted the (probable) directory now: http://kernel.ubuntu.com/~jsalisbury/lp1549967/
That's a s/88/99/ and the bug is totally unrelated. Downloading kernel and headers now.

[Marco van Zwetselaar (zwets)]

Just tested 4.2.8-040208ckt2.201603021201 and it exhibits the bug.

[Joseph Salisbury (jsalisbury)]

Good catch, Marco. Thanks for finding the correct directory and testing it. I updated the bisect and am building the next kernel now. I'll post it the the correct directory shortly.

[Joseph Salisbury (jsalisbury)]

I built the first test kernel, up to the following commit:
37c95c36efa1173b25a53241362f100ed2e3baa8

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1548867

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

[Marcin (marsprivate+web)]

4.2.8-040208ckt2-generic_4.2.8-040208ckt2.20160303095 doesn't work.

[Joseph Salisbury (jsalisbury)]

I built the first test kernel, up to the following commit:
2a68dd76355cde6110797a506ca1b204dcfb37f2

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1548867

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

[Marco van Zwetselaar (zwets)]

4.2.8-040208ckt2-generic_4.2.8-040208ckt2.201603031453 has the bug.

[Marcin (marsprivate+web)]

4.2.8-040208ckt2-generic_4.2.8-040208ckt2.201603031453 has the bug.

[Joseph Salisbury (jsalisbury)]

I built the next test kernel, up to the following commit:
3c3361a6f6e7a682046b405200aea1661a6d3bf5

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1548867

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

[Marco van Zwetselaar (zwets)]

4.2.8-040208ckt2-generic_4.2.8-040208ckt2.201603071309 has the bug, sorry :-/

[Marcin (marsprivate+web)]

Same here.

[Joseph Salisbury (jsalisbury)]

Thanks for testing. During a bisect, it's expected that some test kernels will have the bug while others do not.

I built the next test kernel, up to the following commit:
379901c98e248ecc0127dccd979e104f8a9d4f65

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1548867

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

[Francis (lobofrancis777)]

I too faced the booting problem with Ubuntu 15.10 to kernel 4.2.0.30 after software update. But if I move to previous Kernel version 4.2.0.27, then it is working fine.

Today again I updated my Kernel 4.2.0.30. Now everything is working fine. It seems there was a bug, but now it is resolved.

[Thomas Karl Pietrowski (thopiekar)]

I've got the same problem, as many others here on my HP notebook using AMD+Intel hybrid GFX. I upgraded to xenial just to check whether there is the same problem to and yes, there is the same in 4.4.x.

[dmylnikov (altsiona)]

4.2.8-040208ckt2-generic_4.2.8-040208ckt2.201603091448 works fine

[Marco van Zwetselaar (zwets)]

Confirming that 4.2.8-040208ckt2-generic_4.2.8-040208ckt2.201603091448 works fine here too. @jsalisbury thanks for going after this bug.

[Albert Cutrona (acutbal)]

Hi!!

New kernel update, v. 4.2.0-34, the problem has gone, my laptop boots as usual.

Thank you very much for all!! :D :D

[Christoph Buchner (bilderbuchi)]

@jsalisbury: just to be clear: it's confirmed that jumping from 4.2.0.27 to the current repo version of linux-image-generic, 4.2.0.34.37, should be safe and avoid this bug?

[Joseph Salisbury (jsalisbury)]

@Christoph Buchner, correct. You should upgrade to the latest Ubuntu 4.2 kernel.

[Christoph Buchner (bilderbuchi)]

thank you, installing now. :-)

[Marco van Zwetselaar (zwets)]

Confirming that kernel 4.2.0-34.39 in current Wily does not have the bug.