public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ken Moffat <zarniwhoop@ntlworld.com>
To: linux-kernel@vger.kernel.org
Subject: system apparently coming to its knees with -rc7
Date: Sun, 3 Nov 2013 20:14:57 +0000	[thread overview]
Message-ID: <20131103201457.GA26797@milliways> (raw)

[-- Attachment #1: Type: text/plain, Size: 1695 bytes --]

 I'm not sure how best to describe this.  I've got a 4-processor AMD
phenom desktop (single socket, 8GB memory, 16GB swap available)
running 64-bit x86_64.  It was building some desktop packages using
'make -j4', doing a backup (rsync over nfs3, from fcrontab), with
firefox and some urxvt terms open.  My wm is icewm which has taskbar
windows for both net activity and cpu activity.

 Normally, the cpu activity window is green on black (bottom quarter
during configure and make install, and up to all four quarters during
make -j4).  I noticed that the bottom quarter had turned red, with
black above it.  At this point the system was still responding.  I
fired up 'top', that showed me that kswapd, rsync, and cc1 were each
using more than 99%, and only 1 cc1 process appeared to be running.
Gradually, the cpu indicator panel turned 3/4 red.

 The box was not swapping according to 'top' (still a little memory
available).  After some time I killed the build with with Ctrl-C.
'top' still showed cc1 using more than 99%.  I got a trace with
Sysrq-T and decided to reboot.

 Shut down the terms and the browser without difficulty, then tried
to leave X with ctrl-alt-backspace (call me a traditionalist).

 Nothing happened, except that the mouse pointer disappeared and the
desktop clock froze.  Possibly it _was_ going back to a tty.  After
about 10 seconds 1 got as far as MagicSysRQ-S and the screen went
black.  Unmounted, rebooted.

 I'm attaching gzipped versions of the part of the syslog that shows
the trace, and my config - the trace expands to over 300K.  System
is recent linuxfromscratch (gcc-4.8.1) but with make-4.0.

ĸen
-- 
das eine Mal als Tragödie, dieses Mal als Farce

[-- Attachment #2: syslog.gz --]
[-- Type: application/x-gunzip, Size: 31224 bytes --]

[-- Attachment #3: config.gz --]
[-- Type: application/x-gunzip, Size: 17064 bytes --]

                 reply	other threads:[~2013-11-03 20:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20131103201457.GA26797@milliways \
    --to=zarniwhoop@ntlworld.com \
    --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