From: Kurt Roeckx <Q@ping.be>
To: Russell Coker <russell@coker.com.au>
Cc: selinux@tycho.nsa.gov
Subject: Re: Weird problem using latest kernel.
Date: Tue, 10 Jun 2003 23:32:06 +0200 [thread overview]
Message-ID: <20030610213206.GA4837@ping.be> (raw)
In-Reply-To: <200306082325.13088.russell@coker.com.au>
On Sun, Jun 08, 2003 at 11:25:13PM +1000, Russell Coker wrote:
> On Sun, 8 Jun 2003 21:46, Kurt Roeckx wrote:
> > 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.
>
> I believe that the bug is in the main kernel code. I have not reported this
> to the linux-kernel list because I don't have enough hard evidence, and I
> expect that lots of other people have discovered the same bug. If you choose
> to post to linux-kernel then please feel free to quote my message or provide
> the URL for the SE Linux list archives.
Just for update, the current uptime is just over 4 days now
without any problems at all running on a plain 2.4.21-rc7.
I really believe the problem is in the patch.
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.
prev parent reply other threads:[~2003-06-10 21:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-08 11:46 Weird problem using latest kernel Kurt Roeckx
2003-06-08 13:25 ` Russell Coker
2003-06-10 21:32 ` Kurt Roeckx [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=20030610213206.GA4837@ping.be \
--to=q@ping.be \
--cc=russell@coker.com.au \
--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.