After 14.10 updates to kernel 3.16.0-36, system is not booting, resulting in black screen due to NULL pointer in intel_ring_init_seqno

[Pirouette Cacahuète]

This happens everytime I boot after updating kernel from 3.16.0-34 to 3.16.0-36. Keeping 3.16.0-34 still works.

Blackscreen is illuminated. I do not see any splash screen, nor X. Failsafe mode works, booting with "nomodeset" works (but it's slow). When this happens, on the next reboot I do see some "BUG:" lines in syslog, like:

Apr 27 21:01:54 portable-alex kernel: [ 2.457904] BUG: unable to handle kernel NULL pointer dereference at (null)
Apr 27 21:01:54 portable-alex kernel: [ 2.457911] IP: [< (null)>] (null)
Apr 27 21:01:54 portable-alex kernel: [ 2.457913] PGD 51b93d067 PUD 51b8ec067 PMD 0
Apr 27 21:01:54 portable-alex kernel: [ 2.457916] Oops: 0010 [#1] SMP
Apr 27 21:01:54 portable-alex kernel: [ 2.457918] Modules linked in: rtsx_pci_sdmmc i915(+) e1000e ahci ptp i2c_algo_bit drm_kms_helper libahci pps_core psmouse drm rtsx_pci wmi video
Apr 27 21:01:54 portable-alex kernel: [ 2.457926] CPU: 0 PID: 128 Comm: systemd-udevd Not tainted 3.16.0-36-generic #48-Ubuntu
Apr 27 21:01:54 portable-alex kernel: [ 2.457929] Hardware name: LENOVO 20BXCTO1WW/20BXCTO1WW, BIOS JBET45WW (1.10 ) 02/03/2015
Apr 27 21:01:54 portable-alex kernel: [ 2.457930] task: ffff88051be6bd20 ti: ffff88051b9a8000 task.ti: ffff88051b9a8000
Apr 27 21:01:54 portable-alex kernel: [ 2.457932] RIP: 0010:[<0000000000000000>] [< (null)>] (null)
Apr 27 21:01:54 portable-alex kernel: [ 2.457934] RSP: 0018:ffff88051b9ab890 EFLAGS: 00010286
Apr 27 21:01:54 portable-alex kernel: [ 2.457936] RAX: 0000000000000246 RBX: ffff88051bbb1928 RCX: 0000000000000001
Apr 27 21:01:54 portable-alex kernel: [ 2.457937] RDX: 0000000000000001 RSI: 00000000ffffeffe RDI: ffff88051bbb1928
Apr 27 21:01:54 portable-alex kernel: [ 2.457938] RBP: ffff88051b9ab8b0 R08: ffff88051bbb0000 R09: 0000000000000246
Apr 27 21:01:54 portable-alex kernel: [ 2.457940] R10: ffff880529403900 R11: ffffffff811a6ddf R12: 00000000ffffeffe
Apr 27 21:01:54 portable-alex kernel: [ 2.457941] R13: ffff88051bbb0000 R14: 00000000ffffeffe R15: ffff88051bf90800
Apr 27 21:01:54 portable-alex kernel: [ 2.457942] FS: 00007f8127b4f880(0000) GS:ffff88053dc00000(0000) knlGS:0000000000000000
Apr 27 21:01:54 portable-alex kernel: [ 2.457944] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 27 21:01:54 portable-alex kernel: [ 2.457945] CR2: 0000000000000000 CR3: 000000051b942000 CR4: 00000000003407f0
Apr 27 21:01:54 portable-alex kernel: [ 2.457947] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Apr 27 21:01:54 portable-alex kernel: [ 2.457948] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Apr 27 21:01:54 portable-alex kernel: [ 2.457949] Stack:
Apr 27 21:01:54 portable-alex kernel: [ 2.457950] ffffffffc02499fd ffff88051bbb1928 ffff88051bbb7148 ffff88051bbb7148
Apr 27 21:01:54 portable-alex kernel: [ 2.457953] ffff88051b9ab8e8 ffffffffc022e5b7 00000000ffffefff 00000000ffffeffe
Apr 27 21:01:54 portable-alex kernel: [ 2.457955] ffff88051bbb0000 ffff88051bbb0000 ffff88051bbb0000 ffff88051b9ab910
Apr 27 21:01:54 portable-alex kernel: [ 2.457957] Call Trace:
Apr 27 21:01:54 portable-alex kernel: [ 2.457977] [<ffffffffc02499fd>] ? intel_ring_init_seqno+0x3d/0xb0 [i915]
Apr 27 21:01:54 portable-alex kernel: [ 2.457991] [<ffffffffc022e5b7>] i915_gem_init_seqno+0x77/0xc0 [i915]
Apr 27 21:01:54 portable-alex kernel: [ 2.458002] [<ffffffffc022e629>] i915_gem_set_seqno+0x29/0x60 [i915]
Apr 27 21:01:54 portable-alex kernel: [ 2.458013] [<ffffffffc022fdcd>] i915_gem_init_hw+0x12d/0x380 [i915]
Apr 27 21:01:54 portable-alex kernel: [ 2.458022] [<ffffffffc0230075>] i915_gem_init+0x55/0x1d0 [i915]
Apr 27 21:01:54 portable-alex kernel: [ 2.458039] [<ffffffffc02956a2>] i915_driver_load+0xe32/0x1030 [i915]
Apr 27 21:01:54 portable-alex kernel: [ 2.458042] [<ffffffff813a05e8>] ? kobject_uevent_env+0x178/0x690
Apr 27 21:01:54 portable-alex kernel: [ 2.458046] [<ffffffff814cf087>] ? get_device+0x17/0x30
Apr 27 21:01:54 portable-alex kernel: [ 2.458048] [<ffffffff814d4af5>] ? klist_class_dev_get+0x15/0x20
Apr 27 21:01:54 portable-alex kernel: [ 2.458051] [<ffffffff817773b8>] ? klist_node_init+0x38/0x60
Apr 27 21:01:54 portable-alex kernel: [ 2.458054] [<ffffffff81777476>] ? klist_add_tail+0x46/0x50
Apr 27 21:01:54 portable-alex kernel: [ 2.458056] [<ffffffff814d089b>] ? device_add+0x1db/0x6d0
Apr 27 21:01:54 portable-alex kernel: [ 2.458066] [<ffffffffc012f4f6>] ? drm_sysfs_device_add+0xd6/0x120 [drm]
Apr 27 21:01:54 portable-alex kernel: [ 2.458072] [<ffffffffc012b9dd>] drm_dev_register+0xad/0x100 [drm]
Apr 27 21:01:54 portable-alex kernel: [ 2.458078] [<ffffffffc012e5cd>] drm_get_pci_dev+0x8d/0x200 [drm]
Apr 27 21:01:54 portable-alex kernel: [ 2.458088] [<ffffffffc020b4bb>] i915_pci_probe+0x3b/0x60 [i915]
Apr 27 21:01:54 portable-alex kernel: [ 2.458091] [<ffffffff813e6d15>] local_pci_probe+0x45/0xa0
Apr 27 21:01:54 portable-alex kernel: [ 2.458093] [<ffffffff813e7ff5>] ? pci_match_device+0xe5/0x110
Apr 27 21:01:54 portable-alex kernel: [ 2.458096] [<ffffffff813e8139>] pci_device_probe+0xd9/0x130
Apr 27 21:01:54 portable-alex kernel: [ 2.458098] [<ffffffff814d3bd3>] driver_probe_device+0xa3/0x410
Apr 27 21:01:54 portable-alex kernel: [ 2.458100] [<ffffffff814d400b>] __driver_attach+0x8b/0x90
Apr 27 21:01:54 portable-alex kernel: [ 2.458101] [<ffffffff814d3f80>] ? __device_attach+0x40/0x40
Apr 27 21:01:54 portable-alex kernel: [ 2.458104] [<ffffffff814d1a4b>] bus_for_each_dev+0x6b/0xb0
Apr 27 21:01:54 portable-alex kernel: [ 2.458106] [<ffffffff814d365e>] driver_attach+0x1e/0x20
Apr 27 21:01:54 portable-alex kernel: [ 2.458107] [<ffffffff814d3260>] bus_add_driver+0x180/0x250
Apr 27 21:01:54 portable-alex kernel: [ 2.458109] [<ffffffff814d47e4>] driver_register+0x64/0xf0
Apr 27 21:01:54 portable-alex kernel: [ 2.458112] [<ffffffff813e658c>] __pci_register_driver+0x4c/0x50
Apr 27 21:01:54 portable-alex kernel: [ 2.458117] [<ffffffffc012e84a>] drm_pci_init+0x10a/0x140 [drm]
Apr 27 21:01:54 portable-alex kernel: [ 2.458119] [<ffffffffc02ed000>] ? 0xffffffffc02ecfff
Apr 27 21:01:54 portable-alex kernel: [ 2.458129] [<ffffffffc02ed089>] i915_init+0x89/0x90 [i915]
Apr 27 21:01:54 portable-alex kernel: [ 2.458132] [<ffffffff81002148>] do_one_initcall+0xd8/0x210
Apr 27 21:01:54 portable-alex kernel: [ 2.458135] [<ffffffff811a8902>] ? __vunmap+0xa2/0x100
Apr 27 21:01:54 portable-alex kernel: [ 2.458138] [<ffffffff810f39f8>] load_module+0x14b8/0x1b60
Apr 27 21:01:54 portable-alex kernel: [ 2.458140] [<ffffffff810ef370>] ? store_uevent+0x40/0x40
Apr 27 21:01:54 portable-alex kernel: [ 2.458143] [<ffffffff811e77b8>] ? kernel_read+0x48/0x60
Apr 27 21:01:54 portable-alex kernel: [ 2.458145] [<ffffffff810f4216>] SyS_finit_module+0x86/0xb0
Apr 27 21:01:54 portable-alex kernel: [ 2.458149] [<ffffffff8178c98d>] system_call_fastpath+0x1a/0x1f
Apr 27 21:01:54 portable-alex kernel: [ 2.458150] Code: Bad RIP value.
Apr 27 21:01:54 portable-alex kernel: [ 2.458153] RIP [< (null)>] (null)
Apr 27 21:01:54 portable-alex kernel: [ 2.458154] RSP <ffff88051b9ab890>
Apr 27 21:01:54 portable-alex kernel: [ 2.458155] CR2: 0000000000000000
Apr 27 21:01:54 portable-alex kernel: [ 2.458157] ---[ end trace e531fde427227413 ]---

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-36-generic 3.16.0-36.48
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.4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: alex 3165 F.... pulseaudio
 /dev/snd/controlC0: alex 3165 F.... pulseaudio
Date: Tue Apr 28 09:20:10 2015
HibernationDevice: RESUME=UUID=3013558c-f831-45dd-8df1-9446a8f310c5
InstallationDate: Installed on 2012-11-03 (905 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: LENOVO 20BXCTO1WW
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-34-generic root=UUID=fb606209-63f0-4ff0-a524-a7cba117cdc3 ro quiet splash nomdmonddf nomdmonisw
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-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: Upgraded to utopic on 2015-03-07 (51 days ago)
dmi.bios.date: 02/03/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: JBET45WW (1.10 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BXCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrJBET45WW(1.10):bd02/03/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20BXCTO1WW
dmi.product.version: ThinkPad T450s
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[Pirouette Cacahuète (lissyx)]

Updated BIOS to latest version available (v1.12), no change.

[Alberto Salvia Novella (es20490446e)]

Do you experience this bug if you use <https://wiki.ubuntu.com/Kernel/MainlineBuilds>?

When answered, please set this bug status back to "confirmed". Thank you.

[Pirouette Cacahuète (lissyx)]

Alberto, is it really needed to check when I confirmed that 3.16.0-34 works well and that the issues starts with 3.16.0-36 ?
BTW, I already ran pre-4.0 kernel successfully on the same laptop while investigating https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1429489

[Pirouette Cacahuète (lissyx)]

According to /lib/modules/3.16.0-36-generic/build/.config:CONFIG_VERSION_SIGNATURE="Ubuntu 3.16.0-36.48-generic 3.16.7-ckt9", I should check mainline kernel http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16.7-ckt9-utopic/ ... Let's see what I get with this one.

[Pirouette Cacahuète (lissyx)]

So, kernel 3.16.7-ckt9 from mainline repos do boot successfully :)

[Alberto Salvia Novella (es20490446e)]

And the one at the top of <http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D>?

When answered, please set this bug status back to "confirmed".

[Pirouette Cacahuète (lissyx)]

How many kernels do you want that I test ? It's not like each time I have to stop working, so if I should get a bunch and test them at once, it will be easier for everyone ...

[Jerome Jolidon (jerome-jolidon)]

Also affects 14.04.2 LTS here.
Installed mainline kernel v4.1-rc1-vivid and it boots fine (although I cannot say if the info is relevant since I'm running trusty).

[Yang Yang (uk0052003)]

My 14.04.2 LTS has same problem.

[remerson (ubuntu-remerson)]

3.16.0-36 no boot on 14.04.2 LTS Intel NUC i3-5010U, as described above - going back to 3.16.0-34 works fine.

[Mick O'Rourke (mkorourke)]

- 3.16.0-36 not booting on 14.04.2 LTS, Lenovo x250, Intel i5
- 3.16.0-34 works fine if selected in grub to boot

process stops somewhere just before the display manager starts up

model name : Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz

  *-display
       description: VGA compatible controller
       product: Broadwell-U Integrated Graphics
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 09
       width: 64 bits
       clock: 33MHz
       capabilities: vga_controller bus_master cap_list rom
       configuration: driver=i915 latency=0

[John doe (r9-launchpad-fq)]

S

[John doe (r9-launchpad-fq)]

Same prb here with Ubuntu 14.04.2 LTS on Dell Latitude 7450.
- 3.16.0-36 not booting , Dell Latitude 7450, Intel i7 (Broadwell GT2)
- 3.16.0-34 works fine if selected in grub to boot

Seems related to Bug #1450156.

[John doe (r9-launchpad-fq)]

Trusty with utopic LTS enablement stack for graphics.

[Moritz Reiter (reitermoritz)]

Same problem on Thinkpad T450s (Broadwell chip) and Trusty.

3.16.0-34 works fine, 3.16.0-36 just shows black screen with backlight lit.

[John doe (r9-launchpad-fq)]

Similar as Pirouette Cacahuète: Blackscreen is illuminated. I do not see any splash screen, nor X. Failsafe mode works, booting with "nomodeset" works.

[penalvch (penalvch)]

Pirouette Cacahuète, the next step is to fully commit bisect from kernel 3.16.0-34 to 3.16.0-36 in order to identify the last good kernel commit, followed immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

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

[Pirouette Cacahuète (lissyx)]

Currently bisecting:
$ git bisect log
# bad: [4f37b5b1578d66c7d6787e180bddeb631f5adee5] UBUNTU: Ubuntu-3.16.0-36.48
# good: [cfe550c2824b7917963795cac393998ac56ceb5c] UBUNTU: Ubuntu-3.16.0-34.47
git bisect start 'Ubuntu-3.16.0-36.48' 'Ubuntu-3.16.0-34.47'
# bad: [fcf73471bf9fc7f60f10253c03739e49cf1f463e] drm/radeon: do a posting read in rs600_set_irq
git bisect bad fcf73471bf9fc7f60f10253c03739e49cf1f463e

[Pirouette Cacahuète (lissyx)]

Still bad for now:
$ git bisect log
# bad: [4f37b5b1578d66c7d6787e180bddeb631f5adee5] UBUNTU: Ubuntu-3.16.0-36.48
# good: [cfe550c2824b7917963795cac393998ac56ceb5c] UBUNTU: Ubuntu-3.16.0-34.47
git bisect start 'Ubuntu-3.16.0-36.48' 'Ubuntu-3.16.0-34.47'
# bad: [fcf73471bf9fc7f60f10253c03739e49cf1f463e] drm/radeon: do a posting read in rs600_set_irq
git bisect bad fcf73471bf9fc7f60f10253c03739e49cf1f463e
# bad: [611f6fde150fc2523b2074d40f4290af2e6e87ab] udp: only allow UFO for packets from SOCK_DGRAM sockets
git bisect bad 611f6fde150fc2523b2074d40f4290af2e6e87ab
# bad: [d89a0fb687d7c9cedd62b26f982258679cf70268] of: add optional options parameter to of_find_node_by_path()
git bisect bad d89a0fb687d7c9cedd62b26f982258679cf70268
# bad: [bf4787bab6ea96aaba9768c98e8d679e4ad47694] drm/ast: switch to using CACHED by default for sysram
git bisect bad bf4787bab6ea96aaba9768c98e8d679e4ad47694

I see potentially interesting commits in:
$ git log --oneline Ubuntu-3.16.0-34.47..
3329a6e drm/i915/bdw: Cleanup pre prod workarounds
d960a0b drm/i915/bdw: Apply workarounds in render ring init function
a4b15d0a drm/i915: call lpt_init_clock_gating on BDW too
090271c drm/i915/bdw: 3D_CHICKEN3 has write mask bits
d13c2ab KEYS: request_key() should reget expired keys rather than give EKEYEXPIRED
d745351 UBUNTU: Start new release

[Pirouette Cacahuète (lissyx)]

$ git bisect good
d960a0bdfb6406d65c29cad4689d03c895fa5fcd is the first bad commit
commit d960a0bdfb6406d65c29cad4689d03c895fa5fcd
Author: Arun Siluvery <email address hidden>
Date: Thu Mar 26 14:49:27 2015 +0200

    drm/i915/bdw: Apply workarounds in render ring init function

    BugLink: http://bugs.launchpad.net/bugs/1374389

    For BDW workarounds are currently initialized in init_clock_gating() but
    they are lost during reset, suspend/resume etc; this patch moves the WAs
    that are part of register state context to render ring init fn otherwise
    default context ends up with incorrect values as they don't get initialized
    until init_clock_gating fn.

    v2: Add workarounds to golden render state
    This method has its own issues, first of all this is different for
    each gen and it is generated using a tool so adding new workaround
    and mainitaining them across gens is not a straightforward process.

    v3: Use LRIs to emit these workarounds (Ville)
    Instead of modifying the golden render state the same LRIs are
    emitted from within the driver.

    v4: Use abstract name when exporting gen specific routines (Chris)

    For: VIZ-4092
    Signed-off-by: Arun Siluvery <email address hidden>
    Reviewed-by: Ville Syrjälä <email address hidden>
    Signed-off-by: Daniel Vetter <email address hidden>
    (backported from commit 86d7f23842f1bce3ab5e8c8d0c676112bbc4c99b)
    Signed-off-by: Timo Aaltonen <email address hidden>

    Conflicts:
     drivers/gpu/drm/i915/intel_ringbuffer.c
    Signed-off-by: Brad Figg <email address hidden>

:040000 040000 dadeaa890a6bee2e5d2fbd3cc0490ca0019d334d 34647b04b44f8b912d13e41c990b2eface864642 M drivers

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[penalvch (penalvch)]

Pirouette Cacahuète, could you please test the latest mainline kernel (4.1-rc1) and advise to the results?

[Timo Aaltonen (tjaalton)]

No need to test further mainlines, the backports that work fine on trusty kernel somehow broke here.. Need to investigate if something is still missing :/

[Timo Aaltonen (tjaalton)]

this is utopic specific

test kernel here:
http://koti.kapsi.fi/~tjaalton/bdw/

the mistake was pretty obvious, one extra 'else' where it shouldn't be..

[Pirouette Cacahuète (lissyx)]

Grabbing those kernel and giving a try

[Pirouette Cacahuète (lissyx)]

And I do confirm that the 3.16.0-36.48+bdw1 do works \o/

[Timo Aaltonen (tjaalton)]

thanks for testing and the bisect!

I'll send the patch so next (-38?) kernel should include it

[phitastic (robbel)]

Hi Timo,
> No need to test further mainlines, the backports that work fine on trusty kernel somehow broke here.
I have the same problem (blank screen when booting my broadwell-based thinkpad) under trusty. My current work-around is to use the previous kernel 3.16.0-34, or, to boot with -36 in recovery mode and then choose 'resume normal boot' (which then goes through fine). Could it be that the backport is broken there too? Or is that a separate bug report?
Thanks,
Philipp

[Timo Aaltonen (tjaalton)]

yes it is, will be fixed once the utopic kernel is available

[caljorden (caljorden)]

Same Problem here with

[caljorden (caljorden)]

Same problem here with Asus X305 laptop (Intel Core M-5Y10c CPU)

[Tom Fifield (fifieldt)]

exact same as this above for me:
- 3.16.0-36 not booting on 14.04.2 LTS, Lenovo x250, Intel i5
- 3.16.0-34 works fine if selected in grub to boot

fix needed in trusty, using 3.16.0-34 as a workaround for now.

[chrisber (chrisber)]

impact's Lenovo T550 Kernel 3.16.0-36 too.

[Timo Aaltonen (tjaalton)]

Every Broadwell is affected, no need to confirm this anymore.

[phitastic (robbel)]

14.04.2 LTS just made kernel 3.16.0-37 available but that unfortunately still does not fix the issue.

[Timo Aaltonen (tjaalton)]

check the version, you need 3.16.0-37.51, not .49 or .50

[Moritz Reiter (reitermoritz)]

The one in the public Trusty repositories (3.16.0-37.49~14.04.1.) doesn't work on my T450s.

I don't know how to install 3.16.0-37.51. I have the proposed repository enabled and tried "sudo apt-get install linux-image-3.16.0-37-generic/trusty-proposed" but it tells me I already have the newest version (-49).

[Moritz Reiter (reitermoritz)]

If someone could point me to a doc on how to install 3.16.0-37.51 in Trusty, I would be happy to test it.

I enabled the proposed repository and tried "sudo apt-get install linux-image-3.16.0-37-generic/trusty-proposed" but it tells me I already have the newest version, which is 3.16.0-37.49~14.04.1.

[Zee Alexander (pizzaops)]

Not fixed on my T450s either.

[Timo Aaltonen (tjaalton)]

https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+packages

or wait for the packages to be copied to the archive

[Moritz Reiter (reitermoritz)]

Thanks for the hint, Timo!

3.16.0-37.51 also doesn't boot on my T450s.

Boot process gets stuck displaying:

Loading Linux 3.16.0-37-generic
Loading initial ramdisk

I installed the .deb from the link you provided, Timo, and aptitude tells me the -51 version is installed:

$ sudo aptitude show linux-image-3.16.0-37-generic
[...]
Package: linux-image-3.16.0-37-generic
New: yes
State: installed
Automatically installed: no
Version: 3.16.0-37.51

3.16.0-34.47 is still the last kernel that works for me, although not perfectly (rendering issues when using SNA, fallback to UXA makes system usable but with partially very bad 2D graphics performance).

[Moritz Reiter (reitermoritz)]

I have to correct my last comment:

3.16.0-37.51 does boot.

I had to install the linux-image-extra package, too, which I didn't in the first try.

[Ross Grady (0iq-ross)]

I'm the reporter on Bug #1450156 which was marked as a dupe of this one. I can confirm that 3.16.0-37.51 boots successfully on my affected hardware (Lenovo Thinkpad X1 Carbon 3rd Generation).

[Zee Alexander (pizzaops)]

Problem is now fixed for me as well on my T450s:

gothputer :: ~ % uname -a
Linux gothputer 3.16.0-37-generic #51~14.04.1-Ubuntu SMP Wed May 6 15:23:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

[John doe (r9-launchpad-fq)]

boot problem is now fixed on my Dell Latitude E7450:
$ uname -a
Linux [snip] 3.16.0-37-generic #51~14.04.1-Ubuntu SMP Wed May 6 15:23:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

[Kat (katarina-kosovac)]

The boot just got fixed on Lenovo E550 aswel.

[andi bachmann (bachmann)]

after regular update through `update-manager` booting on my T450s is working again.

Thanks!

[Chris Crisafulli (itnet7)]

I have an HP Envy , model # m7-k211dx 5th Gen Intel® Core™ i7-5500U processor & NVIDIA GeForce 840M graphics. I have been having issues for the last couple of days where I had to avoid using the 36-generic kernel, the only way it would boot is if I chose a previous kernel version. Otherwise it would hang on a purple screen. after reading what bachmann wrote, I booted the laptop to a previous kernel and performed a regular update and am glad to say it worked for me as well!

[Pirouette Cacahuète (lissyx)]

Upgraded my T450s to latest kernel for 14.10 release, which is 3.16.0-38 (.52), and it does boot properly :). Thanks!

[Karl Koerner (karel-k-rehor)]

I know this is a bit late. I've had a lot of work the last two weeks. But this morning I upgraded the kernel to 3.16.0-37-generic and it works on my HP Pro Book 470 G2. Thanks!

[Andrej Krutak (andree182)]

3.16.0-38 seems to work on Thinkpad Yoga S3 (14), Broadwell... -36/-37 didn't work, -34 worked too. Ubuntu 14.04.