From: meino.cramer@gmx.de
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Suspend to RAM caused crashes
Date: Sun, 21 Aug 2011 17:30:52 +0200 [thread overview]
Message-ID: <20110821153052.GA3105@solfire> (raw)
In-Reply-To: <201108211127.57077.michaelkintzios@gmail.com>
Mick <michaelkintzios@gmail.com> [11-08-21 12:32]:
> Here's a strange one:
>
> Suspending a Pentium4 32bit machine used to work a treat. For years. Then
> around 9 months ago or so, I can't recall exactly, it started 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 ...
>
> 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. :-(
>
> Unfortunately, mysql has left a lock file behind, so it won't start at reboot
> until I remove the lockfile.
>
> 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:
>
> slot 1 - 1G,
> slot 2 - 0.5G,
> slot 3 - 1G,
> slot 4 - 0.5G
>
> 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).
>
> If I wait until the machine is using more than 1G or so, then it will always
> crash.
>
> 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?
> --
> Regards,
> Mick
Hi Mick,
one thing, which is able to produce any kind of error except those, which one
would exspect in a certain context, is a bad capicitor on the mobo (or
sometimes in the power supply).
If I understand your posting correctly, your PC is not the youngest
one...?
I had a motherboard, which completly fails to boot the very first
stages of the kernel boot process, but perfectly runs memtest86....
Bad capacitors...
More RAM means more power.
What happens, if you change the RAMS in such a manner:
slot 1 - 0.5G,
slot 2 - 1G,
slot 3 - 0.5G
slot 4 - 1G,
?
Does teh computer have problems after accessing slot 2 or after access
more than 1G?
Best regards,
mcc
prev parent reply other threads:[~2011-08-21 15:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-21 10:27 [gentoo-user] Suspend to RAM caused crashes Mick
2011-08-21 11:19 ` [gentoo-user] " Francesco Talamona
2011-08-21 11:42 ` Mick
2011-08-21 11:57 ` [gentoo-user] " Pandu Poluan
2011-08-21 12:37 ` Mick
2011-08-21 15:12 ` [gentoo-user] " Nikos Chantziaras
2011-08-21 15:22 ` Volker Armin Hemmann
2011-08-21 15:33 ` Mark Knecht
2011-08-21 15:43 ` Nikos Chantziaras
2011-08-21 16:08 ` Mark Knecht
2011-08-21 16:26 ` Nikos Chantziaras
2011-08-21 17:27 ` Mark Knecht
2011-08-21 17:28 ` Volker Armin Hemmann
2011-08-22 4:54 ` Francesco Talamona
2011-08-21 12:53 ` [gentoo-user] " Volker Armin Hemmann
2011-08-21 15:30 ` meino.cramer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110821153052.GA3105@solfire \
--to=meino.cramer@gmx.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox