From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@transmeta.com>, andrea@suse.de
Subject: pre5 VM livelock
Date: Tue, 30 Oct 2001 16:20:25 -0500 [thread overview]
Message-ID: <3BDF1999.CAF5D101@mandrakesoft.com> (raw)
2.4.14-pre5 was looking very nice on my alpha, doing RPM builds. It
seems to swap only when it needs to, and subjectively, performance
appears better.
However at this very moment, the kernel is livelocked. I can type on
console and do sysrq to your heart's content... I can even sysrq-s and
sync successfully. But no processing occurs. I can ping, but two ssh
sessions are frozen.
Key symptoms: Free swab 0Kb according to sysrq-m, and several processes
in run state according to sysrq-t.
Let me know if I should poke at this alpha further before rebooting.
further info:
free pages: 2560 kb (0kb highmem)
( active 2422 inactive 38578 free 320 )
swap cache: add 850670 delete 850666 find 323063/440091 race 1+0
free swap: 0kb
49074 pages of ram
786 free pages
1299 reserved pages
2683 pages shared
4 pages swap cached
4 pages in page table cache
buffer memory: 168kb
This behavior is reproducible, I am pretty sure.
--
Jeff Garzik | Only so many songs can be sung
Building 1024 | with two lips, two lungs, and one tongue.
MandrakeSoft | - nomeansno
next reply other threads:[~2001-10-30 21:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-30 21:20 Jeff Garzik [this message]
2001-10-30 22:46 ` pre5 VM livelock Andrea Arcangeli
2001-10-30 22:49 ` Linus Torvalds
2001-10-30 23:18 ` Andrea Arcangeli
2001-10-30 23:21 ` Linus Torvalds
2001-10-30 23:43 ` Jeff Garzik
2001-10-31 0:10 ` Linus Torvalds
2001-10-31 9:42 ` Marcelo Tosatti
2001-10-31 11:34 ` Jeff Garzik
2001-10-31 10:23 ` Marcelo Tosatti
2001-10-30 23:40 ` Linus Torvalds
2001-10-30 23:45 ` Jeff Garzik
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=3BDF1999.CAF5D101@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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