Kernel panic with ulatencyd on kernel 3.2.0-29-generic

Bug #1034099 reported by Artur Szymiec
152
This bug affects 34 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
High
Joseph Salisbury
Precise
Fix Released
High
Joseph Salisbury
Quantal
Fix Released
High
Joseph Salisbury
ulatencyd (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

After latest kernel update to 3.2.0-29 Ubuntu 12.04 causes kernel panic on boot with ulatencyd installed. Removing the ulatencyd solves the problem. Attached kernel log. Seems that this is related to the network manager process.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: ulatencyd (not installed)
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
Uname: Linux 3.2.0-29-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu12
Architecture: amd64
Date: Tue Aug 7 19:56:18 2012
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423)
ProcEnviron:
 LANGUAGE=pl_PL
 TERM=xterm
 PATH=(custom, no user)
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
SourcePackage: ulatencyd
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Artur Szymiec (artur-szymiec) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in ulatencyd (Ubuntu):
status: New → Confirmed
Revision history for this message
BubbaJ (azstuenthome) wrote :

Also having trouble after installing 3.2.0-29 (not low latency, just the normal one). Something is not right. It failed during the install from 3.2.0-27 and told me that something was broken. I noticed that the Network Manager icon was grayed out after the kernel install. I reverted back to 3.2.0-27 and the Network Manager icon returned to normal. I uninstalled 3.2.0-29 and will wait until it's fixed.

Revision history for this message
PerfectCarl (name-is-carl) wrote :

It seems that it aslo prevent to install the guest additions for virtualbox.
The compilation is fine, but when you reboot your computer twice, the
boot process fails.

Removing ulatencyd fixes that.

tags: added: kernel-bug regression-update
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
CruelAngel (hendricha) wrote :

Is this still valid? / Why haven't anyone fixed this yet?

Revision history for this message
Otto Robba (otto-ottorobba) wrote :

Does this happen with 12.10's kernel? If it doesn't, it might be worth considering to up the kernel.

Revision history for this message
Artur Szymiec (artur-szymiec) wrote :

Yes - I can confirm that this bug still happen in 12.10.

Revision history for this message
RabbitBot (rabbitbot-a) wrote :

Still happens in generic x86-64 kernel, version 3.2.0.34.37

Screenshot of the lockup on boot: http://ompldr.org/vZ2p1Zg
(though it won't be particularly useful since a log is already attached)

tags: added: quantal regression-release
Changed in linux (Ubuntu):
importance: Undecided → High
tags: added: kernel-da-key
tags: added: performing-bisect
Changed in linux (Ubuntu):
assignee: nobody → Joseph Salisbury (jsalisbury)
status: Confirmed → In Progress
Changed in linux (Ubuntu Precise):
importance: Undecided → High
Changed in linux (Ubuntu Quantal):
importance: Undecided → High
Changed in linux (Ubuntu Precise):
status: New → In Progress
Changed in linux (Ubuntu Quantal):
status: New → In Progress
Changed in linux (Ubuntu Precise):
assignee: nobody → Joseph Salisbury (jsalisbury)
Changed in linux (Ubuntu Quantal):
assignee: nobody → Joseph Salisbury (jsalisbury)
no longer affects: ulatencyd (Ubuntu Precise)
no longer affects: ulatencyd (Ubuntu Quantal)
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

I'd like to perform a kernel bisect to identify what commit caused this regression. It sounds like this regression was introduced in 3.2.0-29.46, so I will bisect between 3.2.0-28.45 and 3.2.0-29.46.

I'm going to first see if I can reproduce this bug. If I can, I can perform the bisect and testing. Is installing the ulatencyd package all that is required, or do I need to do some configuring of ulatencyd?

This bug may be related to commit ffaf6a1e73719e0250fce7b52015187180a77fe9 . In parallel with bisecting, I'm going to build a test kernel with that commit reverted. I'll post a link to that test kernel shortly.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

I created a Precise test kernel with commit ffaf6a1e73719e0250fce7b52015187180a77fe9 reverted.

The test kernel can be downloaded from:
http://people.canonical.com/~jsalisbury/lp1034099/

Can folks affected by this bug test that kernel and report back if it still exhibits this bug?

Thanks in advance!

Revision history for this message
Artur Szymiec (artur-szymiec) wrote :

Hi,

I have just tested the proposed kernel 3.2.0-34-generic #53~lp1034099v1.
I can confirm that it works correctly with ulatencyd installed.
No crash or any other missbehaviour.
Great Job !!!

Kind regards

Artur

tags: added: kernel-key
tags: removed: kernel-key
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

It would be good if other folks affected by this bug can also test the kernel posted in comment #11.

Also, has anyone tested with the latest Raring kernel[0]?

[0] https://launchpad.net/ubuntu/+source/linux/3.7.0-4.12

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

I created another test kernel with the following commit reverted:
800d4d30c8f20bd728e5741a3b77c4859a613f7c

This test kernel does not have commit ffaf6a1e73719e0250fce7b52015187180a77fe9 reverted.

Reverting commit 800d4d30c8f20bd728e5741a3b77c4859a613f7c is what is done in a fix that is getting queued up in upstream stable. The upstream commit SHA1 is: fd8ef11730f1d03d5d6555aa53126e9e34f52f12

It would be great if folks affected by this bug can test this new kernel. The kernel can be downloaded from:

http://people.canonical.com/~jsalisbury/lp1034099/

Revision history for this message
Sergey "Shnatsel" Davidoff (shnatsel) wrote :

I can confirm that the new kernel - 3.2.0-34.53~lp1034099v2_all.deb - doesn't suffer from this bug.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This bug will be fixed when upstream commit fd8ef11 is applied to upstream stable v3.2. I see that it has already been applied to upstream v3.0, v3.4, and v3.6.

I'll monitor stable-queue and update the bug when the fix lands in 3.2.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

I will also submit an SRU request for Quantal.

Changed in linux (Ubuntu):
status: In Progress → Fix Released
Changed in linux (Ubuntu Quantal):
status: In Progress → Fix Released
Changed in linux (Ubuntu Precise):
status: In Progress → Fix Released
Changed in ulatencyd (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Silvio Sisto (sistoviejo) wrote :

I have experienced this bug today. Installing ulatencyd renders an unbootable system (because it causes kernel panic). Uninstalling it solves the problem.

cat /etc/lsb-release
-------------------------
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=13.10
DISTRIB_CODENAME=saucy
DISTRIB_DESCRIPTION="Ubuntu 13.10"

uname -a
-----------
Linux ... 3.11.0-18-generic #32-Ubuntu SMP Tue Feb 18 21:11:14 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

aptitude show ulatencyd
-------------------------------
Package: ulatencyd
Version: 0.5.0-8
Section: universe/utils
Maintainer: Ubuntu Developers <email address hidden>
Architecture: amd64
Uncompressed Size: 403 k
Depends: libc6 (>= 2.17), libdbus-1-3 (>= 1.0.2), libdbus-glib-1-2 (>= 0.78), libglib2.0-0 (>= 2.22.0), liblua5.1-0, libpolkit-gobject-1-0 (>= 0.99), libxcb1, dbus,
         lua5.1 | lua, lua-posix
PreDepends: dpkg (>= 1.15.7.2)
Recommends: consolekit
Conflicts: ulatencyd

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.