the fix above disables usage of dm (softraid) feature - this is not so
good :-(
so I am not able to use the feisty xen kernel together with Software
Raid0 or Raid5.
--
after upgrade edgy->feisty, high udev CPU usage
https://bugs.launchpad.net/bugs/89693
You received this bug notification becau
I also have the same problem with kernel 2.6.18 running on a cryptroot.
This does seem to be some kind of loop entered by udev. For me this
fixed the issue:
/etc/udev/rules.d/85-evms.rules:
commenting out this:
#SUBSYSTEM=="block", ACTION=="add|change", KERNEL=="dm-*",
GOTO="evms_activate_do"
f
** Changed in: udev (Ubuntu)
Status: Unconfirmed => Fix Released
--
after upgrade edgy->feisty, high udev CPU usage
https://bugs.launchpad.net/bugs/89693
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailin
I get similar behaviour on 2.6.19-4 with xen. (which is the only xen
kernel in feisty so far).
2.6.20-[9-13]-[generic|lowlatency|server] don't have this behaviour.
2.6.20-X xen kernel might solve this :)
--
after upgrade edgy->feisty, high udev CPU usage
https://launchpad.net/bugs/89693
--
ub
I get a similar symptom when testing a mainline 2.6.21-rc3 kernel.
It seems to be some kind of udev event loop involving the lvm2 and evms
udev rules. It is triggered for me when evms_activate is run.
Attached file is a log obtained by booting without the evms init script,
turning on udev debug l
Okay, sorry. Nevermind. I rebooted to the Ubuntu kernel
(2.6.20-9-generic) and I did not get the same behaviour. I guess it is
related to some upstream kernel bug that has been fixed in later
versions. For my part, I removed the dm-mod.ko module, and it "fixed"
this problem for me. (Since I am
