Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1390724 > unrolled thread

Re: [PATCH 3.16 000/217] 3.16.35-rc1 review

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [PATCH 3.16 000/217] 3.16.35-rc1 review Guenter Roeck <linux@roeck-us.net> - 2016-04-29 06:20 +0200
    Re: [PATCH 3.16 000/217] 3.16.35-rc1 review Ben Hutchings <ben@decadent.org.uk> - 2016-04-30 21:50 +0200
      Re: [PATCH 3.16 000/217] 3.16.35-rc1 review Guenter Roeck <linux@roeck-us.net> - 2016-05-01 01:30 +0200

#1390724 — Re: [PATCH 3.16 000/217] 3.16.35-rc1 review

On 04/26/2016 04:02 PM, Ben Hutchings wrote:
> This is the start of the stable review cycle for the 3.16.35 release.
> There are 217 patches in this series, which will be posted as responses
> to this one.  If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Sat Apr 30 22:00:00 UTC 2016.
> Anything received after that time might be too late.
>

Updated build and test results:

Build results:
	total: 137 pass: 135 fail: 2
Failed builds:
	arc:allnoconfig
	arm64:allmodconfig

Qemu test results:
	total: 97 pass: 94 fail: 3
Failed tests:
	arm:xilinx-zynq-a9:multi_v7_defconfig:zynq-zc706
	arm64:smp:defconfig
	arm64:nosmp:defconfig

This is after dropping a couple of builds and qemu tests which are
known to be bad in 3.16, and after some fixes in the tree.

The arm64 build failure is due to gcc5, which needs a patch from a
later kernel. The other failures are new and did not occur in 3.16.7.

A bisect of the arm64 qemu failure points to commit f98ab7a1e78
("mm, vmstat: allow WQ concurrency to discover memory reclaim doesn't
make any progress"). Unfortunately, that is inconclusive, since there
have been several follow-up commits trying to fix it. After reverting
all those commits, the test still fails.

Guenter

[toc] | [next] | [standalone]

#1391663

[Multipart message — attachments visible in raw view] — view raw

On Thu, 2016-04-28 at 21:16 -0700, Guenter Roeck wrote:
> On 04/26/2016 04:02 PM, Ben Hutchings wrote:
> > 
> > This is the start of the stable review cycle for the 3.16.35 release.
> > There are 217 patches in this series, which will be posted as responses
> > to this one.  If anyone has any issues with these being applied, please
> > let me know.
> > 
> > Responses should be made by Sat Apr 30 22:00:00 UTC 2016.
> > Anything received after that time might be too late.
> > 
> Updated build and test results:
> 
> Build results:
> 	total: 137 pass: 135 fail: 2
> Failed builds:
> 	arc:allnoconfig
> 	arm64:allmodconfig
>
> Qemu test results:
> 	total: 97 pass: 94 fail: 3
> Failed tests:
> 	arm:xilinx-zynq-a9:multi_v7_defconfig:zynq-zc706
> 	arm64:smp:defconfig
> 	arm64:nosmp:defconfig
> 
> This is after dropping a couple of builds and qemu tests which are
> known to be bad in 3.16, and after some fixes in the tree.
> 
> The arm64 build failure is due to gcc5, which needs a patch from a
> later kernel. The other failures are new and did not occur in 3.16.7.
>
> A bisect of the arm64 qemu failure points to commit f98ab7a1e78
> ("mm, vmstat: allow WQ concurrency to discover memory reclaim doesn't
> make any progress"). Unfortunately, that is inconclusive, since there
> have been several follow-up commits trying to fix it. After reverting
> all those commits, the test still fails.

Thank you very much for the analysis.  I'll look at the failures later
as none of them appear to be related to the current patch series.

Ben.

-- 
Ben Hutchings
Tomorrow will be cancelled due to lack of interest.

[toc] | [prev] | [next] | [standalone]

#1391722

On 04/30/2016 12:44 PM, Ben Hutchings wrote:
> On Thu, 2016-04-28 at 21:16 -0700, Guenter Roeck wrote:
>> On 04/26/2016 04:02 PM, Ben Hutchings wrote:
>>>
>>> This is the start of the stable review cycle for the 3.16.35 release.
>>> There are 217 patches in this series, which will be posted as responses
>>> to this one.  If anyone has any issues with these being applied, please
>>> let me know.
>>>
>>> Responses should be made by Sat Apr 30 22:00:00 UTC 2016.
>>> Anything received after that time might be too late.
>>>
>> Updated build and test results:
>>
>> Build results:
>> 	total: 137 pass: 135 fail: 2
>> Failed builds:
>> 	arc:allnoconfig
>> 	arm64:allmodconfig
>>
>> Qemu test results:
>> 	total: 97 pass: 94 fail: 3
>> Failed tests:
>> 	arm:xilinx-zynq-a9:multi_v7_defconfig:zynq-zc706

Update:

This failure was sporadic and easily fixed by adding "rootwait"
to the command line options.

Guenter

>> 	arm64:smp:defconfig
>> 	arm64:nosmp:defconfig
>>
>> This is after dropping a couple of builds and qemu tests which are
>> known to be bad in 3.16, and after some fixes in the tree.
>>
>> The arm64 build failure is due to gcc5, which needs a patch from a
>> later kernel. The other failures are new and did not occur in 3.16.7.
>>
>> A bisect of the arm64 qemu failure points to commit f98ab7a1e78
>> ("mm, vmstat: allow WQ concurrency to discover memory reclaim doesn't
>> make any progress"). Unfortunately, that is inconclusive, since there
>> have been several follow-up commits trying to fix it. After reverting
>> all those commits, the test still fails.
>
> Thank you very much for the analysis.  I'll look at the failures later
> as none of them appear to be related to the current patch series.
>
> Ben.
>

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web