removing as a dup only temorarily.
** This bug is no longer a duplicate of bug 802626
vgchange may deadlock in initramfs when VG present that's not used for rootfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 802626 ***
https://bugs.launchpad.net/bugs/802626
** This bug has been marked a duplicate of bug 802626
vgchange may deadlock in initramfs when VG present that's not used for rootfs
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 802626 ***
https://bugs.launchpad.net/bugs/802626
** This bug has been marked a duplicate of bug 802626
vgchange may deadlock in initramfs when VG present that's not used for rootfs
** This bug is no longer a duplicate of bug 802626
vgchange may
I caught the same bug, but I don't use any LVM. System hangs on boot
when I use -15 kernel (generic and manually recompiled). -13 kernel
works fine. I can't add --noudevsync to any line because there are no
appropriate.
Laptop: Acer Aspire 5739G.
--
You received this bug notification because
Reopened the bug by removing the duplicate status, following the comment
on bug 802626:
James,
I don't believe that's true. If the rootfs is in the same VG, there
should be no possibility of udev being stopped in the initramfs prior to
the dependent event making its way through the system,
Possible dups: bug 906358 and bug 631795
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902491
Title:
Severe regression with latest kernel update: 3.0.0-14.23 takes an
unreasonable amount of time
** Changed in: linux (Ubuntu)
Importance: Medium = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902491
Title:
Severe regression with latest kernel update: 3.0.0-14.23 takes an
*** This bug is a duplicate of bug 802626 ***
https://bugs.launchpad.net/bugs/802626
Given that the --noudevsync work-around from #802626 also appears to
reliably fix this bug, I'm marking this bug as a duplicate of #802626.
** This bug has been marked a duplicate of bug 802626
vgchange
I have this bug too with 3.2 kernels.
Acer Aspire TimelineX 5820TG
Ubuntu 11.10
All my partitions on lvm .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902491
Title:
Severe regression with latest
I can confirm --noudevsync does work around the problem. Just tested it
on latest 3.2.1 kernel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902491
Title:
Severe regression with latest kernel
Yes, I have exactly the same problem on my Thinkpad X61.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902491
Title:
Severe regression with latest kernel update: 3.0.0-14.23 takes an
unreasonable
I have a testing USB flash drive with bootable Ubuntu Oneiric on it.
I boot it with debug=y in kernel command line which causes init scripts to
output execution debug.info right to the console
I boot with either 3.0.0.-13 and 3.0.0-14 and find that noth of them hang
exactly on run-init executing
And yes, I tried to remove lvm2 mdadm and regenerate initramfs,
this did not change anything.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902491
Title:
Severe regression with latest kernel
I've also run into this bug.
3.0.0-14 introduced a - precisely - 60 second delay into my boot-time.
Tried 3.0.0-15 from proposed, with the same result. The only way to
alleviate it was to roll-back to 3.0.0-13 (last kernel to not exhibit
this behaviour). I've also tried a 3.2 kernel from
** 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/902491
Title:
Severe regression with latest kernel update: 3.0.0-14.23 takes an
unreasonable amount of time to boot due to
I have all my partitions on lvm except boot. I can confirm --noudevsync
does work around the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902491
Title:
Severe regression with latest
Can those who hit the bug please check if the patch in #802626 fixes the
issue?
(basicaly it consists in adding a --noudevsync parameter to the vgchange
command in
/lib/udev/rules.d/85-lvm2.rules. Then you need to regenerate the initramfs with
update-initramfs -u)
If it does we can probably
@Sergio, does the patch in 802626 resolve your issue?
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902491
Title:
Severe regression with latest kernel update:
Yes, as mentioned in #6, adding the --noudevsync parameter fixes the
delay for me.
Now, I wonder if it is just me, or also others have the same experience.
IMHO, this is important to know because the bug title in 802626 is about
those who have the root filesystem outside LVM and all the rest in
Another little note.
I made a lot of testing in the last days.
I have a feeling that in extremely rare cirumstances also 3.0.0-13 hangs at
boot (happened once in about 100 test boots)
Only, on my machine 3.0.0-13 hangs 1% of the boots (which goes unnoticed),
while -14 does systematically.
--
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lvm2 (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/902491
Title:
Severe
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: udev (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/902491
Title:
Severe
It looks like I hit this problem too, although perhaps I didn't leave it long
enough to see if it would boot. Just assumed with no disk activity it wasn't
going to boot.
In recovery mode it complained about a problem with root. Note root is on lvm2
and I'm running 64 Bit
3.0.0-13 works fine.
Tried to catch some error info by booting in recovery mode
I think I managed watching for an instant something about
watershed -c sh /sbin/lvm vgscan; /sbin/lvm vgchange -a y
Can this issue be related to lvm?
To Jason: do you have any lvm partition?
--
You received this bug notification
Ok, I think I am probably running into bug Bug #802626 or Bug #818177
What happens is that if I add --noudevsync to the lvm2 udev rule in
lib/udev and then I update the initramfs the delay disappears.
Thus adding lvm2 and udev to the bug.
However, I still wonder why I am running into this.
1)
This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report at bugzilla.kernel.org [1]? That will allow the upstream
Developers to examine the issue, and may provide a quicker resolution to
the bug.
If you
Also, you mention this is a regression. Does the 3.0.0-13-generic
kernel boot in a reasonable amount of time? If not, can you post the
last kernel that was booting properly?
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
In any case, if after thinking about the above points you still think
that I should open an upstram bug, I'll be glad to to so.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902491
Title:
Severe
3.0.0-13 is the latest kernel that is booting fine.
3.0.0-14 does not, nor does 3.2RC4
However I am not extremely comfortable at opening an upstream kernel
bug. The following points are unclear to me:
1) I have a strong suspicion that the issue I am running into is caused
by a subtle timing
Same problem here. Had to revert to old kernel for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902491
Title:
Severe regression with latest kernel update: 3.0.0-14.23 takes an
unreasonable
30 matches
Mail list logo
