can't boot with new lowlatency kernel

[Sandra Karuving]

with the new 3.13.0-6-lowlatency i cant boot. it choose and shows up plymouth (or some text, if i disable plymout)
next the computer hungs up completely. no SysRq. only a hard turn off.
the same generic kernel works without problems

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-6-lowlatency 3.13.0-6.23
ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0
Uname: Linux 3.13.0-6-generic x86_64
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: fabi 2400 F.... pulseaudio
 /dev/snd/controlC1: fabi 2400 F.... pulseaudio
CurrentDesktop: KDE
Date: Fri Jan 31 16:59:44 2014
HibernationDevice: RESUME=UUID=1db62c66-60db-4cfe-bde9-72d501cc14cc
InstallationDate: Installed on 2013-12-12 (50 days ago)
InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Dell Inc. OptiPlex 760
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-6-generic root=UUID=5293cdc9-6817-4800-8809-b1d291d3a7e0 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-6-generic N/A
 linux-backports-modules-3.13.0-6-generic N/A
 linux-firmware 1.123
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/21/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.name: 0F373D
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 15
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA15:bd08/21/2012:svnDellInc.:pnOptiPlex760:pvr:rvnDellInc.:rn0F373D:rvrA00:cvnDellInc.:ct15:cvr:
dmi.product.name: OptiPlex 760
dmi.sys.vendor: Dell Inc.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Can you follow the "Boot options" instructions on the following wiki to enable additional output on boot:

https://wiki.ubuntu.com/DebuggingKernelBoot

As mentioned on the wiki, it would be great if you can attach a log file which may have captured any messages you see. If you are unable to capture a log file, a digital photo will work just as well. As a last resort you can even copy messages down by hand.

[Joseph Salisbury (jsalisbury)]

And just to confirm, like you mentioned in the description, the linux-image-3.13.0-6-generic kernel does boot fine?

Also, I see the apport data indicates: Package: linux-image-3.13.0-6-lowlatency 3.13.0-6.23. Does the kernel boot sometimes? If not, does it boot on the OptiPlex 760 and not another type of machine?

[Joseph Salisbury (jsalisbury)]

In additional to answering the previous questions, could you also try to boot with the following kernel boot option: "nothreadirqs"

[Joseph Salisbury (jsalisbury)]

I built an amd64 lowlatency test kernel with PREEMPT disabled. This kernel can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1275116/

Can you test this kernel and see if it also exhibits this bug? Please note, this is a diagnostic kernel and not a fix.

Thanks in advance!

[Sandra Karuving (lumks)]

Arrg :/ seems like yahoos imap dont work correctly. i didnt get any notification, sorry

your Kernel works.

all other lowletency kernels of the 3.13 series dont boot up on the optiplex, and EEEPC 1005h. not a single time. they just stop after a few secounds on boot.

[Joseph Salisbury (jsalisbury)]

@Sandra, thanks for the update.

Can you follow the details in comment #3 of this bug and see if there is additional debug info you can provide?

[Joseph Salisbury (jsalisbury)]

Also, the upstream 3.13.2 kernel is now available. Can you test this kernel to see if it still exhibits the bug? It can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.2-trusty/

[Sandra Karuving (lumks)]

3.13.0-8-lowlatency with bootuption "nothreadirqs" works (i can boot it up)

mainline lowlatency kernel (with ubuntu standard bootoptions) works too (but shows many many apparmor errors)

removing the standard boot options on 3.13.0-8-lowlatency (#3) dont work

[Joseph Salisbury (jsalisbury)]

We would like to gather as much info as possible when the boot failure happens. Comment #3 has a link on how to gather additional debug information. We would like you to remove quiet splash and add debug boot options. Then boot without the nothreadirqs option, to reproduce the problem.

As mentioned on the wiki, it would be great if you can attach a log file which may have captured any messages you see. If you are unable to capture a log file, a digital photo will work just as well. As a last resort you can even copy messages down by hand.

[Sandra Karuving (lumks)]

Is there some more generic way to get informations? because there are lots of parameters and i think i need to set them all, but i dont have the time to do this

[Joseph Salisbury (jsalisbury)]

We are looking for any messages printed to the screen when the boot fails. To see further debug info, you could edit the /etc/default/grub file and change this line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

to this:

GRUB_CMDLINE_LINUX_DEFAULT=""

Then run the following from a terminal:

sudo update-grub

Once you reboot, this change will take effect.

[Sandra Karuving (lumks)]

3 bootups with the 'GRUB_CMDLINE_LINUX_DEFAULT=""' option

http://i.imgur.com/csOYLTT.jpg
thats always the moment when nothing happens anymore and i have to hard-reset the computer.

[Joseph Salisbury (jsalisbury)]

Were you able to test the 3.13.2 kernel, which was posted in comment #9? It would be good to know if the bug still exists with that kernel.

[Sandra Karuving (lumks)]

already done it in comment #10 (its the mainline part). i can boot up. but what i had noticed, the computer freezes a little later while i work, or browse the web.

[Joseph Salisbury (jsalisbury)]

It would be good to know if when using the threadirqs parameter is a regression. If that is the case, we can bisect to identify the commit that introduced this.

Can you test the following kernels with the threadirqs parameter enabled and post back if any do not exhibit the bug:

v3.2 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2-precise/
v3.4 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-quantal/
v3.8 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-raring
v3.12 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-trusty/

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

Thanks in advance!

[Joseph Salisbury (jsalisbury)]

The following commit has landed in upstream v3.14-rc5:

commit a1227f3c1030e96ebc51d677d2f636268845c5fb
Author: Stanislaw Gruszka <email address hidden>
Date: Wed Feb 19 10:29:01 2014 +0100

    usb: ehci: fix deadlock when threadirqs option is used

It has also been cc'd to stable, so it will make it's way into the stable releases through the usual stable update process.

Can you test the latest mainline kernel to confirm it resolves this bug? It can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc5-trusty/

[Joseph Salisbury (jsalisbury)]

I built a Trusty test kernel that has a cherry pick of commit a1227f3c1030e96ebc51d677d2f636268845c5fb. This test kernel can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1275116/

Can you test this kernel and confirm it resolves this bug? I built an i386 and amd_64 version of the kernel. You will need to install both the linux-image and linux-image-extra packages.

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux - 3.13.0-16.36

---------------
linux (3.13.0-16.36) trusty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
    - LP: #1287903

  [ Andy Whitcroft ]

  * Revert "[Config] lowlatency -- turn CONFIG_IRQ_FORCED_THREADING_DEFAULT
    off temporarily"

  [ Chris Bainbridge ]

  * SAUCE: x86: set Pentium M as PAE capable
    - LP: #930447

  [ Dave Jones ]

  * SAUCE: taint: repurpose TAINT_UNSAFE_SMP to TAINT_CPU_OUT_OF_SPEC
    - LP: #930447

  [ Paolo Pisati ]

  * [Config] SND_DAVINCI_SOC && SND_AM33XX_SOC_EVM =m
  * [Config] armhf: DRM_TILCDC=m

  [ Philippe Bergheaud ]

  * SAUCE: powerpc: fix xmon disassembler for little-endian
    - LP: #1286255

  [ Tim Gardner ]

  * [Config] CONFIG_MICROCODE_EARLY=y
  * [Config] CONFIG_R8821AE=m
  * [Config] Add some virtio drivers to -virtual
    - LP: #1287401
  * [Config] inclusion-list: vesafb and virtio_balloon are built-in
  * SAUCE: vmwgfx: Expose U32_MAX

  [ Upstream Kernel Changes ]

  * Revert "drm/vmwgfx: Fix regression caused by "drm/ttm: make ttm
    reservation calls behave like reservation calls""
  * Revert "drm/vmwgfx: Fix the driver for large dma addresses"
  * usb: ehci: fix deadlock when threadirqs option is used
    - LP: #1274987, #1279081
  * Staging: rtl8812ae: Add Realtek 8821 PCI WIFI driver
    - LP: #1287298
  * intel_pstate: Remove periodic P state boost
  * intel_pstate: Add trace point to report internal state.
  * intel_pstate: Take core C0 time into account for core busy calculation
  * intel_pstate: Use LFM bus ratio as min ratio/P state
  * intel_pstate: Add support for Baytrail turbo P states
  * intel_pstate: Change busy calculation to use fixed point math.
  * PM / hibernate: Fix restore hang in freeze_processes()
  * ipmi: remove deprecated IRQF_DISABLED
  * ipmi: use USEC_PER_SEC instead of 1000000 for more meaningful
  * ipmi: fix timeout calculation when bmc is disconnected
  * ipmi: Cleanup error return
  * ipmi: Add missing rv in ipmi_parisc_probe()
  * drm/ttm: ttm object security fixes for render nodes
  * drivers: gpu: Mark functions as static in vmwgfx_kms.c
  * drivers: gpu: Mark functions as static in vmwgfx_buffer.c
  * drivers: gpu: Mark functions as static in vmwgfx_fence.c
  * drm/vmwgfx: Fix the driver for large dma addresses
  * drm/vmwgfx: Update the svga3d register header file for new device
    version
  * drm/vmwgfx: Update the driver user-space interface for guest-backed
    objects
  * drm/vmwgfx: Replace vram_size with prim_bb_mem for calculation of max
    resolution
  * drm/vmwgfx: Update the svga register definition
  * drm/vmwgfx: Adapt capability reporting to new hardware version
  * drm/vmwgfx: Add MOB management
  * drm/vmwgfx: Hook up MOBs to TTM as a separate memory type
  * drm/vmwgfx: Read bounding box memory from the appropriate register
  * drm/vmwgfx: Add the possibility to validate a buffer as a MOB
  * drm/vmwgfx: Hook up guest-backed queries
  * drm/vmwgfx: Detach backing store from its resources when it is evicted
  * drm/vmwgfx: Hook up guest-backed contexts
  * drm/vmwgfx: Hook up guest-backed surfaces
  * drm/vmwgfx: Add guest-backed shaders
  * drm/vmwgfx: Validate guest...