public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Sergey S. Kostyliov" <rathamahata@php4.ru>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, anton@megashop.ru
Subject: Re: 2.6.X kernel memory leak?
Date: Fri, 9 Apr 2004 16:15:04 +0400	[thread overview]
Message-ID: <200404091615.04340.rathamahata@php4.ru> (raw)
In-Reply-To: <20040409020903.0897857d.akpm@osdl.org>

Hello Andrew,

On Friday 09 April 2004 13:09, Andrew Morton wrote:
> "Sergey S. Kostyliov" <rathamahata@php4.ru> wrote:
> >
> > And here is part of sysrq-T for the third machine, which have just locked up,
> >  kernel is 2.6.5-rc3-aa2.
> 
> It does look like a kernel memory leak, but it's not into slab.
> 
> You've disabled iptables.  Possibly there's a leak in a device driver? 
> Which drivers are in regular use there?  What are you using for those
> hardware RAID controllers?

I've seen this kind of lockup (according to sysrq-T) on different boxes:

1) ope
	RAID:		mylex 352
	drivers:	e100, dac960
	.config:	http://sysadminday.org.ru/2.6.1-io_lockup/ope/.config

2) terror
	RAID:		megaraid 320-2
	drivers:	e1000, megaraid2
	.config:	http://sysadminday.org.ru/2.6.X-lockup/terror/.config

3) mirror
	drivers:	e100, aic7xxx, md, netconsole
	.config:	http://sysadminday.org.ru/2.6.X-lockup/mirror/.config

I also saw the same symptoms on a fourth box, but I'm not shure about
this one because it didn't use to be attached to serial console at that time.

For this box:
	RAID:		Compaq smart 2
	drivers:	tlan,epic100,cpqarray

-- 
                   Best regards,
                   Sergey S. Kostyliov <rathamahata@php4.ru>
                   Public PGP key: http://sysadminday.org.ru/rathamahata.asc

      reply	other threads:[~2004-04-09 12:19 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                         ` 2.6.X kernel memory leak? (was: Re: 2.6.1 IO lockup on SMP systems) Sergey S. Kostyliov
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 [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=200404091615.04340.rathamahata@php4.ru \
    --to=rathamahata@php4.ru \
    --cc=akpm@osdl.org \
    --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