It seems that the code causing the bug will be reverted in 4.9-rc7:
https://bugzilla.kernel.org/show_bug.cgi?id=187061#c15
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594023
Title:
Poweroff or
So, it seems we are all on Dell with a Samsung SSD 850 drive. Next week
I'll have a chance to try a different SSD from Kingston. I'll see if the
bug is still reproducible.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Could be related to this bug?
https://bugzilla.kernel.org/show_bug.cgi?id=187061
https://bugzilla.kernel.org/show_bug.cgi?id=151631
It affects kernels >= 4.8 on (as far as I know) any distro.
I'm experiencing problems on both Fedora 24 and Ubuntu 16.10 running kernel 4.8
on a Dell Latitude
We have the same problem, any news on this topic?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353269
Title:
celery worker crashes on startup when python-librabbitmq is used
To manage
During the weekend I was able to reproduce the issue using a Trusty VM with
kernel 3.13.0-43.72
kernel 3.13.0-44.73 fixes the issue.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
I can confirm that the issue looks fixed using 3.13.0-44.73~precise1
from precise-proposed.
I made more than ten reboots with the new kernel installed on VMs and
all were successful. Then I switched back to the previous
3.13.0-43.72~precise1 and VMs boot failed at the first trial. Again back
to
I have this issue running an Ubuntu 12.04.5 guest (running kernel
3.13.0-43-generic) on a KVM Hypervisor with the same configuration
(Ubuntu 12.04.5, 3.13.0-43, CPU 4x AMD Opteron(TM) Processor 6274, Dell
R915).
I'm unable to boot the guest the 80% of the trials. The error is
reproducible even
I confirm, like Jeff Wilson, that I had the same issue with 3.13 and got
resolved with 3.14.1.
I cannot right now test the kernel suggested in #46.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have the same issue on Ubuntu 12.04 LTS using Trusty kernel:
Linux version 3.13.0-29-generic (buildd@roseapple) (gcc version 4.6.3
(Ubuntu/Linaro 4.6.3-1ubuntu5) ) #53~precise1-Ubuntu SMP Wed Jun 4
22:06:25 UTC 2014
Distributor ID: Ubuntu
Description:Ubuntu 12.04.4 LTS
Release:
Public bug reported:
I'm unable to upgrade to procps 1:3.2.8-11ubuntu6.1 inside an LXC on
Ubuntu 12.04.3 (same version for both host and container).
When I run 'apt-get upgrade' I get:
Setting up procps (1:3.2.8-11ubuntu6.1) ...
start: Job failed to start
invoke-rc.d: initscript procps, action
Same problem on LXC containers. And
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1157643/comments/11
doesn't fix the issue for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1157643
The AMD microcode coming from linux-firmware - 1.79.6 is freezing 99% of
the times my 5 Dell PowerEdge M915 blades (4x64 Cores Opteron 6274,
currently with 3.0.4 BIOS).
This happens both at boot and also if I blacklist the 'microcode' module
and then I run 'modprobe microcode' after the system is
Thanks Grant.
The update is already scheduled for next Monday morning. I'll keep you updated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1200533
Title:
Please update AMD ucode/microcode in
13 matches
Mail list logo
