Subject: kern/35224: kernel hangs in mclpl after heavy net load in the sparc64 port (eventually also other ports)
To: None <kern-bug-people@netbsd.org, gnats-admin@netbsd.org,>
From: None <stephan.pietzko@uni-konstanz.de>
List: netbsd-bugs
Date: 12/09/2006 21:50:00
>Number:         35224
>Category:       kern
>Synopsis:       daemons freeze in mclpl condition after lot of net traffic from netbsd-2 through netbsd-3
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Dec 09 21:50:00 +0000 2006
>Originator:     Charlie Root
>Release:        NetBSD-3
>Organization:
        Admin of several NetBSD server at the university of konstanz
>Environment:
                I use the the GENERIC-kernel on sparc64 on a sun Netra T1. This server is
                a http-mirror for big files. I followed the netbsd-2 brach and had allways
                the same problem and now i follow the netbsd-3 branch and still have the problem.
System: NetBSD nepal 3.1_STABLE NetBSD 3.1_STABLE (GENERIC) #0: Mon Nov 13 01:16:33 CET 2006 root@nepal:/usr/obj/sys/arch/sparc64/compile/GENERIC sparc64
Architecture: sparc64
Machine: sparc64
>Description:
                The server has heavy net load (50-100% of a 100BaseT Interface all the time) and the daemon
                freezes after some days in a unkillable condition (mclpl in top or ps). I followed
                netbsd-2 and netbsd-3 without difference. I have the same problem with apache, thttpd
                and lighttpd. I have to reboot the machine every some days. If the traffic is very high i
                have to reboot two times a day.
>How-To-Repeat:
                I think you just have to produce constant heavy net usage. I donno how to include more data or
                infomation about this problem. I have no core dump or something else. These days the server is
                serving a new Wikipedia-DVD-image and the machine is crashing once a day. I can give some
                of the developers an account on this machine, if someone likes to verify the problem right on
                this server.
>Fix: