2.6.X kernel memory leak? (was: Re: 2.6.1 IO lockup on SMP systems)

[Sergey S. Kostyliov]

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@xxxxxxx>
                   Public PGP key: http://sysadminday.org.ru/rathamahata.asc
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/