From owner-freebsd-arm@FreeBSD.ORG Sun Apr 28 07:49:55 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 560B7CAA for ; Sun, 28 Apr 2013 07:49:55 +0000 (UTC) (envelope-from tvijlbrief@gmail.com) Received: from mail-ie0-x236.google.com (mail-ie0-x236.google.com [IPv6:2607:f8b0:4001:c03::236]) by mx1.freebsd.org (Postfix) with ESMTP id 302A41C54 for ; Sun, 28 Apr 2013 07:49:55 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id bn7so6344217ieb.27 for ; Sun, 28 Apr 2013 00:49:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=IG6Ynqgbzj7XptCI4VhNpaxdo4Cjzpo2yg4W442HB0M=; b=NkIvMbL+ph6KwKMg+zUONl4DNEwNLLFqL1DSNjLuA/uAb5V6QaDGY0zlmi06+dfj5V htl462FmSlBiQ+KTV5X0gOYwANcIXSCAtS0lM2kY9DdzkqI5zguo0c213nclze0WK8Nk ba+urdLLKIHsBEQfIQ2IUCuNESppiEOUz/AYDXJghHpdA4B6KZvMR5ybbQJZvycs/J5J 9UJ5tj2wTJ/FxOj9p/gPxoyf+xrsXIP//GEiINSPFoCB2reBVAoAqPSQReuVbSRviOPx dFUBqbyuk04sTyUwbXvHNzMa62+NZXrl6GgY+/nbr0Bf6bpjO7t3yr3GHC5GXzSD3X6L +j6w== MIME-Version: 1.0 X-Received: by 10.42.203.68 with SMTP id fh4mr12785536icb.36.1367135394778; Sun, 28 Apr 2013 00:49:54 -0700 (PDT) Received: by 10.50.92.34 with HTTP; Sun, 28 Apr 2013 00:49:54 -0700 (PDT) Date: Sun, 28 Apr 2013 09:49:54 +0200 Message-ID: Subject: Raspberry Pi VM tests From: Tom Vijlbrief To: freebsd-arm@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Apr 2013 07:49:55 -0000 I did some testing to see if I could reproduce the strange killed processes which I experienced during build world on my 256MB RPI. I disabled the swap partition on my USB drive and did some testing with the "stress" program from ports: stress --vm 1 --vm-bytes 200M --vm-keep results in dmesg: pid 664 (stress), uid 1000, was killed: out of swap space That's logical. Next I did a stress --vm 1 --vm-bytes 150M --vm-keep and a few moments later: pid 606 (sshd), uid 0: exited on signal 11 pid 610 (cron), uid 0: exited on signal 11 (core dumped) This should NOT happen. Another problem is that i tried a large zmodem upload on the serial console of a 10MB file. Minicom and sz on the sending site, rz (from lrzsz from ports) on the receiving site. This works, but if I run a compile in another ssh session during the transfer then the transfer hangs and the serial console will no longer handle any input. Killing the console shell results in a new getty but it cannot receive any input. It's dead. data > /dev/console does show output however. I use a kernel from a current tree a few days old. Can others reproduce these problems?