So any idea when the backport will drop?
--
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/1793901
Title:
kernel oops in bcache module
Status in linux package in Ubuntu:
Fix Committed
B
** Tags added: invalid
--
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/1793901
Title:
kernel oops in bcache module
Status in linux package in Ubuntu:
Incomplete
Bug description:
Thi
My system has changed somewhat, as I moved my root / to bcache with a kernel
that worked.
Still, I installed the mainline build, and the oops did not occur so far.
However I also cannot run that kernel properly as it does not seem to work well
with Nvidia graphics. (very low resolution and proba
My system has changed somewhat, as I moved my root / to bcache with a kernel
that worked.
Still, I installed the mainline build, and the oops did not occur so far.
However I also cannot run that kernel properly as it does not seem to work well
with Nvidia graphics. (very low resolution and proba
My system has changed somewhat, as I moved my root / to bcache with a kernel
that worked.
Still, I installed the mainline build, and the oops did not occur so far.
However I also cannot run that kernel properly as it does not seem to work well
with Nvidia graphics. (very low resolution and proba
https://launchpad.net/ubuntu/+source/linux/4.15.0-34.37
--
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/1793901
Title:
kernel oops in bcache module
Status in linux package in Ubuntu:
C
It seems that this might be only a problem with linux-image-4.15.0-34-generic
I tested it now with linux-image-4.15.0-34-generic and 4.18.0 (self compiled)
and in both cases the oops didn't trigger after a reasonable amount of time.
When checking the changelog for -34 it seems there was a change r
repost with ubuntu-bug and for different package as this one might be
more generally applicable. This is also reproducible, happens each time
sometime after mount, even after a reboot. New crash log is attached.
** Attachment added: "linux-image-4.15.0-34-generic.0.crash"
https://bugs.launchpa
Public bug reported:
This was on an 18.04.1 install running the 4.15-34 generic kernel image,
running from a normal ext4 root device.
I had just a short while before created a new bcache device that was mounted
but to which no data had been written yet. Then without any apparent particular
reas
9 matches
Mail list logo
