[Kernel-packages] [Bug 1754581] Re: trusty bcache NULL pointer exception

2018-03-22 Thread Launchpad Bug Tracker
** Merge proposal unlinked: https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/341915 -- 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/1754581 Title: trusty bcache NULL

[Kernel-packages] [Bug 1754581] Re: trusty bcache NULL pointer exception

2018-03-22 Thread Launchpad Bug Tracker
** Merge proposal linked: https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/341915 -- 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/1754581 Title: trusty bcache NULL

[Kernel-packages] [Bug 1754581] Re: trusty bcache NULL pointer exception

2018-03-19 Thread Ryan Harper
I think it may have always been present; I can recreate this on Trusty GA kernels; we've changed how we clean/remove bcache devices which I believe is triggering a new path on Trusty kernels. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed

[Kernel-packages] [Bug 1754581] Re: trusty bcache NULL pointer exception

2018-03-12 Thread Joseph Salisbury
Do you happen to know if this is a regression in Trusty, or if this bug always existed in Trusty and was fixed in Xenial and newer kernels? ** Changed in: linux (Ubuntu Trusty) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged -- You

Re: [Kernel-packages] [Bug 1754581] Re: trusty bcache NULL pointer exception

2018-03-09 Thread Ryan Harper
On Fri, Mar 9, 2018 at 9:49 AM, Joseph Salisbury wrote: > Did this issue start happening after an update/upgrade? Was there a > prior kernel version where you were not having this particular problem? I don't think so; how we're using/clearing/stopping bcache has

[Kernel-packages] [Bug 1754581] Re: trusty bcache NULL pointer exception

2018-03-09 Thread Joseph Salisbury
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16