[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#876035: marked as done (linux: i386: i/o with PAE kernels and > 8GB ram)

Your message dated Sat, 24 Apr 2021 14:30:30 +0200
with message-id <YIQPZiapCzUdssWn@eldamar.lan>
and subject line Re: Bug#876035: linux: i386: i/o with PAE kernels and > 8GB ram
has caused the Debian Bug report #876035,
regarding linux: i386: i/o with PAE kernels and > 8GB ram
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
876035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876035
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: linux
Severity: important
Version: 4.2
Tags: upstream
Control: affects -1 jenkins.debian.org
Control: block 875990 by -1

It seems that since linux 4.2, PAE systems suffer from severe i/o write
performance issues on systems with more than 8GB of ram. The bug was
probably there all along, but recent changes in the kernel made the
impacts more obvious...

  https://bugzilla.kernel.org/show_bug.cgi?id=196157
  https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1698118


A detailed description of the issue:

  http://flaterco.com/kb/PAE_slowdown.html


This can be seen on the reproducible builds i386 nodes, after upgrading
to stretch late june/early july 2017, there was a huge spike in iowait:

  https://jenkins.debian.net/munin/debian.net/profitbricks-build2-i386.debian.net/cpu.html
  https://jenkins.debian.net/munin/debian.net/profitbricks-build12-i386.debian.net/cpu.html


Switching to an amd64 kernel for hardware that supports it is an option
in many cases, though at least for reproducible builds purposes, doesn't
test reproducibility issues case by 32-bit vs. 64-bit kernel variations.


live well,
  vagrant

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
Hi Vagrant,

On Sun, Sep 17, 2017 at 10:16:56AM -0700, Vagrant Cascadian wrote:
> Source: linux
> Severity: important
> Version: 4.2
> Tags: upstream
> Control: affects -1 jenkins.debian.org
> Control: block 875990 by -1
> 
> It seems that since linux 4.2, PAE systems suffer from severe i/o write
> performance issues on systems with more than 8GB of ram. The bug was
> probably there all along, but recent changes in the kernel made the
> impacts more obvious...
> 
>   https://bugzilla.kernel.org/show_bug.cgi?id=196157
>   https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1698118
> 
> 
> A detailed description of the issue:
> 
>   http://flaterco.com/kb/PAE_slowdown.html
> 
> 
> This can be seen on the reproducible builds i386 nodes, after upgrading
> to stretch late june/early july 2017, there was a huge spike in iowait:
> 
>   https://jenkins.debian.net/munin/debian.net/profitbricks-build2-i386.debian.net/cpu.html
>   https://jenkins.debian.net/munin/debian.net/profitbricks-build12-i386.debian.net/cpu.html
> 
> 
> Switching to an amd64 kernel for hardware that supports it is an option
> in many cases, though at least for reproducible builds purposes, doesn't
> test reproducibility issues case by 32-bit vs. 64-bit kernel variations.

I'm going trough some older Debian bugreports. I think this one would
by now be sensible to close and doing so. Feel free to reopen if you
disagree, which us OTOH would help to clean up the massive amount of
open bugs in Debian with some age and no further conversations.

Regards,
Salvatore

--- End Message ---
Reply to: