1 |
On Sunday 21 August 2011, Mick wrote: |
2 |
> Here's a strange one: |
3 |
> |
4 |
> Suspending a Pentium4 32bit machine used to work a treat. For years. |
5 |
> Then around 9 months ago or so, I can't recall exactly, it started |
6 |
> causing crashes. What happens is that the monitor will go to sleep |
7 |
> and the disk will stop immediately, but the machine continues to run |
8 |
> and run and run ... |
9 |
> |
10 |
> At that point I have lost access to the keyboard and the monitor does |
11 |
> not wake up if I move the mouse. Using ssh to connect shows that |
12 |
> the machine is off the network, so I assume that the NIC is also |
13 |
> suspended. The only way to recover is to pull the plug. :-( |
14 |
> |
15 |
> Unfortunately, mysql has left a lock file behind, so it won't start |
16 |
> at reboot until I remove the lockfile. |
17 |
> |
18 |
> Now, here's the strange thing about all this. I have 4 RAM modules, |
19 |
> 2x1G and 2x500M. Following the manual I have installed them in this |
20 |
> order: |
21 |
> |
22 |
> slot 1 - 1G, |
23 |
> slot 2 - 0.5G, |
24 |
> slot 3 - 1G, |
25 |
> slot 4 - 0.5G |
26 |
> |
27 |
> If I try to suspend the machine soon after boot, when it is still |
28 |
> using low amounts of memory, the machine will suspend each time |
29 |
> without fail (just like it used to do in the past). |
30 |
> |
31 |
> If I wait until the machine is using more than 1G or so, then it will |
32 |
> always crash. |
33 |
> |
34 |
> I'm running memtest86+ just in case, but 3 passes and no errors are |
35 |
> shown so far. Suspend to RAM is really a time saver on this machine |
36 |
> and was being used at least 4-5 times a day. Now the box is running |
37 |
> non-stop 16 hours a day or more, which is wasteful (although with |
38 |
> the Pentium4 I'm saving on central heating bills!) Any ideas what I |
39 |
> can look into to resolve this? |
40 |
|
41 |
I'm using KDE to suspend my machine, for some reason it recently stopped |
42 |
working, but it was only with kernel 3.0.1 |
43 |
|
44 |
I was able to see an error quickly changing to tty12 where the console |
45 |
is used to echo /var/log/messages after clicking "sleep" button in KDE |
46 |
|
47 |
Aug 15 07:42:31 aemaeth polkitd(authority=local): Registered |
48 |
Authentication Agent for unix- |
49 |
session:/org/freedesktop/ConsoleKit/Session1 (system bus name :1.29 |
50 |
[/usr/lib64/kde4/libexec/polkit-kde-authentication-agent-1], object path |
51 |
/org/kde/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) |
52 |
Aug 15 07:42:35 aemaeth dbus[3247]: [system] Rejected send message, 2 |
53 |
matched rules; type="method_call", sender=":1.33" (uid=501 pid=4883 |
54 |
comm="nautilus --sm-client-id 10c6d9d5610001307993940000") |
55 |
interface="org.freedesktop.DBus.Properties" member="GetAll" error |
56 |
name="(unset)" requested_reply="0" destination=":1.1" (uid=0 pid=3297 |
57 |
comm="/usr/sbin/console-kit-daemon ") |
58 |
|
59 |
The machine locked itself shortly after that error, but the log was |
60 |
there. |
61 |
|
62 |
My problem is now gone with kernel 3.0.3. I wish yours it's not a RAM |
63 |
issue, it could be tricky to spot, because memtest is not putting any |
64 |
load to the machine, so it's very useful when it reports error, but when |
65 |
it doesn't you can't be sure if RAM modules are in good health. |
66 |
From my experience the stress load of compiling large packages is more |
67 |
likely to evidence RAM faults than memtest itself. |
68 |
|
69 |
HTH |
70 |
Francesco |
71 |
|
72 |
-- |
73 |
Linux Version 3.0.0-gentoo, Compiled #3 SMP PREEMPT Fri Aug 5 21:02:22 |
74 |
CEST 2011 |
75 |
Two 2.9GHz AMD Athlon 64 X2 Processors, 4GB RAM, 11659 Bogomips Total |
76 |
aemaeth |