Happy to provide either hardware or help testing a solution if needed!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2015414
Title:
5.15.0-69 ice driver deadlocks with bonded e810 NICs
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1534054
Title:
use-after-free found by KASAN in blk_mq_register_disk
** Description changed:
We are trying to debug the kernel using KASAN and we found that when a
VM is booting in our cloud, on the virtualised kernel, there is a use-
after-free access that should not be there.
The failing VM was running on a host with kernel 3.13.0-66-generic
- (trusty)
** Description changed:
We are trying to debug the kernel using KASAN and we found that when a
VM is booting in our cloud, on the virtualised kernel, there is a use-
after-free access that should not be there.
- Here is the trace from KASAN:
+ The failing VM was running on a host with ker
** Description changed:
+ We are trying to debug the kernel using KASAN and we found that when a
+ VM is booting in our cloud, on the virtualised kernel, there is a use-
+ after-free access that should not be there.
+
+ Here is the trace from KASAN:
+
The error message can be observed in the d
This bug is probably not relevant anymore, I just tried on my laptop and
it crashed nicely:
ii linux-crashdump 3.13.0.49.56
amd64Linux kernel crashdump setup for the latest generic kernel
Kernel: 3.16.0-28-generic
On trusty.
** Tags removed: cts
*
My deployment is still running strong after over 36 hours. No crashes. I
will leave it running for a few more days to see if it happens after a
few days... and will report back.
@arges, thanks for this fix!
--
You received this bug notification because you are a member of Kernel
Packages, which
I have been trying to verify this kernel and I haven't seen exactly the
soft lockup crash, but this other one, which may or may not be related
but wanted to make a note of it:
[ 2406.041444] Kernel panic - not syncing: hung_task: blocked tasks
[ 2406.043163] CPU: 1 PID: 35 Comm: khungtaskd Not tai
I have a different VM that has crashed (also nested nova compute), this
one had ksm disabled. See log attached.
** Attachment added: "soft-lockup-different-node.log"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1413540/+attachment/4303814/+files/soft-lockup-different-node.log
** Change
apport file for linux.
** Attachment added: "apport.linux-image-3.13.0-44-generic.61de1tqv.apport"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1413540/+attachment/4303622/+files/apport.linux-image-3.13.0-44-generic.61de1tqv.apport
--
You received this bug notification because you are
I can reproduce this issue and hand a VM over to whoever is going to
triage in a hung state.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1413540
Title:
qemu-kvm package enables KSM on
apport for qemu
** Attachment added: "apport.qemu.pnfp6lff.apport"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1413540/+attachment/4303623/+files/apport.qemu.pnfp6lff.apport
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
apport file for linux.
** Attachment added: "apport.linux-image-3.13.0-44-generic.61de1tqv.apport"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1413540/+attachment/4303621/+files/apport.linux-image-3.13.0-44-generic.61de1tqv.apport
--
You received this bug notification because you are
13 matches
Mail list logo
