[Qa-jenkins-dev] Bug#875990: Bug#875990: reproducible: i/o issues with profitbricks-build2-i386 since stretch upgrade

[Vagrant Cascadian]

On 2017-09-17, Holger Levsen wrote:
> On Sat, Sep 16, 2017 at 07:48:42PM -0700, Vagrant Cascadian wrote:
>> My *hunch* is that build2 and build12 are running a PAE kernel with more
>> than 8GB of ram, and affected by this kernel bug (introduced in linux
>> ~4.2, possibly):
>>   https://bugzilla.kernel.org/show_bug.cgi?id=196157
>>   https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1698118
>  
> indeed!

Not sure if it makes sense to also file a bug in the debian bug tracker
about this...


>> Reducing the ram of the affected builders to 8GB and having more PAE
>> builders with lighter workloads might be a workaround that would get
>> better performance... while still testing 32/64-bit kernel
>> variation.
>
> we lack the diskspace to do so.

Then it might still get better performance to lower the PAE builders to
only use 8GB of ram, even if that means running fewer jobs in
parallel...


>> Running a linux 4.1 kernel from snapshot.debian.org might be another way
>> to test the issue, even if not running long-term.
>
> yeah.

Now that I think about it, switching back to a 3.16.x kernel from jessie
for the PAE builders should be viable at least as long as jessie-lts is
around...


> another option is to just wait. :/

I suspect that *might* be an infinite wait; I get the impression this is
a very low-priority issue upstream, and it would take some active
attempt to fix it upstream...


live well,
  vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/qa-jenkins-dev/attachments/20170917/f670e50f/attachment.sig>