Adding lkft-triage@ list.
On Mon, Feb 18, 2019 at 10:14:06AM +0100, Niklas Cassel wrote:
Ok, my patch was included
author Niklas Cassel niklas.cassel@linaro.org2019-02-15 11:55:33 +0100 committer Mark Brown broonie@kernel.org2019-02-15 17:45:11 +0000
So it wasn't my patch :)
Thank you updating the status. Nice to see the problem fixed.
So my understanding here is that the issue is fixed as of next-20190211, and we don't know why.
The issue is still seen on mainline, which is approaching 5.0 release.
So: - next: fixed - mainline: broken - 4.20: working (was never broken in this way)
Since 5.0 will likely be released this weekend, can we identify the patch and get it merged into mainline so that 5.0 does not contain this issue when released?
Dan
On Mon, 18 Feb 2019 at 10:04, Naresh Kamboju naresh.kamboju@linaro.org wrote:
Niklas,
I do not know which patch fixed kernel panic [1] on db410c.
On Mon, 18 Feb 2019 at 14:28, Niklas Cassel niklas.cassel@linaro.org wrote:
FWIW I've sent a patch for the problem that Nicos found in the logs: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git/commit...
Unfortunately, I don't think it is related to your kernel not mounting rootfs.
Linux -next 20190211 onwards the db410c boot pass and running all LKFT test plan successfully. https://qa-reports.linaro.org/lkft/linux-next-oe/build/next-20190211/ This bug is been fixed as resolved.
[1] https://bugs.linaro.org/show_bug.cgi?id=4084#c7
- Naresh
On Tue, Feb 19, 2019 at 09:59:05AM -0600, Dan Rue wrote:
Adding lkft-triage@ list.
On Mon, Feb 18, 2019 at 10:14:06AM +0100, Niklas Cassel wrote:
Ok, my patch was included
author Niklas Cassel niklas.cassel@linaro.org2019-02-15 11:55:33 +0100 committer Mark Brown broonie@kernel.org2019-02-15 17:45:11 +0000
So it wasn't my patch :)
Thank you updating the status. Nice to see the problem fixed.
So my understanding here is that the issue is fixed as of next-20190211, and we don't know why.
The issue is still seen on mainline, which is approaching 5.0 release.
So:
- next: fixed
- mainline: broken
- 4.20: working (was never broken in this way)
Since 5.0 will likely be released this weekend, can we identify the patch and get it merged into mainline so that 5.0 does not contain this issue when released?
Daniel and I bisected this and found the commit that fixes the issue is: 535c78a9345a ("revert "initramfs: cleanup incomplete rootfs"")
which fixes ff1522bb7d9845 ("initramfs: cleanup incomplete rootfs"), which was first tagged in v5.0-rc1.
It has not been added to mainline yet.
Dan
On Mon, 18 Feb 2019 at 10:04, Naresh Kamboju naresh.kamboju@linaro.org wrote:
Niklas,
I do not know which patch fixed kernel panic [1] on db410c.
On Mon, 18 Feb 2019 at 14:28, Niklas Cassel niklas.cassel@linaro.org wrote:
FWIW I've sent a patch for the problem that Nicos found in the logs: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git/commit...
Unfortunately, I don't think it is related to your kernel not mounting rootfs.
Linux -next 20190211 onwards the db410c boot pass and running all LKFT test plan successfully. https://qa-reports.linaro.org/lkft/linux-next-oe/build/next-20190211/ This bug is been fixed as resolved.
[1] https://bugs.linaro.org/show_bug.cgi?id=4084#c7
- Naresh
On Thu, Feb 21, 2019 at 4:43 PM Dan Rue dan.rue@linaro.org wrote:
On Tue, Feb 19, 2019 at 09:59:05AM -0600, Dan Rue wrote:
Adding lkft-triage@ list.
On Mon, Feb 18, 2019 at 10:14:06AM +0100, Niklas Cassel wrote:
Ok, my patch was included
author Niklas Cassel niklas.cassel@linaro.org2019-02-15 11:55:33 +0100 committer Mark Brown broonie@kernel.org2019-02-15 17:45:11 +0000
So it wasn't my patch :)
Thank you updating the status. Nice to see the problem fixed.
So my understanding here is that the issue is fixed as of next-20190211, and we don't know why.
The issue is still seen on mainline, which is approaching 5.0 release.
So:
- next: fixed
- mainline: broken
- 4.20: working (was never broken in this way)
Since 5.0 will likely be released this weekend, can we identify the patch and get it merged into mainline so that 5.0 does not contain this issue when released?
Daniel and I bisected this and found the commit that fixes the issue is: 535c78a9345a ("revert "initramfs: cleanup incomplete rootfs"")
which fixes ff1522bb7d9845 ("initramfs: cleanup incomplete rootfs"), which was first tagged in v5.0-rc1.
It has not been added to mainline yet.
What makes this set of patches specific to DB410c? Do you understand that?
Dan
On Mon, 18 Feb 2019 at 10:04, Naresh Kamboju naresh.kamboju@linaro.org wrote:
Niklas,
I do not know which patch fixed kernel panic [1] on db410c.
On Mon, 18 Feb 2019 at 14:28, Niklas Cassel niklas.cassel@linaro.org wrote:
FWIW I've sent a patch for the problem that Nicos found in the logs: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git/commit...
Unfortunately, I don't think it is related to your kernel not mounting rootfs.
Linux -next 20190211 onwards the db410c boot pass and running all LKFT test plan successfully. https://qa-reports.linaro.org/lkft/linux-next-oe/build/next-20190211/ This bug is been fixed as resolved.
[1] https://bugs.linaro.org/show_bug.cgi?id=4084#c7
- Naresh
-- Linaro - Kernel Validation
On Thu, Feb 21, 2019 at 04:47:43PM +0100, Nicolas Dechesne wrote:
On Thu, Feb 21, 2019 at 4:43 PM Dan Rue dan.rue@linaro.org wrote:
On Tue, Feb 19, 2019 at 09:59:05AM -0600, Dan Rue wrote:
Adding lkft-triage@ list.
On Mon, Feb 18, 2019 at 10:14:06AM +0100, Niklas Cassel wrote:
Ok, my patch was included
author Niklas Cassel niklas.cassel@linaro.org2019-02-15 11:55:33 +0100 committer Mark Brown broonie@kernel.org2019-02-15 17:45:11 +0000
So it wasn't my patch :)
Thank you updating the status. Nice to see the problem fixed.
So my understanding here is that the issue is fixed as of next-20190211, and we don't know why.
The issue is still seen on mainline, which is approaching 5.0 release.
So:
- next: fixed
- mainline: broken
- 4.20: working (was never broken in this way)
Since 5.0 will likely be released this weekend, can we identify the patch and get it merged into mainline so that 5.0 does not contain this issue when released?
Daniel and I bisected this and found the commit that fixes the issue is: 535c78a9345a ("revert "initramfs: cleanup incomplete rootfs"")
which fixes ff1522bb7d9845 ("initramfs: cleanup incomplete rootfs"), which was first tagged in v5.0-rc1.
It has not been added to mainline yet.
What makes this set of patches specific to DB410c? Do you understand that?
Sorry I don't, was hoping someone else might know. Something to do with the size of initramfs? Our db410c build must have been the only combination that triggered it.
Dan
Dan
On Mon, 18 Feb 2019 at 10:04, Naresh Kamboju naresh.kamboju@linaro.org wrote:
Niklas,
I do not know which patch fixed kernel panic [1] on db410c.
On Mon, 18 Feb 2019 at 14:28, Niklas Cassel niklas.cassel@linaro.org wrote:
FWIW I've sent a patch for the problem that Nicos found in the logs: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git/commit...
Unfortunately, I don't think it is related to your kernel not mounting rootfs.
Linux -next 20190211 onwards the db410c boot pass and running all LKFT test plan successfully. https://qa-reports.linaro.org/lkft/linux-next-oe/build/next-20190211/ This bug is been fixed as resolved.
[1] https://bugs.linaro.org/show_bug.cgi?id=4084#c7
- Naresh
-- Linaro - Kernel Validation
-
Dan Rue -
Nicolas Dechesne