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