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

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

Bug#866314: linux-image-4.9.0-3-686-pae: 100+ times slower disk writes on 4.x+/i386/16+RAM, compared to 3.x

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#866314: linux-image-4.9.0-3-686-pae: 100+ times slower disk writes on 4.x+/i386/16+RAM, compared to 3.x Salvatore Bonaccorso <carnil@debian.org> - 2021-05-02 11:50 +0200
    Bug#866314: linux-image-4.9.0-3-686-pae: 100+ times slower disk writes on 4.x+/i386/16+RAM, compared to 3.x Holger Levsen <holger@layer-acht.org> - 2021-05-03 13:40 +0200
      Bug#866314: linux-image-4.9.0-3-686-pae: 100+ times slower disk writes on 4.x+/i386/16+RAM, compared to 3.x Diederik de Haas <didi.debian@cknow.org> - 2022-06-01 01:40 +0200
        Processed: Re: Bug#866314: linux-image-4.9.0-3-686-pae: 100+  times slower disk writes on 4.x+/i386/16+RAM, compared to 3.x "Debian Bug Tracking System" <owner@bugs.debian.org> - 2022-06-01 01:40 +0200
        Bug#866314: linux-image-4.9.0-3-686-pae: 100+ times slower disk writes on 4.x+/i386/16+RAM, compared to 3.x Holger Levsen <holger@layer-acht.org> - 2022-06-01 14:20 +0200
          Bug#866314: linux-image-4.9.0-3-686-pae: 100+ times slower disk writes on 4.x+/i386/16+RAM, compared to 3.x Diederik de Haas <didi.debian@cknow.org> - 2022-06-01 15:00 +0200
            Bug#866314: linux-image-4.9.0-3-686-pae: 100+ times slower disk writes on 4.x+/i386/16+RAM, compared to 3.x Holger Levsen <holger@layer-acht.org> - 2022-06-01 15:20 +0200
              Bug#866314: linux-image-4.9.0-3-686-pae: 100+ times slower disk writes on 4.x+/i386/16+RAM, compared to 3.x Diederik de Haas <didi.debian@cknow.org> - 2022-06-01 16:10 +0200
                Bug#866314: linux-image-4.9.0-3-686-pae: 100+ times slower disk writes on 4.x+/i386/16+RAM, compared to 3.x Holger Levsen <holger@layer-acht.org> - 2022-06-01 16:20 +0200
                  Bug#866314: linux-image-4.9.0-3-686-pae: 100+ times slower disk writes on 4.x+/i386/16+RAM, compared to 3.x Diederik de Haas <didi.debian@cknow.org> - 2022-06-01 16:50 +0200
        Bug#866314: linux-image-4.9.0-3-686-pae: 100+ times slower disk writes on 4.x+/i386/16+RAM, compared to 3.x Diederik de Haas <didi.debian@cknow.org> - 2022-12-11 15:10 +0100
          Processed: Re: Bug#866314: linux-image-4.9.0-3-686-pae: 100+  times slower disk writes on 4.x+/i386/16+RAM, compared to 3.x "Debian Bug Tracking System" <owner@bugs.debian.org> - 2022-12-11 15:10 +0100

#71107 — Bug#866314: linux-image-4.9.0-3-686-pae: 100+ times slower disk writes on 4.x+/i386/16+RAM, compared to 3.x

Hi Holger,

On Wed, Jun 28, 2017 at 07:53:48PM +0000, Holger Levsen wrote:
> package: linux-image-4.9.0-3-686-pae
> version: 4.9.30-2+deb9u2
> # severity: important ?
> forwarded: https://bugzilla.kernel.org/show_bug.cgi?id=196157
> 
> Hi,
> 
> upon upgrading the i386 build nodes for tests.reproducible-builds.org to Stretch
> I noticed a huge performance loss, which I could "fix" by installing 
> linux-image-4.9.0-3-amd64:amd64 (version 4.9.30-2+deb9u2 too).
> (which btw is a nice example for Multiarchs's usefulness…)
> 
> Today Vagrant pointed me to https://bugzilla.kernel.org/show_bug.cgi?id=196157
> which is the upstream issue tracking this.
> 
> I'm filing this bug for the benefit of other Debian users and for myself to
> benefit from the BTS subscription and tracking features…
> 
> We want to run half of our i386 build nodes with a 32 bit kernel and the other
> half with an 64 bit kernel to test reproducibility under this variation, so
> I'm really looking forward to see this bug fixed soon. Other people can
> probably just keep running the amd64 kernel, thus I've decided for normal 
> severity for this issue.
> 
> Thanks for maintaining src:linux!

Doing some maintenance on open bugs for src:linux to bring unnecessary
still open bugs down, this one appeared as well on the radar of older
bugs for older kernels.

Do you still want to keep this bug open for some reason, or should we
close it? I'm fine either way, but here I wanted to ask epxlicitly, as
there was still some movements up to february 2020 in the referenced
upstream report.

I just wonder if it will be worth off, but maybe yes.

Regards,
Salvatore

[toc] | [next] | [standalone]

#71199

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

Hi Salvatore,

On Sun, May 02, 2021 at 11:39:05AM +0200, Salvatore Bonaccorso wrote:
> Doing some maintenance on open bugs for src:linux to bring unnecessary
> still open bugs down, this one appeared as well on the radar of older
> bugs for older kernels.
> 
> Do you still want to keep this bug open for some reason, or should we
> close it? I'm fine either way, but here I wanted to ask epxlicitly, as
> there was still some movements up to february 2020 in the referenced
> upstream report.
> 
> I just wonder if it will be worth off, but maybe yes.

I suppose it might be time to reduce memory on our i386 nodes to 15gb and
see how that goes. We're still seeing our i386 nodes hanging basically
every other day and I hope reducing memory will fix that.

I suppose it would be nice to keep this bug open but I don't care that much
either way. I understand i386 with lots of memory is super uncommon.

cc:ing Mattia for his opinion on this.


-- 
cheers,
	Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

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

#75409

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

Control: tag -1 moreinfo

On Mon, 3 May 2021 11:26:55 +0000 Holger Levsen <holger@layer-acht.org> wrote:
> Hi Salvatore,
> 
> On Sun, May 02, 2021 at 11:39:05AM +0200, Salvatore Bonaccorso wrote:
> > Do you still want to keep this bug open for some reason, or should we
> > close it? I'm fine either way, but here I wanted to ask epxlicitly, as
> > there was still some movements up to february 2020 in the referenced
> > upstream report.
> > 
> > I just wonder if it will be worth off, but maybe yes.
> 
> I suppose it might be time to reduce memory on our i386 nodes to 15gb and
> see how that goes. We're still seeing our i386 nodes hanging basically
> every other day and I hope reducing memory will fix that.
> 
> I suppose it would be nice to keep this bug open but I don't care that much
> either way. I understand i386 with lots of memory is super uncommon.
> 
> cc:ing Mattia for his opinion on this.

What's the current status wrt this bug?

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

#75410 — Processed: Re: Bug#866314: linux-image-4.9.0-3-686-pae: 100+ times slower disk writes on 4.x+/i386/16+RAM, compared to 3.x

Processing control commands:

> tag -1 moreinfo
Bug #866314 [src:linux] linux-image-4.9.0-3-686-pae: 100+ times slower disk writes on 4.x+/i386/16+RAM, compared to 3.x
Added tag(s) moreinfo.

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

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

#75422

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

On Wed, Jun 01, 2022 at 01:27:32AM +0200, Diederik de Haas wrote:
> What's the current status wrt this bug?

we downgraded the memory of our nodes to 8gb to work around the issue...


-- 
cheers,
	Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

So what CAN we actually do? Well, individual decisions (eating less meat,
taking public transport, buying less fast fashion) are all important, but we
also need to change the system. As you may know, just 100 companies are
responsible for 71% of global emissions. (@JessicaTheLaw)
https://www.theguardian.com/sustainable-business/2017/jul/10/100-fossil-fuel-companies-investors-responsible-71-global-emissions-cdp-study-climate-change

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

#75424

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

On Wednesday, 1 June 2022 14:09:28 CEST Holger Levsen wrote:
> On Wed, Jun 01, 2022 at 01:27:32AM +0200, Diederik de Haas wrote:
> > What's the current status wrt this bug?
> 
> we downgraded the memory of our nodes to 8gb to work around the issue...

Andrew Morton said in https://bugzilla.kernel.org/show_bug.cgi?id=196157#c21 :
"People are still hurting from this.  It does seem a pretty major
regression for highmem machines.

I'm surprised that we aren't hearing about this from distros.  Maybe it
only affects a subset of highmem machines?

Anyway, can we please take another look at it?  Seems that we messed up
highmem dirty pagecache handling in the 4.2 timeframe."

I didn't see a mention of this bug in that upstream bug report.

A mention of "the i386 build nodes for tests.reproducible-builds.org" may also 
help to increase the priority for the upstream devs.
And if it's possible to equip one of the machines with 16G again and provide 
access to the upstream devs to that machine, that will likely increase the 
chances that something may happen.

So it would be really helpful if this would be added to the upstream bug 
report. Otherwise it's extremely unlikely anything will change.

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

#75425

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

On Wed, Jun 01, 2022 at 02:53:06PM +0200, Diederik de Haas wrote:
> So it would be really helpful if this would be added to the upstream bug 
> report.

then please do so?!?


-- 
cheers,
	Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

Bottled water companies don't produce water, they produce plastic bottles.

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

#75426

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

On Wednesday, 1 June 2022 15:11:37 CEST Holger Levsen wrote:
> On Wed, Jun 01, 2022 at 02:53:06PM +0200, Diederik de Haas wrote:
> > So it would be really helpful if this would be added to the upstream bug
> > report.
> 
> then please do so?!?

And with that I've lost any motivation to further reduce the Debian kernel bug 
list. Let's keep this and other pointless bug open for ever.

Well done.

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

#75427

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

On Wed, Jun 01, 2022 at 04:01:10PM +0200, Diederik de Haas wrote:
> On Wednesday, 1 June 2022 15:11:37 CEST Holger Levsen wrote:
> > On Wed, Jun 01, 2022 at 02:53:06PM +0200, Diederik de Haas wrote:
> > > So it would be really helpful if this would be added to the upstream bug
> > > report.
> > then please do so?!?
> 
> And with that I've lost any motivation to further reduce the Debian kernel bug 
> list. Let's keep this and other pointless bug open for ever.
> Well done.

you seem to assume that I know how to report upstream bugs to the kernel.
yet I don't know.


-- 
cheers,
	Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

The past is over.

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

#75428

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

On Wednesday, 1 June 2022 16:15:51 CEST Holger Levsen wrote:
> you seem to assume that I know how to report upstream bugs to the kernel.
> yet I don't know.

https://bugzilla.kernel.org/show_bug.cgi?id=196157 is a (standard) Bugzilla 
instance where you could create an account if you don't have it and then add
your response to that bug.

Andrew Morton seems to prefer plain email and his' message can be found
on lore.kernel.org here: 
https://lore.kernel.org/linux-mm/20170622123736.1d80f1318eac41cd661b7757@linux-foundation.org/

That message also contains instructions at the bottom how to do it (properly).

If you have further questions, I'll do my best to answer them.

HTH,
  Diederik

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

#77578

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

Control: tag -1 -moreinfo

On Wednesday, 1 June 2022 01:27:32 CET Diederik de Haas wrote:
> What's the current status wrt this bug?

Just saw upstream commit 630dc25e43dacfb5af94cd41532e77c47ec1caff which should 
become part of 6.1-rc9 and/or 6.1 and it would be interesting to know if that 
would make a difference wrt this bug.

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

#77579 — Processed: Re: Bug#866314: linux-image-4.9.0-3-686-pae: 100+ times slower disk writes on 4.x+/i386/16+RAM, compared to 3.x

Processing control commands:

> tag -1 -moreinfo
Bug #866314 [src:linux] linux-image-4.9.0-3-686-pae: 100+ times slower disk writes on 4.x+/i386/16+RAM, compared to 3.x
Removed tag(s) moreinfo.

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

[toc] | [prev] | [standalone]

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

csiph-web