From: Henry <henry@borg.metroweb.co.za>
To: Andrew Morton <andrewm@uow.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: OOPS (kswapd) in 2.4.5 and 2.4.6
Date: Sun, 8 Jul 2001 13:08:22 +0200 [thread overview]
Message-ID: <01070813155100.04666@borg> (raw)
In-Reply-To: <01070516412506.06182@borg> <01070711384402.00793@borg> <3B46DC5C.76A3D7A5@uow.edu.au>
In-Reply-To: <3B46DC5C.76A3D7A5@uow.edu.au>
>
> No, his oops was a bad inode state while trying to
> release unused NFS client inodes. Different bug :)
>
New development. No oops, but apache eventually crashed with the same
error message 'semget - no space left on device'. So,... either this
was a coincidence (ie, with the kernel issue) and a problem exists with
Apache/1.3.19 Ben-SSL/1.42 (Unix)/PHP which requires a reboot to fix,
or something else is happening. Could there be a link between the
previous kernel bug and the apache issue? Do you have any idea what
the error message means, or what it's related to? Previously (when the
oops was prevalent), the oops would occur at roughly the same time as
the apache problem - which could mean everything, or nothing at all...
sigh.
Cheers
Henry
prev parent reply other threads:[~2001-07-08 11:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-05 14:03 OOPS (kswapd) in 2.4.5 and 2.4.6 Henry
2001-07-05 16:53 ` Wayne Whitney
2001-07-05 17:09 ` Henry
2001-07-06 5:59 ` Henry
2001-07-06 8:35 ` Andrew Morton
2001-07-06 10:31 ` Henry
2001-07-07 6:03 ` Henry
2001-07-07 8:07 ` Andrew Morton
2001-07-07 9:33 ` Henry
2001-07-07 9:54 ` Andrew Morton
2001-07-08 11:08 ` Henry [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=01070813155100.04666@borg \
--to=henry@borg.metroweb.co.za \
--cc=andrewm@uow.edu.au \
--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