From: "Sergey S. Kostyliov" <rathamahata@php4.ru>
To: linux-kernel@vger.kernel.org
Cc: Anton Kovalenko <anton@megashop.ru>
Subject: 2.6.X kernel memory leak? (was: Re: 2.6.1 IO lockup on SMP systems)
Date: Thu, 8 Apr 2004 13:08:43 +0400 [thread overview]
Message-ID: <200404081308.43056.rathamahata@php4.ru> (raw)
In-Reply-To: <200402281756.08260.rathamahata@php4.ru>
Hello all,
On Saturday 28 February 2004 17:56, Sergey S. Kostyliov wrote:
> On Thursday 26 February 2004 23:03, Andrew Morton wrote:
> <cut>
> > OK, thanks. Is there any possibility that you can run without iptables for
> > a while, see if that fixes it?
>
> I recompiled 2.6.3 without iptables support, unfortunately it doesn't
> solve the problem, machine still hangs.
It looks like problem hasn't gone away in the last kernels. The visible
symptoms haven't changed: machine is pingable, tcp ports which were in
LISTEN state remains to be in LISTEN after lockup, nothing else.
The last one is for different machine than in my previous reports,
so I suspect this is not a hardware issue. Kernel is 2.6.5-aa3 but
I believe Andrea's changes is not related to this problem.
sysrq-M
http://sysadminday.org.ru/2.6.X-lockup/terror/20040408/sysrq-M
sysrq-T
http://sysadminday.org.ru/2.6.X-lockup/terror/20040408/sysrq-T
.config
http://sysadminday.org.ru/2.6.X-lockup/terror/.config
`lspci -vv'
http://sysadminday.org.ru/2.6.X-lockup/terror/lspci_-vv
`dmesg'
http://sysadminday.org.ru/2.6.X-lockup/terror/dmesg
/etc/fstab
http://sysadminday.org.ru/2.6.X-lockup/terror/fstab
--
Best regards,
Sergey S. Kostyliov <rathamahata@php4.ru>
Public PGP key: http://sysadminday.org.ru/rathamahata.asc
next prev parent reply other threads:[~2004-04-08 9:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-31 16:40 2.6.1 IO lockup on SMP systems Sergey S. Kostyliov
2004-02-01 0:17 ` Andrew Morton
2004-02-21 16:45 ` Sergey S. Kostyliov
2004-02-21 19:30 ` Andrew Morton
2004-02-22 17:39 ` Alexander Y. Fomichev
2004-02-23 17:27 ` Sergey S. Kostyliov
2004-02-23 21:30 ` Mike Fedyk
2004-02-24 11:56 ` Sergey S. Kostyliov
2004-02-23 22:26 ` Andrew Morton
2004-02-24 7:23 ` Marcelo Tosatti
2004-02-24 6:53 ` Andrew Morton
2004-02-24 11:54 ` Sergey S. Kostyliov
2004-02-26 12:19 ` Sergey S. Kostyliov
2004-02-26 12:53 ` Andrew Morton
2004-02-26 13:11 ` Andrew Morton
2004-02-26 14:37 ` Dave Jones
2004-02-26 15:37 ` Arjan van de Ven
2004-02-26 14:30 ` Sergey S. Kostyliov
2004-02-26 20:03 ` Andrew Morton
2004-02-28 14:56 ` Sergey S. Kostyliov
2004-04-08 9:08 ` Sergey S. Kostyliov [this message]
2004-04-09 7:17 ` 2.6.X kernel memory leak? Sergey S. Kostyliov
2004-04-09 9:09 ` Andrew Morton
2004-04-09 12:15 ` Sergey S. Kostyliov
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=200404081308.43056.rathamahata@php4.ru \
--to=rathamahata@php4.ru \
--cc=anton@megashop.ru \
--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