** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/659422
Title:
Boot failure after upgrading kernel to 2.6.32-25-generic
To
** Tags added: bisect-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/659422
Title:
Boot failure after upgrading kernel to 2.6.32-25-generic
To manage notifications about this bug go to:
Failed to start up immediately after a virgin install of 32-bit Server
(Minimal Virtual Install option) 10.04 LTS on VMWare ESXi 4.1. Get the
segfault after the udevd failure line, then a revert to busybox.
Changing VMWare's identified OS from Ubuntu 32-bit to any other value does not
resolve
Changing any of the VM settings did not work for me (VMware 4.1),
2.6.32-38-generic failed with udevd segfault.
Finally I installed the virtual kernel (apt-get install linux-image-virtual),
which is suitable for VMware according to the Ubuntu Server FAQ:
I have the same problem after upgrading Vmware ESXi 4.0 to ESXi4.1.
I've found another work around that works for me:
In the vSphere manager, shutdown the virtual machine and edit it
settings: go to the Options tab, and select CPU/MMU Virtualization.
There, change the selected option from
Still segfaults all the way up to kernel .32 (from .25), on fully
updated virtual machines.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/659422
Title:
Boot failure after upgrading kernel to
** 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/659422
Title:
Boot failure after upgrading kernel to 2.6.32-25-generic
--
ubuntu-bugs
I am using a few of different JumpBoxes, and after migrating them from
ESXi4.0 to ESXi4.1 I went to boot them back up, in 2 of them have
received the error message saying:
Segmentation fault
Gave up waiting for root device
I have already tried switching the OS Type in vSphere device manager
It looks like the 2.6.35-* versions of the kernel do not have the same
problem.
This worked for me:
- If you don't have an ealier kernel version to boot into; in VMware, disable
acceleration for the VM. (Right click: Edit Settings... - Options - General
- Disable acceleration)
- Start the VM.
It may be worthwhile to note that the same errors above look like the same
errors when running any netboot image newer than the linux-20081029ubuntu100 eg:
32bit:
http://archive.ubuntu.com/ubuntu/dists/lucid/main/installer-i386/20081029ubuntu100/images/netboot/ubuntu-installer/i386/linux
I can confirm that this happens with kernel 2.6.32-27-generic-pae on a
VMware ESX 4.1 (build 320092). udevadm segfaults right after the kernel
has finished loading, and it inevitable leads to failure to mount the
root filesystem.
Eagerly waiting for a fix!
--
You received this bug notification
Forgot to say that both kernels -27 and -26 work just fine on ESX 4.0.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/659422
Title:
Boot failure after upgrading kernel to 2.6.32-25-generic
--
** Branch linked: lp:ubuntu/maverick/sauce
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/659422
Title:
Boot failure after upgrading kernel to 2.6.32-25-generic
--
ubuntu-bugs mailing list
I bisected the problem down to this change:
commit 4f797709f4c0f61368c2f0f989cefc805fed0c9e
Author: Brad Figg brad.f...@canonical.com
Date: Fri Aug 27 09:10:55 2010 -0700
mm: make the vma list be doubly linked
BugLink: http://bugs.launchpad.net/bugs/625392
commit
Hello,
we had the same problem in our company and I found a solution for this.
In ESXi 4.1 vSphere Client choose the VM Ware-Machine which starts with the
segmentation fault
and go to the machine settings.
There you have to change the host operating system from Ubuntu 32 bit to
Another
Version
Hello,
we had the same problem in our company and I found a workaround for this.
In ESXi 4.1 vSphere Client choose the VM Ware-Machine which starts with the
segmentation fault
and go to the machine settings.
There you have to change the host operating system from Ubuntu 32 bit to
Another
Same problem here (after upgrade from ESX 3.5i - ESXi 4.1i) and 32 bits
Virtual Machine.
Ubuntu 10.04.1 LTS Kernel 2.6.32-25-generic-pae won't boot (udev segault):
same errors as below.
Upgrade to 2.6.32-26-generic: same problem.
Older installed kernel (2.6.24-23-server) won't boot too, udev
Tried with 2.6.32-24-generic: boot withou problems !
--
Boot failure after upgrading kernel to 2.6.32-25-generic
https://bugs.launchpad.net/bugs/659422
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This problem persists in the recent 2.6.32-26-generic kernel.
--
Boot failure after upgrading kernel to 2.6.32-25-generic
https://bugs.launchpad.net/bugs/659422
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Confirming that upgrading from 2.6.32-24 to 2.6.32-25 breaks the system.
Segmentation fault occurs while booting.
--
Boot failure after upgrading kernel to 2.6.32-25-generic
https://bugs.launchpad.net/bugs/659422
You received this bug notification because you are a member of Ubuntu
Bugs, which
I have gone back through the process and can confirm that on ESX 4.1 the
2.6.32-25-generic kernel segfaults during boot, the -pae kernel does not
segfault. The udevadm command segfaults:
udevadm[94]: segfault at 1 ip 0001 sp bfb55514 error 4 in libdl.so.2
After the segfault, the user is
This does not happen on ESX 3.5i or VMware Workstation 7.
--
Boot failure after upgrading kernel to 2.6.32-25-generic
https://bugs.launchpad.net/bugs/659422
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I can confirm this happens on VMware ESX 4.1. I know for certain it
does not happen on older vmware-server 1.0.X series. And when it dumps
me into the initramfs console, I can run udevadm and about 50% of the
time it will segfault.
--
Boot failure after upgrading kernel to 2.6.32-25-generic
Why exactly was it marked 'incomplete' without any additional comments?
What information is missing?
** Changed in: linux (Ubuntu)
Status: Incomplete = New
--
Boot failure after upgrading kernel to 2.6.32-25-generic
https://bugs.launchpad.net/bugs/659422
You received this bug
** Attachment added: AlsaDevices.txt
https://bugs.launchpad.net/bugs/659422/+attachment/1688925/+files/AlsaDevices.txt
** Attachment added: AplayDevices.txt
https://bugs.launchpad.net/bugs/659422/+attachment/1688926/+files/AplayDevices.txt
** Attachment added: BootDmesg.txt
** Changed in: linux (Ubuntu)
Status: New = Incomplete
--
Boot failure after upgrading kernel to 2.6.32-25-generic
https://bugs.launchpad.net/bugs/659422
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
26 matches
Mail list logo
