public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Andries.Brouwer@cwi.nl
Cc: linux-kernel@vger.kernel.org
Subject: Re: a Linux swap storm
Date: Mon, 08 May 2006 05:23:19 +0200	[thread overview]
Message-ID: <1147058599.7584.9.camel@homer> (raw)
In-Reply-To: <200605071931.k47JVbs18224@apps.cwi.nl>

On Sun, 2006-05-07 at 21:31 +0200, Andries.Brouwer@cwi.nl wrote: 
> Earlier this evening I showed someone some pictures under X:
> 
> % display -size 300x300 *.jpg
> 
> (395 pictures, 315 MB). When display (from ImageMagick)
> started to repeat, I exited the program.
> At this moment the machine became unusable for twenty minutes
> of solid disk activity.
> No keystroke seen, not even the Ctrl-Alt-Backspace to kill X,
> or Ctrl-Alt-F1 to switch consoles, no mouse movement seen,
> vmstat did not produce any output for twenty minutes.
> 
> The vmstat 5 output was
> 
> procs -----------memory---------- ---swap-- -----io---- --system-- ----cpu----
>  r  b   swpd   free   buff  cache   si   so    bi    bo   in    cs us sy id wa
> 
>  0  3 315728   3164   4424   3356  646  382   792   382 2425   182  0  5  0 95
>  1  1 316356   3856   4428   3572  454  366   507   366 2242   150  0  5  0 95
>  0  1 317540   3784   4456   3664  530  578   590   578 2403   179  0  7  0 93
>  0  1 306740   4240   4524   5372 127013 49878 129427 50061 405016 32901  0  4  0 95
>  1  1 306712   3992   4536   5372   30    0    30     3  450   122  2  1 94  2
>  0  0 306692   4016   4548   5372   18    0    18     3  402   134  2  2 96  1
>  0  0 306692   4016   4560   5372    0    0     0     3  257    35  1  1 98  0

This is after ImageMagic exited?  If so, and you don't have a userland
hog sitting on that memory, I'd suggest posting /proc/meminfo and any
part of /proc/slabinfo showing large numbers of allocations.  (if you
can repeat with latest vanilla kernel that is)

> The machine is vanilla 2.6.14, 256MB, 550MB swap.
> 
> % rpm -qf `which X`
> xorg-x11-server-6.8.2-100
> 
> I wonder what precisely happened. Is this an X bug? Or a kernel bug?
> The effect is reproducible.

I'd lean toward kernel.  If it was thrashing so hard that the box became
a doorstop for 20 minutes, seems to me that's a fine description of oom,
so somebody should have been killed.  Does SysRq-M work during the
seizure?

-Mike


      parent reply	other threads:[~2006-05-08  3:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-07 19:31 a Linux swap storm Andries.Brouwer
2006-05-07 20:17 ` Jan Engelhardt
2006-05-07 20:37 ` Jesper Juhl
2006-05-08  3:23 ` Mike Galbraith [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1147058599.7584.9.camel@homer \
    --to=efault@gmx.de \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox