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
** 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 =
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.
--
You received this bug notification because you are a
I will also submit an SRU request for Quantal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1034099
Title:
Kernel panic with ulatencyd on kernel 3.2.0-29-generic
To manage notifications about
I can confirm that the new kernel - 3.2.0-34.53~lp1034099v2_all.deb -
doesn't suffer from this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1034099
Title:
Kernel panic with ulatencyd on
** Tags removed: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1034099
Title:
Kernel panic with ulatencyd on kernel 3.2.0-29-generic
To manage notifications about this bug go to:
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
--
You received this bug notification because you are a member of Ubuntu
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
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
--
You received this bug notification because you are a
** Changed in: linux (Ubuntu)
Importance: Undecided = High
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1034099
Title:
Kernel panic with ulatencyd on kernel
** Tags added: performing-bisect
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1034099
Title:
Kernel panic with ulatencyd on kernel 3.2.0-29-generic
To manage notifications about this bug go to:
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Status: Confirmed = In Progress
** Also affects: linux (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: ulatencyd (Ubuntu Precise)
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
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
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
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Tags added: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1034099
Title:
Kernel panic with ulatencyd on kernel 3.2.0-29-generic
To manage notifications about this bug go to:
Yes - I can confirm that this bug still happen in 12.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1034099
Title:
Kernel panic with ulatencyd on kernel 3.2.0-29-generic
To manage notifications
Does this happen with 12.10's kernel? If it doesn't, it might be worth
considering to up the kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1034099
Title:
Kernel panic with ulatencyd on
Is this still valid? / Why haven't anyone fixed this yet?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1034099
Title:
Kernel panic with ulatencyd on kernel 3.2.0-29-generic
To manage
** Tags added: kernel-bug regression-update
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1034099
Title:
Kernel panic
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1034099
Title:
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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ulatencyd (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1034099
Title:
** Attachment added: Kernel log at system panic
https://bugs.launchpad.net/ubuntu/+source/ulatencyd/+bug/1034099/+attachment/3251644/+files/kernel.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
25 matches
Mail list logo