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

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

Bug#960674: golang-go: "fatal error: gc_trigger underflow" on mipsel

Back to article view | Back to linux.debian.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

  Bug#960674: golang-go: "fatal error: gc_trigger underflow" on mipsel Adrian Bunk <bunk@debian.org> - 2020-06-08 19:20 +0200
    Processed: Re: Bug#960674: golang-go: "fatal error: gc_trigger  underflow" on mipsel "Debian Bug Tracking System" <owner@bugs.debian.org> - 2020-06-08 19:20 +0200
    Bug#962485: Please revert CONFIG_MIPS_O32_FP64_SUPPORT change mipsel YunQiang Su <syq@debian.org> - 2021-03-25 08:10 +0100
      Bug#962485: Please revert CONFIG_MIPS_O32_FP64_SUPPORT change mipsel Bastian Blank <waldi@debian.org> - 2021-03-25 09:10 +0100

#67254 — Bug#960674: golang-go: "fatal error: gc_trigger underflow" on mipsel

Control: clone -1 -2
Control: reassign -2 src:linux 4.19.118-1
Control: found -2 5.4.6-1
Control: notforwarded -2
Control: severity -2 serious
Control: retitle -2 Please revert CONFIG_MIPS_O32_FP64_SUPPORT change

On Fri, May 29, 2020 at 11:03:14PM +0200, Aurelien Jarno wrote:
> On 2020-05-28 09:04, YunQiang Su wrote:
> > Adrian Bunk <bunk@debian.org> 于2020年5月21日周四 下午3:40写道：
> > > On Thu, May 21, 2020 at 06:41:34AM +0800, YunQiang Su wrote:
> > > > Adrian Bunk <bunk@debian.org> 于2020年5月21日周四 上午4:44写道：
> > > > > On Tue, May 19, 2020 at 11:43:30AM +0800, Shengjing Zhu wrote:
> > > > > >
> > > > > > FTR, after giving back golang-1.14 mipsel several times, it's finally
> > > > > > built, by a longson builder.
> > > > > > So I guess it only occurs on octeon. Since the porterbox eller is also
> > > > > > octeon, it also can't build any go program.
> > > > >
> > > > > On eller golang-1.14 fails to build both in sid and buster chroots.
> > > > >
> > > > > golang-1.11 also fails to build in a buster chroot with floating point
> > > > > test errors.
> > > > >
> > > > > golang-1.14 gets unbroken by GOMIPS=softfloat.
> > > > >
> > > > > The only kernel configuration change on eller in the buster point
> > > > > release is CONFIG_MIPS_O32_FP64_SUPPORT=y, everything observed would
> > > > > make sense if the problem is that golang-1.11 and golang-1.14 are
> > > > > not compatible with CONFIG_MIPS_O32_FP64_SUPPORT.
> > > >
> > > > It is just support O32_FP64. I don't expect it will have any effect.
> > > > Since currently, the toolchain/libraries are all FPXX.
> > >
> > > Only the gcc/binutils toolchain/libraries or also the Go toolchain?
> > 
> > you are right. the current golang still output FP32 object...
> > So, we think that it is buggy.
> > 
> > Since Loongson CPU has some strange behaviour, it even can work...
> > Let's try to patch golang to support FPXX or FP64.
> > 
> > https://github.com/golang/go/issues/39289
> 
> That's probably a solution for bullseye/sid, however we can't backport
> such changes and rebuild the go world in buster. I therefore think that
> for buster the kernel change has to be reverted.

What is clear at this point is that the kernel change should be reverted
in buster since it causes a regression (including build failures on 
buildds). I am cloning this bug for a revert in the kernel of
https://salsa.debian.org/kernel-team/linux/-/commit/947fbc66183d022fe3de7871dfb262d2b87af826

I am marking the version in bullseye as found since we might run into 
the same problem again when buster DSAs will be built on machines 
running the bullseye kernel after the release of bullseye. It might be 
possible to mitigate this problem (e.g. in the kernel or by keeping some 
buildd running with the buster kernel), but without an open bug this 
issue might get forgotten and then resurface after the bullseye release.

> Aurelien

cu
Adrian

[toc] | [next] | [standalone]

#67255 — Processed: Re: Bug#960674: golang-go: "fatal error: gc_trigger underflow" on mipsel

Processing control commands:

> clone -1 -2
Bug #960674 [golang-go] golang-go: "fatal error: gc_trigger underflow" on mipsel
Bug 960674 cloned as bug 962485
> reassign -2 src:linux 4.19.118-1
Bug #962485 [golang-go] golang-go: "fatal error: gc_trigger underflow" on mipsel
Bug reassigned from package 'golang-go' to 'src:linux'.
No longer marked as found in versions golang-defaults/2:1.14~1.
Ignoring request to alter fixed versions of bug #962485 to the same values previously set
Bug #962485 [src:linux] golang-go: "fatal error: gc_trigger underflow" on mipsel
Marked as found in versions linux/4.19.118-1.
> found -2 5.4.6-1
Bug #962485 [src:linux] golang-go: "fatal error: gc_trigger underflow" on mipsel
Marked as found in versions linux/5.4.6-1.
> notforwarded -2
Bug #962485 [src:linux] golang-go: "fatal error: gc_trigger underflow" on mipsel
Unset Bug forwarded-to-address
> severity -2 serious
Bug #962485 [src:linux] golang-go: "fatal error: gc_trigger underflow" on mipsel
Severity set to 'serious' from 'important'
> retitle -2 Please revert CONFIG_MIPS_O32_FP64_SUPPORT change
Bug #962485 [src:linux] golang-go: "fatal error: gc_trigger underflow" on mipsel
Changed Bug title to 'Please revert CONFIG_MIPS_O32_FP64_SUPPORT change' from 'golang-go: "fatal error: gc_trigger underflow" on mipsel'.

-- 
960674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960674
962485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962485
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

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

#69957 — Bug#962485: Please revert CONFIG_MIPS_O32_FP64_SUPPORT change mipsel

YunQiang Su <syq@debian.org> 于2021年2月20日周六 下午2:19写道：
>
> https://lore.kernel.org/linux-mips/20210220061635.9976-1-yunqiang.su@cipunited.com/T/#u
> This patch for kernel can fix this problem.
>
> Let's wait for the reply of kernel upstream community.
>

the newest version of this patch:

https://patchwork.kernel.org/project/linux-mips/patch/20210322015902.18451-1-yunqiang.su@cipunited.com/

Is it possible for Debian's kernel to apply this patch?

> Bastian Blank <waldi@debian.org> 于2021年2月11日周四 下午2:57写道：
> >
> > Moin
> >
> > On Thu, Feb 11, 2021 at 10:15:02AM +0800, YunQiang Su wrote:
> > > > Could the mips porters comment on this? Given that we're close to the release
> > > > of bullseye, I'm not convinced it's a good idea to change this now.
> >
> > This option is also a dependency of several types of CPU support.  So it
> > might not be feasable to disable.
> >
> > > Yes. It will be a problem to run with buster's golang program on
> > > bullseys's kernel.
> > > Let's have another way to get this problem sloved without revert this changes.
> >
> > Sure, by discontinuing support for go on mips for example.
> >
> > > Maybe detect the golang applications and run them in FP32 mode?
> >
> > The kernel already does.  But it seems go decided to set the FPXX marker
> > on it's objects.  See https://github.com/golang/go/issues/39435
> >
> > Bastian
> >
> > --
> > Captain's Log, star date 21:34.5...
> >

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

#69960 — Bug#962485: Please revert CONFIG_MIPS_O32_FP64_SUPPORT change mipsel

On Thu, Mar 25, 2021 at 03:00:06PM +0800, YunQiang Su wrote:
> YunQiang Su <syq@debian.org> 于2021年2月20日周六 下午2:19写道：
> > https://lore.kernel.org/linux-mips/20210220061635.9976-1-yunqiang.su@cipunited.com/T/#u
> > This patch for kernel can fix this problem.
> > Let's wait for the reply of kernel upstream community.
> the newest version of this patch:
> https://patchwork.kernel.org/project/linux-mips/patch/20210322015902.18451-1-yunqiang.su@cipunited.com/
> Is it possible for Debian's kernel to apply this patch?

Get it applied via stable@kernel.org.

And please fix your MUA to not produce TOFU.

Bastian

-- 
Killing is stupid; useless!
		-- McCoy, "A Private Little War", stardate 4211.8

[toc] | [prev] | [standalone]

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

csiph-web