From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Qv6Sg-00087J-6e for garchives@archives.gentoo.org; Sun, 21 Aug 2011 11:45:08 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 10A9521C205; Sun, 21 Aug 2011 11:44:52 +0000 (UTC) Received: from mail-wy0-f181.google.com (mail-wy0-f181.google.com [74.125.82.181]) by pigeon.gentoo.org (Postfix) with ESMTP id 3ED8F21C117 for ; Sun, 21 Aug 2011 11:42:22 +0000 (UTC) Received: by wyg36 with SMTP id 36so4029655wyg.40 for ; Sun, 21 Aug 2011 04:42:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:reply-to:to:subject:date:user-agent:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; bh=B8jGl5AKEp7/yHFURJt2FlTSUU4Ed7YYEu4LlxmyBTc=; b=pCKsngVwGu+9hVygmbKZd8LXN1VRdOcPgjjkhpsjeU2+CMqhgGeJw3kssZTXH3A9uY r6IX8WmRJwPRH/pOT4QwusC3hCHuvVGNWkU0a7tcT2ip5V1mQ3Vd9tE9p7xeQUQoRtKE 4byvNtrT2jnr0mRak1hKpS0ly6YfYDBOnurLI= Received: by 10.227.177.133 with SMTP id bi5mr1095371wbb.39.1313926942352; Sun, 21 Aug 2011 04:42:22 -0700 (PDT) Received: from dell_xps.localnet (230.3.169.217.in-addr.arpa [217.169.3.230]) by mx.google.com with ESMTPS id eq21sm4018790wbb.1.2011.08.21.04.42.20 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 21 Aug 2011 04:42:21 -0700 (PDT) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: Suspend to RAM caused crashes Date: Sun, 21 Aug 2011 12:42:58 +0100 User-Agent: KMail/1.13.7 (Linux/2.6.39-gentoo-r3; KDE/4.6.5; x86_64; ; ) References: <201108211127.57077.michaelkintzios@gmail.com> <201108211319.40825.francesco.talamona@know.eu> In-Reply-To: <201108211319.40825.francesco.talamona@know.eu> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2050100.VCOYFqTY97"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201108211243.07642.michaelkintzios@gmail.com> X-Archives-Salt: X-Archives-Hash: 98032b03624c2f77ed290d7715c3e513 --nextPart2050100.VCOYFqTY97 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Sunday 21 Aug 2011 12:19:40 Francesco Talamona wrote: > On Sunday 21 August 2011, Mick wrote: > > Here's a strange one: > >=20 > > Suspending a Pentium4 32bit machine used to work a treat. For years. > >=20 > > Then around 9 months ago or so, I can't recall exactly, it started > >=20 > > causing crashes. What happens is that the monitor will go to sleep > > and the disk will stop immediately, but the machine continues to run > > and run and run ... > >=20 > > At that point I have lost access to the keyboard and the monitor does > > not wake up if I move the mouse. Using ssh to connect shows that > > the machine is off the network, so I assume that the NIC is also > > suspended. The only way to recover is to pull the plug. :-( > >=20 > > Unfortunately, mysql has left a lock file behind, so it won't start > > at reboot until I remove the lockfile. > >=20 > > Now, here's the strange thing about all this. I have 4 RAM modules, > > 2x1G and 2x500M. Following the manual I have installed them in this > > order: > >=20 > > slot 1 - 1G, > > slot 2 - 0.5G, > > slot 3 - 1G, > > slot 4 - 0.5G > >=20 > > If I try to suspend the machine soon after boot, when it is still > > using low amounts of memory, the machine will suspend each time > > without fail (just like it used to do in the past). > >=20 > > If I wait until the machine is using more than 1G or so, then it will > > always crash. > >=20 > > I'm running memtest86+ just in case, but 3 passes and no errors are > > shown so far. Suspend to RAM is really a time saver on this machine > > and was being used at least 4-5 times a day. Now the box is running > > non-stop 16 hours a day or more, which is wasteful (although with > > the Pentium4 I'm saving on central heating bills!) Any ideas what I > > can look into to resolve this? >=20 > I'm using KDE to suspend my machine, for some reason it recently stopped > working, but it was only with kernel 3.0.1 >=20 > I was able to see an error quickly changing to tty12 where the console > is used to echo /var/log/messages after clicking "sleep" button in KDE >=20 > Aug 15 07:42:31 aemaeth polkitd(authority=3Dlocal): Registered > Authentication Agent for unix- > session:/org/freedesktop/ConsoleKit/Session1 (system bus name :1.29 > [/usr/lib64/kde4/libexec/polkit-kde-authentication-agent-1], object path > /org/kde/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) > Aug 15 07:42:35 aemaeth dbus[3247]: [system] Rejected send message, 2 > matched rules; type=3D"method_call", sender=3D":1.33" (uid=3D501 pid=3D48= 83 > comm=3D"nautilus --sm-client-id 10c6d9d5610001307993940000") > interface=3D"org.freedesktop.DBus.Properties" member=3D"GetAll" error > name=3D"(unset)" requested_reply=3D"0" destination=3D":1.1" (uid=3D0 pid= =3D3297 > comm=3D"/usr/sbin/console-kit-daemon ") >=20 > The machine locked itself shortly after that error, but the log was > there. >=20 > My problem is now gone with kernel 3.0.3. I wish yours it's not a RAM > issue, it could be tricky to spot, because memtest is not putting any > load to the machine, so it's very useful when it reports error, but when > it doesn't you can't be sure if RAM modules are in good health. > From my experience the stress load of compiling large packages is more > likely to evidence RAM faults than memtest itself. No problem with big package emerges, or running demanding applications like= =20 gimp, inkscape and firefox, chrome and opera with umpteen tabs open, plus=20 Windows7 running on virtualbox on occasion. When all 3G is needed the mach= ine=20 will swap happily. I would readily say that I am certain this is not a memory problem except .= =2E.=20 the 2x1G RAM modules are not the same make as the 2x500M modules. In the p= ast=20 I have had MoBos which were very particular on choice of memory modules and= =20 mismatching them led to all sort of obscure crashes (e.g. when swapping was= =20 starting). =2D-=20 Regards, Mick --nextPart2050100.VCOYFqTY97 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iEYEABECAAYFAk5Q70sACgkQVTDTR3kpaLaFPwCcCxh1llS1kbCAifdEOd8DOH/7 8rIAn2RqyXRKyflQjdHh1KTOVjWVIJ4e =SCUQ -----END PGP SIGNATURE----- --nextPart2050100.VCOYFqTY97--