| 1 |
(sorry for top-posting) |
| 2 |
|
| 3 |
Do the 1 GB pieces have the same timing values as the 0.5 GB pieces? |
| 4 |
|
| 5 |
Try slowing down the memory timing parameters in BIOS (should look |
| 6 |
like 8-5-3-3 or something like that; larger numbers are slower). |
| 7 |
|
| 8 |
Rgds, |
| 9 |
|
| 10 |
|
| 11 |
On 2011-08-21, Mick <michaelkintzios@×××××.com> wrote: |
| 12 |
> On Sunday 21 Aug 2011 12:19:40 Francesco Talamona wrote: |
| 13 |
>> On Sunday 21 August 2011, Mick wrote: |
| 14 |
>> > Here's a strange one: |
| 15 |
>> > |
| 16 |
>> > Suspending a Pentium4 32bit machine used to work a treat. For years. |
| 17 |
>> > |
| 18 |
>> > Then around 9 months ago or so, I can't recall exactly, it started |
| 19 |
>> > |
| 20 |
>> > causing crashes. What happens is that the monitor will go to sleep |
| 21 |
>> > and the disk will stop immediately, but the machine continues to run |
| 22 |
>> > and run and run ... |
| 23 |
>> > |
| 24 |
>> > At that point I have lost access to the keyboard and the monitor does |
| 25 |
>> > not wake up if I move the mouse. Using ssh to connect shows that |
| 26 |
>> > the machine is off the network, so I assume that the NIC is also |
| 27 |
>> > suspended. The only way to recover is to pull the plug. :-( |
| 28 |
>> > |
| 29 |
>> > Unfortunately, mysql has left a lock file behind, so it won't start |
| 30 |
>> > at reboot until I remove the lockfile. |
| 31 |
>> > |
| 32 |
>> > Now, here's the strange thing about all this. I have 4 RAM modules, |
| 33 |
>> > 2x1G and 2x500M. Following the manual I have installed them in this |
| 34 |
>> > order: |
| 35 |
>> > |
| 36 |
>> > slot 1 - 1G, |
| 37 |
>> > slot 2 - 0.5G, |
| 38 |
>> > slot 3 - 1G, |
| 39 |
>> > slot 4 - 0.5G |
| 40 |
>> > |
| 41 |
>> > If I try to suspend the machine soon after boot, when it is still |
| 42 |
>> > using low amounts of memory, the machine will suspend each time |
| 43 |
>> > without fail (just like it used to do in the past). |
| 44 |
>> > |
| 45 |
>> > If I wait until the machine is using more than 1G or so, then it will |
| 46 |
>> > always crash. |
| 47 |
>> > |
| 48 |
>> > I'm running memtest86+ just in case, but 3 passes and no errors are |
| 49 |
>> > shown so far. Suspend to RAM is really a time saver on this machine |
| 50 |
>> > and was being used at least 4-5 times a day. Now the box is running |
| 51 |
>> > non-stop 16 hours a day or more, which is wasteful (although with |
| 52 |
>> > the Pentium4 I'm saving on central heating bills!) Any ideas what I |
| 53 |
>> > can look into to resolve this? |
| 54 |
>> |
| 55 |
>> I'm using KDE to suspend my machine, for some reason it recently stopped |
| 56 |
>> working, but it was only with kernel 3.0.1 |
| 57 |
>> |
| 58 |
>> I was able to see an error quickly changing to tty12 where the console |
| 59 |
>> is used to echo /var/log/messages after clicking "sleep" button in KDE |
| 60 |
>> |
| 61 |
>> Aug 15 07:42:31 aemaeth polkitd(authority=local): Registered |
| 62 |
>> Authentication Agent for unix- |
| 63 |
>> session:/org/freedesktop/ConsoleKit/Session1 (system bus name :1.29 |
| 64 |
>> [/usr/lib64/kde4/libexec/polkit-kde-authentication-agent-1], object path |
| 65 |
>> /org/kde/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) |
| 66 |
>> Aug 15 07:42:35 aemaeth dbus[3247]: [system] Rejected send message, 2 |
| 67 |
>> matched rules; type="method_call", sender=":1.33" (uid=501 pid=4883 |
| 68 |
>> comm="nautilus --sm-client-id 10c6d9d5610001307993940000") |
| 69 |
>> interface="org.freedesktop.DBus.Properties" member="GetAll" error |
| 70 |
>> name="(unset)" requested_reply="0" destination=":1.1" (uid=0 pid=3297 |
| 71 |
>> comm="/usr/sbin/console-kit-daemon ") |
| 72 |
>> |
| 73 |
>> The machine locked itself shortly after that error, but the log was |
| 74 |
>> there. |
| 75 |
>> |
| 76 |
>> My problem is now gone with kernel 3.0.3. I wish yours it's not a RAM |
| 77 |
>> issue, it could be tricky to spot, because memtest is not putting any |
| 78 |
>> load to the machine, so it's very useful when it reports error, but when |
| 79 |
>> it doesn't you can't be sure if RAM modules are in good health. |
| 80 |
>> From my experience the stress load of compiling large packages is more |
| 81 |
>> likely to evidence RAM faults than memtest itself. |
| 82 |
> |
| 83 |
> No problem with big package emerges, or running demanding applications like |
| 84 |
> gimp, inkscape and firefox, chrome and opera with umpteen tabs open, plus |
| 85 |
> Windows7 running on virtualbox on occasion. When all 3G is needed the |
| 86 |
> machine |
| 87 |
> will swap happily. |
| 88 |
> |
| 89 |
> I would readily say that I am certain this is not a memory problem except |
| 90 |
> ... |
| 91 |
> the 2x1G RAM modules are not the same make as the 2x500M modules. In the |
| 92 |
> past |
| 93 |
> I have had MoBos which were very particular on choice of memory modules and |
| 94 |
> mismatching them led to all sort of obscure crashes (e.g. when swapping was |
| 95 |
> starting). |
| 96 |
> -- |
| 97 |
> Regards, |
| 98 |
> Mick |
| 99 |
> |
| 100 |
|
| 101 |
|
| 102 |
-- |
| 103 |
-- |
| 104 |
Pandu E Poluan - IT Optimizer |
| 105 |
My website: http://pandu.poluan.info/ |
Archives