From owner-freebsd-stable Thu Aug 30 6:28:14 2001 Delivered-To: freebsd-stable@freebsd.org Received: from light.imasy.or.jp (light.imasy.or.jp [202.227.24.4]) by hub.freebsd.org (Postfix) with ESMTP id 51F3837B406 for ; Thu, 30 Aug 2001 06:28:07 -0700 (PDT) (envelope-from ume@mahoroba.org) Received: (from uucp@localhost) by light.imasy.or.jp (8.11.6+3.4W/8.11.6/light) with UUCP id f7UDQWT16220; Thu, 30 Aug 2001 22:26:32 +0900 (JST) (envelope-from ume@mahoroba.org) Received: from peace.mahoroba.org (IDENT:LXADKl3BYi19BeijWenyue9fXJCTZytZ1hX0cK5mommty22JWxyf7kx0MKlJwNFt@peace.mahoroba.org [3ffe:505:2:0:200:f8ff:fe05:3eae]) (authenticated as ume with CRAM-MD5) by mail.mahoroba.org (8.11.6/8.11.6/chaos) with ESMTP/inet6 id f7UDNFj05231; Thu, 30 Aug 2001 22:23:15 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Thu, 30 Aug 2001 22:23:56 +0900 (JST) Message-Id: <20010830.222356.125820097.ume@mahoroba.org> To: mwm@mired.org Cc: varju@webct.com, stable@freebsd.org Cc: ume@mahoroba.org Subject: Re: Freezes in 4.4RC on SMP Kernel and gkrellm From: Hajimu UMEMOTO In-Reply-To: <15245.51106.120852.616240@guru.mired.org> References: <15245.28607.676147.717891@guru.mired.org> <20010829155138.F60349-100000@snapple.webct.com> <15245.51106.120852.616240@guru.mired.org> X-Mailer: xcite1.38> Mew version 1.95b119 on Emacs 20.7 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-Operating-System: FreeBSD 5.0-CURRENT Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >>>>> On Wed, 29 Aug 2001 23:57:06 -0500 >>>>> Mike Meyer said: mwm> Turns out that gkrellm can be *very* hazardous to your system. I've mwm> got a situation where the system panics every time I start gkrellm. I mwm> believe this is a bug in gkrellm, not in the system. I didn't thought this thread lead to GKrellM problem. X-( mwm> From looking over gkrellm's code, it assumes that any smb device it mwm> finds is the one it knows about - and proceeds to try and extract data mwm> from it. This seems like a bad idea - at least in this case. Yes, it is dirty. However, I have no idea to distinguish if smb is mapped to initpm. I wish to fix it. Is there any way to do it? mwm> gkrellm also has the problem that it initializes every monitor it mwm> knows about, even if that one isn't being displayed. Without the smb mwm> devices, it uses /dev/io, and that's left open so that gkrellm can mwm> lower it's privileges after opening the file. This means bugs in other mwm> modules could stroke /dev/io in some strange way - and I believe mwm> that's the root cause of the freezes I'm seeing. I wish to have a generic method to obtain temperature, fan speed and voltage without any extra privilege. mwm> I've installed gkrellm WITHOUT_SENSOR=yes - which sgid instead of suid mwm> - and enabled all the things that I had on when the system was mwm> freezing before, except the sensors. I'll turn sensor support off by default for workaround. Sincerely, -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message