All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kurt Roeckx <Q@ping.be>
To: selinux@tycho.nsa.gov
Subject: Weird problem using latest kernel.
Date: Sun, 8 Jun 2003 13:46:17 +0200	[thread overview]
Message-ID: <20030608114617.GA4456@ping.be> (raw)

I've been using 2.4.21-rc2, without patch, for a while without
problems.  Then I switched to 2.4.21-rc7 with the patch for rc6
found on http://www.coker.com.au/selinux/kern/

Using that, the first night something must have gone wrong using
updatedb, it was still running when I got back home that night,
which is ore than 12 hours after it starts.  You could hear the
hard disk going, the load was around 8, it was very unresponsive.
I just rebooted it.

The next day I had no problems, but the day after that I went to
see before I went to work and it was again still running.  This
time I started vmstat to have an idea of what's going on, and it
seems to be very heavily using the swap for some reason.

I killed updatedb and all it's children, but that didn't seem to
have helped, so I rebooted again.

After asking other people who run rc7, and searching list, nobody
else seems to have a problem, so I assumed it had to do something
with the lsm patch.  So I removed the patch and made a new
kernel.

I have no problems for 2 nights now with plain 2.4.21-rc7, didn't
have any problem with plain rc2 either, but things really don't
work very well with the lsm patched.


Kurt


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

             reply	other threads:[~2003-06-08 11:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-08 11:46 Kurt Roeckx [this message]
2003-06-08 13:25 ` Weird problem using latest kernel Russell Coker
2003-06-10 21:32   ` Kurt Roeckx

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=20030608114617.GA4456@ping.be \
    --to=q@ping.be \
    --cc=selinux@tycho.nsa.gov \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.