On Fri, Mar 9, 2018 at 9:49 AM, Joseph Salisbury
<email address hidden> 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 changed.
I can reproduce this on multiple trusty kernels:
3.13.0-101-generic (buildd@lgw01-40) #148-Ubuntu SMP Thu Oct 20
22:08:32 UTC 2016
3.13.0-107-generic (buildd@lcy01-09) #154-Ubuntu SMP Tue Dec 20
09:57:27 UTC 2016
3.13.0-137-generic (buildd@lgw01-amd64-058) #186-Ubuntu SMP Mon Dec 4
19:09:19 UTC 2017
3.13.0-143-generic (buildd@lcy01-amd64-010) #192-Ubuntu SMP Tue Feb 27
10:45:36 UTC 2018
I can confirm that newer kernels do not have this issue:
4.4.0-116-generic (buildd@lcy01-amd64-023) (gcc version 4.8.4 (Ubuntu
4.8.4-2ubuntu1~14.04.4))
Xenial, Artful and Bionic are fine.
>
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-fixed-upstream'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> Once testing of the upstream kernel is complete, please mark this bug as
> "Confirmed".
>
>
> Thanks in advance.
>
> [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc4
>
> ** Changed in: linux (Ubuntu Trusty)
> Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> ** Tags added: kernel-da-key
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1754581
>
> Title:
> trusty bcache NULL pointer exception
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754581/+subscriptions
On Fri, Mar 9, 2018 at 9:49 AM, Joseph Salisbury
<email address hidden> 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 changed.
I can reproduce this on multiple trusty kernels:
3.13.0-101-generic (buildd@lgw01-40) #148-Ubuntu SMP Thu Oct 20 lgw01-amd64- 058) #186-Ubuntu SMP Mon Dec 4 lcy01-amd64- 010) #192-Ubuntu SMP Tue Feb 27
22:08:32 UTC 2016
3.13.0-107-generic (buildd@lcy01-09) #154-Ubuntu SMP Tue Dec 20
09:57:27 UTC 2016
3.13.0-137-generic (buildd@
19:09:19 UTC 2017
3.13.0-143-generic (buildd@
10:45:36 UTC 2018
> /wiki.ubuntu. com/KernelMainl ineBuilds . Please test the latest
> Would it be possible for you to test the latest upstream kernel? Refer
> to https:/
> v4.16 kernel[0].
I can confirm that newer kernels do not have this issue:
4.4.0-116-generic (buildd@ lcy01-amd64- 023) (gcc version 4.8.4 (Ubuntu 14.04.4) )
4.8.4-2ubuntu1~
Xenial, Artful and Bionic are fine.
> fixed-upstream' . bug-exists- upstream' . kernel. ubuntu. com/~kernel- ppa/mainline/ v4.16-rc4 /bugs.launchpad .net/bugs/ 1754581 /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/1754581/ +subscriptions
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-
>
> Once testing of the upstream kernel is complete, please mark this bug as
> "Confirmed".
>
>
> Thanks in advance.
>
> [0] http://
>
> ** Changed in: linux (Ubuntu Trusty)
> Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> ** Tags added: kernel-da-key
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> trusty bcache NULL pointer exception
>
> To manage notifications about this bug go to:
> https:/