From: Genevieve Aubut <gaubut@altersys.com>
To: "'Linux-MM@kvack.org'" <Linux-MM@kvack.org>
Subject: Linux memory problem with TIS firewall
Date: Wed, 30 Sep 1998 15:22:10 -0400 [thread overview]
Message-ID: <01BDEC86.186F1DB0@gate.altersys.com> (raw)
We have installed a TIS firewall on a Red Hat Linux (Kernel version 2.0.34) computer.
Since we installed it, the computer crashes once or twice a day with this error:
- Unable to handle kernel paging request at virtual address "xxx" for example e03b653c
and displays a list of addresses and stack contents as well as :
- Process http-gw (pid: ....)
and at the end the message:
- kfree of non-kmalloced memory ....
The computer is a Pentium MMX 166 with 32 Mb of memory.
The hard disk contains a swap partition of 400 Mb in a 2.8 Gb.
The only application running is the TIS firewall. We downloaded
the most recent version from your ftp site last week.
System Administrator
Altersys Inc.
Montreal - Canada
(450) 674-7774 ext. 225
--
This is a majordomo managed list. To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org
next reply other threads:[~1998-09-30 19:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-30 19:22 Genevieve Aubut [this message]
1998-10-01 7:20 ` Rik van Riel
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=01BDEC86.186F1DB0@gate.altersys.com \
--to=gaubut@altersys.com \
--cc=Linux-MM@kvack.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