I have indeed tried unplugging/swapping connected USB peripherals and
that never appeared to help. The only thing that worked reliably for me
was pinning the old .67 kernel. Something changed after that and the
one thing that did stand out is a huge increase in the initrd image size
of later kern
Shelby,
It is something related to timing or something that is not correctly
initialized.
I have not seen the problem for sometime now. I'm using 18.04. Did you test it?
I don't know if it is fixed or not in recent releases. Maybe it's just
that something changed that misaligned the planets need
@luizluca
Were you ever able to discover a consistent work-around? I have
*exactly* the same issue with 16.04 since something like the .67 kernel
and I've exhausted everything I can think of to try and figure out why
it is behaving this way. The only thing that works (as you yourself
stumbled up
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686837
T
I found out that it wasn't the fact that I changed root=UUID=... that
workaround the bug but the fact that I edited grub. It does not matter
if I change or not settings. Just open the built-in editor and let it
boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
I got again the same bug problem even still on 4.11.0-041100rc8-generic.
It keeps failing even after a reboot. Again, I just changed root=UUID=...
to root=/dev/sda6 and the system booted nicely.
I'll attach a photo of the screen.
It looks like two dumpstacks (interrupt during panic?)
The error m
Maybe, this is the same
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1547559
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686837
Title:
ubuntu fails to boot with btrfs root (unable to moun
I'm running now with 4.11.0-041100rc8-generic and until now, I was not
able to reproduce the problem. Before using the upstream kernel, it was
very frequent for me, happening after every reboot (and requiring me to
boot rescue before a normal boot). It's very probable that upstream
kernel is not af
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.11 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
