Public bug reported:
This issue results in kernel panics for anyone who uses CephFS.
After some digging we suspect this patch to be cause of the kernel
panics:
https://kernel.ubuntu.com/git/kernel-ppa/mirror/ubuntu-
bionic.git/commit/?id=eb0ba4bdcf12d9c29b9d3318627ad9ff3aff5471
This patch
Issue is introduced in bionic kernel 4.15.0-66
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849488
Title:
kernel panics due to incorrect backport
To manage notifications about this bug go to:
In hardy this bug seems to be solved indeed.
btw. this bug is linked to Epiphany - Clone of BoulderDash Game.
instead of the browser.
--
Dialog talking about Firefox
https://bugs.launchpad.net/bugs/39033
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
I don't know if this will help since it sounds a bit different:
We had some Ubuntu booting problems before (run manual build xen on
centos). We fixed this by building a new initrd in the domU and copy
that initrd to dom0 and use it in the config file instead of the
supplied one.
you can build a
The BIOS in these mainboards seems to check for the bootable flag. So
that would also explain the behavior Peter Adolphs explains.
--
No boot flag on any partition - Failure to boot after install - Intel
motherboards
https://bugs.launchpad.net/bugs/115633
You received this bug notification
I can confirm this bug. I installed feisty with the i386 desktop cd and
couldn't boot afterwards. Setting the root partition with the boot flag
fixed it. I attached lspci just in case it might be useful. This problem
also exists with the lastest BIOS version for the Intel DG965WH.
** Attachment
I fixed to problem by removing the nvidia driver and enabling it again
with the restricted-manager. I was missing some important options in
xorg.conf. I guess I was missing these because i upgrade this install
from dapper-edgy-feisty.
--
Title bar not drawn on maximized windows when desktop
Public bug reported:
Binary package hint: xen-image-xen0-2.6.17-5-server-xen0
Same thing happens on debian (xen-linux-system-2.6.17-2-xen-686).
We used the xen0-2.6.17-5-server kernel with the xen-
hypervisor-3.0.3-pae-i386 (3.0.3-rc2) and the generic version with non-
pae hypervisor. The
A correction: It doesn't seem to be related with LVM. Without it the
same thing happens. We also tried different filesystems (JFS and EXT3),
it makes no difference.
So its not related with LVM but the problem persists.
** Summary changed:
- Xen + LVM
+ Xen IOwait problem
** Description
