Very funny, this is during boot, I don't have any tools at the moment
during boot... Ok, when the robot says so, I'll try to set it to
confirmed...
** Description changed:
We got some strange problems here. We're running a vmware farm with
several clusters and different cpus. Customers often gave us a ubuntu
image, we start it and everything is fine. Now one of such machines runs
on an internal cluster and when we tried to move it to an outside
cluster (DMZ, we switched it off before, of course) it just crashes with
segmentation violation. We searched a long time and didn't expected the
kernel has a problem. But after a coworker changed the generic kernel to
the virtual kernel (same version!) everything went well. It seems that
this generic kernel (we're talking 'bout the 64bit version here) has
this problem with this specific CPU: Intel XEON E7340, 2.4 GHz (HP
- Blade: Proliant BL680c G5). Other HP-Hardware (e.g. Intel XEON X6550,
+ Blade: Proliant BL680c G5). Other HP-Hardware (e.g. Intel XEON X5650,
2.67 GHz, Proliant BL460c G6) works fine with generic kernel inside a
vmware VM. The same kernel-version but "virtual" (e.g. linux-
image-2.6.32-33-virtual) always works. A picture of the segmentation
violation of the generic kernel is attached...
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/832730
Title:
kernel crashes at startup/boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/832730/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
