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


Groups > linux.debian.kernel > #61275 > unrolled thread

linux/unstable failing to build on mips

Started byBen Hutchings <ben@decadent.org.uk>
First post2018-06-29 22:30 +0200
Last post2018-06-30 00:10 +0200
Articles 3 — 2 participants

Back to article view | Back to linux.debian.kernel


Contents

  linux/unstable failing to build on mips Ben Hutchings <ben@decadent.org.uk> - 2018-06-29 22:30 +0200
    Re: linux/unstable failing to build on mips Aurelien Jarno <aurelien@aurel32.net> - 2018-06-29 23:30 +0200
      Re: linux/unstable failing to build on mips Ben Hutchings <ben@decadent.org.uk> - 2018-06-30 00:10 +0200

#61275 — linux/unstable failing to build on mips

FromBen Hutchings <ben@decadent.org.uk>
Date2018-06-29 22:30 +0200
Subjectlinux/unstable failing to build on mips
Message-ID<w68bM-49k-9@gated-at.bofh.it>

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

The latest upload of linux to unstable has failed to build on mips
several times, with the failure mode being an apparent hang near the
end of the build process.  (Only one of these failed builds is visible
on buildd.debian.org now, but I think there were two previous
attempts.)

Has there been any attempt to diagnose the hang?  If so, does it seem
to be due to memory exhaustion and extreme swapping, or a software bug,
or some other cause?  Why hasn't it happened when building earlier
versions?

If it's memory exhaustion, are linux and other large packages being
blacklisted for these build hosts?

Ben.

-- 
Ben Hutchings
Sturgeon's Law: Ninety percent of everything is crap.

[toc] | [next] | [standalone]


#61277

FromAurelien Jarno <aurelien@aurel32.net>
Date2018-06-29 23:30 +0200
Message-ID<w697P-4IB-3@gated-at.bofh.it>
In reply to#61275

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

On 2018-06-29 21:29, Ben Hutchings wrote:
> The latest upload of linux to unstable has failed to build on mips
> several times, with the failure mode being an apparent hang near the
> end of the build process.  (Only one of these failed builds is visible
> on buildd.debian.org now, but I think there were two previous
> attempts.)

That's correct.

> Has there been any attempt to diagnose the hang?  If so, does it seem
> to be due to memory exhaustion and extreme swapping, or a software bug,
> or some other cause?  Why hasn't it happened when building earlier
> versions?

Yes, attempted has been made, but it's something difficult to diagnose,
the machine becoming unresponsive. make seems to leave many processes
hanging, causing extreme swapping, which doesn't work well on the
Octeons which swap over NFS. It seems to work fine on the Octeons which
swap over NFS.

mips being one of the few architectures with a buggy version of make, I
wonder if it's related to #890430 or #890309. I guess it's time to
revert to the make version in testing, which would also greatly improve,
or rather restore, the build time.

> If it's memory exhaustion, are linux and other large packages being
> blacklisted for these build hosts?

In the meantime, I have blacklisted linux on the Octeons swapping over
NFS. It should therefore build fine.

Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                 http://www.aurel32.net

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


#61279

FromBen Hutchings <ben@decadent.org.uk>
Date2018-06-30 00:10 +0200
Message-ID<w69Kx-5bB-3@gated-at.bofh.it>
In reply to#61277

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

On Fri, 2018-06-29 at 23:27 +0200, Aurelien Jarno wrote:
> On 2018-06-29 21:29, Ben Hutchings wrote:
[...]
> > Has there been any attempt to diagnose the hang?  If so, does it seem
> > to be due to memory exhaustion and extreme swapping, or a software bug,
> > or some other cause?  Why hasn't it happened when building earlier
> > versions?
> 
> Yes, attempted has been made, but it's something difficult to diagnose,
> the machine becoming unresponsive. make seems to leave many processes
> hanging, causing extreme swapping, which doesn't work well on the
> Octeons which swap over NFS. It seems to work fine on the Octeons which
> swap over NFS.

Swap over NFS is supposed to work since a few years ago, but I have my
doubts.  It is definitely a fragile feature.

[...]
> > If it's memory exhaustion, are linux and other large packages being
> > blacklisted for these build hosts?
> 
> In the meantime, I have blacklisted linux on the Octeons swapping over
> NFS. It should therefore build fine.

Thanks.

Ben.

-- 
Ben Hutchings
Sturgeon's Law: Ninety percent of everything is crap.

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web