From: Russell Coker <russell@coker.com.au>
To: Brian May <bam@snoopy.apana.org.au>, selinux@tycho.nsa.gov
Subject: Re: 2.4.20 stability issues
Date: Fri, 10 Jan 2003 09:57:07 +0100 [thread overview]
Message-ID: <200301100957.07668.russell@coker.com.au> (raw)
In-Reply-To: <20030110002718.GA922@snoopy.apana.org.au>
On Fri, 10 Jan 2003 01:27, Brian May wrote:
> It only happens after an uptime of several hours (if not days; it
> also depends if you count time in suspend mode or not), on my laptop
> computer.
rjc@lyta:/tmp$ uname -a
Linux lyta 2.4.20-se-r #1 Mon Dec 16 19:48:46 CET 2002 i686 unknown unknown
GNU/Linux
rjc@lyta:/tmp$ uptime
09:52:14 up 4 days, 9:11, 1 user, load average: 0.88, 1.33, 0.90
rjc@lyta:/tmp$
I have included a ReiserFS patch for performance that probably does not impact
this.
Let me know if you'd like a copy of the kernel deb that I use for testing and
I'll scp it to snoopy. I don't use FreeSWAN and I have it compiled to
auto-mount devfs, but apart from that it should work for you (it's the same
configuration we use for ns).
> I had no problems with 2.4.19, but as of 2.4.20 I seem to have
> encountered some weird stability issues that I cannot put my finger on.
[]
> So far this has only ever happened with 2.4.19, not 2.4.20. Weird.
???
--
http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/ My home page
--
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.
next prev parent reply other threads:[~2003-01-10 8:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 0:27 2.4.20 stability issues Brian May
2003-01-10 8:57 ` Russell Coker [this message]
2003-01-10 9:24 ` Brian May
2003-01-10 11:04 ` Russell Coker
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=200301100957.07668.russell@coker.com.au \
--to=russell@coker.com.au \
--cc=bam@snoopy.apana.org.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.