Wiadomość została wysłana pod nieaktywny adres poczty elektronicznej.
Jeżeli wiadomość miała tylko jednego adresata - nie zostanie odczytana!
Jeżeli adresatów było więcej, przynajmniej jeden z nich ma nieaktywną
skrzynkę.
Proszę sprawdzić listę adresatów.
Administrator
(Uwaga! Wiadomość wygenerowana automatycznie - prosimy nie odpowiadać.)
Re: SLES 11 SP3 problems
Leland Lucius
to:
LINUX-390
2014-03-13
20:39
Sent by:
Linux on 390 Port <[email protected]>
Please respond to Linux on 390 Port
Show
Details
Wanted to follow up.
Just today we FINALLY got the patched kernel
(3.0.101-0.15.1.6580.16.PTF.859225) from Novell (unbelievable saga!!!).
Changelog shows these changes:
* Tue Mar 11 2014 [email protected]
-
patches.suse/mm-vmscan-Update-rotated-and-scanned-when-force-reclaimed.patch
patches.suse/mm-vmscan-fix-endless-loop-in-kswapd-balancing.patch
patches.suse/mm-vmscan-Do-not-force-reclaim-file-pages-until-it-exceeds-anon.patch
patches.suse/mm-page-writeback.c-do-not-count-anon-pages-as-dirtyable-memory.patch
bnc#859225
I wonder why that differed from yours?
Leland
On 3/7/2014 4:51 PM, Marcy Cortes wrote:
> Ah thanks. And great to know that the future kernel doesn't suffer from
this!
>
> Good work!
>
>
>
> Marcy. Sent from my BlackBerry.
>
>
> ----- Original Message -----
> From: Leland Lucius [mailto:[email protected]]
> Sent: Friday, March 07, 2014 04:24 PM Central Standard Time
> To: [email protected] <[email protected]>
> Subject: Re: [LINUX-390] SLES 11 SP3 problems
>
> On 3/7/2014 3:57 PM, Marcy Cortes wrote:
>> weird, could the combo of the two of them be to blame?
> I'm sure they got it right. Especially since that bit of code has been
> effectively reverted in upstream as well at later kernel versions and
> why I wasn't able to make it happen in a 3.13.5 kernel.
>
> The method I used to try and figure out the cause probably changed
> things enough where the real problem was simply bypassed in some way. I
> can honestly say that the vmscan code is WAY over my head, so I was
> really just taking shots in the dark. Anything to try and push for a
> resolution to the problem.
>
> My method for recreating the problem was a little C program that simply
> allocated a bunch of memory over and over while I'm dropping the caches
> in another ssh session. Worked very reliably. But, with the patch
> reverted, I am no longer able to recreate the issue after many attempts.
>
> Thanks again,
>
> Leland
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO LINUX-390 or
visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> ----------------------------------------------------------------------
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO LINUX-390 or
visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> ----------------------------------------------------------------------
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
