[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180604161649.GA16269@roeck-us.net>
Date: Mon, 4 Jun 2018 09:16:49 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, shuah@...nel.org, patches@...nelci.org,
ben.hutchings@...ethink.co.uk, lkft-triage@...ts.linaro.org,
stable@...r.kernel.org
Subject: Re: [PATCH 4.9 00/29] 4.9.106-stable review
On Mon, Jun 04, 2018 at 08:57:56AM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.106 release.
> There are 29 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Wed Jun 6 06:57:52 UTC 2018.
> Anything received after that time might be too late.
>
For v4.9.105-30-ge0f8632 (4.9.106-rc1-00030-ge0f8632):
Build results:
total: 148 pass: 148 fail: 0
Qemu test results:
total: 139 pass: 137 fail: 2
Failed tests:
mips64:malta_defconfig:nosmp
mips64:malta_defconfig:smp
Qemu tests fail with:
This architecture does not have kernel memory protection.
random: fast init done
Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000a
---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000a
While tracking this down, I found commit 4e4636cf981b ("objtool: Enclose
contents of unreachable() macro in a block"), which says "... Guenter Roeck
reported a boot failure in mips64 ...". Go figure. Applying commit
4e4636cf981b on top of v4.9.106-rc1 indeed fixes the problem.
Guenter
Powered by blists - more mailing lists