From owner-freebsd-stable@FreeBSD.ORG Fri Jul 12 07:44:04 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 0966C149; Fri, 12 Jul 2013 07:44:04 +0000 (UTC) (envelope-from ronald-freebsd8@klop.yi.org) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) by mx1.freebsd.org (Postfix) with ESMTP id 992DC11ED; Fri, 12 Jul 2013 07:44:03 +0000 (UTC) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1UxY1D-00040C-Lo; Fri, 12 Jul 2013 09:43:56 +0200 Received: from [81.21.138.17] (helo=ronaldradial.versatec.local) by smtp.greenhost.nl with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1UxY1D-0002Uz-Hw; Fri, 12 Jul 2013 09:43:55 +0200 Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: freebsd-amd64 , freebsd-stable , "Chris H" Subject: Re: What are the ideal ranges for kern.ipc.shm*? References: <4640843f1a35075d295f99aa9e8ed951.authenticated@ultimatedns.net> Date: Fri, 12 Jul 2013 09:43:52 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: "Ronald Klop" Message-ID: In-Reply-To: <4640843f1a35075d295f99aa9e8ed951.authenticated@ultimatedns.net> User-Agent: Opera Mail/12.16 (Win32) X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.0 X-Spam-Status: No, score=-0.0 required=5.0 tests=BAYES_20 autolearn=disabled version=3.3.1 X-Scan-Signature: 729ef2e9e2cd27dd49f9ca04774c95e6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jul 2013 07:44:04 -0000 On Fri, 12 Jul 2013 05:24:55 +0200, Chris H wrote: > Greetings, > Over the years using the xfce4 desktop, I would occasionally receive > SHM ERROR messages. As they never interfered (so's I could notice), I > always put off attempting to track the cause down. However, now having > performed a fairly major upgrade (~1yr since last), The error appears > to greatly affect KDE4 (used to use kde3) applications I run within > xfce4. The windows don't re-draw correctly, and I receive additional > errors,as well: > ... > Resource id: 0x0 > X Error: BadDrawable (invalid Pixmap or Window parameter) 9 > Major opcode: 62 (X_CopyArea) > Resource id: 0x0 > X Error: BadDrawable (invalid Pixmap or Window parameter) 9 > Major opcode: 62 (X_CopyArea) > Resource id: 0x0 > X Error: BadDrawable (invalid Pixmap or Window parameter) 9 > Major opcode: 62 (X_CopyArea) > Resource id: 0x0 > X Error: BadDrawable (invalid Pixmap or Window parameter) 9 > Major opcode: 62 (X_CopyArea) > Resource id: 0x0 > QCoreApplication::postEvent: Unexpected null receiver > ... > After much searching, it would appear to be related to the > kern.ipc.shm* values. > pertinent details follow: > FreeBSD udns 8.4-STABLE FreeBSD 8.4-STABLE #3: Tue Jul 2 13:41:21 PDT > 2013 > root@udns:/usr/obj/usr/src/sys/AMD64 amd64 > with 64Gb ram, and 3 cores, and nvidia-driver-308.88_1. > # ipcs -M > shminfo: > shmmax: 33554432 (max shared memory segment size) > shmmin: 1 (min shared memory segment size) > shmmni: 192 (max number of shared memory identifiers) > shmseg: 128 (max shared memory segments per process) > shmall: 8192 (max amount of shared memory in pages) My 9.1-STABLE amd64 with 4GB RAM has these default settings: ipcs -M shminfo: shmmax: 536870912 (max shared memory segment size) shmmin: 1 (min shared memory segment size) shmmni: 1024 (max number of shared memory identifiers) shmseg: 1024 (max shared memory segments per process) shmall: 131072 (max amount of shared memory in pages) Regards, Ronald.