1 |
Howdy, |
2 |
|
3 |
As some know, I've done some upgrades recently. A month or so back, I |
4 |
had reboots due to Dolphin using up all the system memory, since |
5 |
upgraded from 16GBs to 32GBs. I stopped using Dolphin for that reason. |
6 |
I'll test it someday to see if the bug is fixed. Just a bit ago I had |
7 |
my system power off. On one hand, I think it is a hardware issue with |
8 |
the computer. On the other hand, I noticed something odd. The display |
9 |
was on on my UPS when my system went down. It usually only comes on |
10 |
when I push the button or the power fails. Thing is, the power hadn't |
11 |
failed. Sort of makes me wonder. I have a CyberPower CP 1350C that has |
12 |
that digital display thing. The display is blue. Some may have seen |
13 |
one before. While I was shutdown, I checked the UPS to make sure it |
14 |
switches as it should by unplugging it. It did. My speakers, modem, |
15 |
router etc didn't lose power. When I got booted up, I ran upsc and it |
16 |
shows a complete charge on the battery. Like this: battery.charge: |
17 |
100 The most load I've ever had on it was about 250 watts. That's with |
18 |
the new CPU and it compiling heavily. It's not even close to being |
19 |
overloaded. |
20 |
|
21 |
I checked the messages log. Before with the memory hogging Dolphin it |
22 |
had logged the problem. Today, it shows this: |
23 |
|
24 |
|
25 |
Dec 15 20:40:01 fireball CROND[30668]: (root) CMD (/usr/lib64/sa/sa1 1 1) |
26 |
Dec 15 20:50:01 fireball CROND[1532]: (root) CMD (/usr/lib64/sa/sa1 1 1) |
27 |
Dec 15 21:00:01 fireball CROND[5513]: (root) CMD (/usr/lib64/sa/sa1 1 1) |
28 |
Dec 15 21:01:01 fireball CROND[5718]: (root) CMD (run-parts |
29 |
/etc/cron.hourly) |
30 |
Dec 15 21:08:34 fireball syslog-ng[4370]: syslog-ng starting up; |
31 |
version='3.17.2' |
32 |
Dec 15 21:08:34 fireball /usr/sbin/gpm[4400]: *** info |
33 |
[daemon/startup.c(136)]: |
34 |
Dec 15 21:08:34 fireball /usr/sbin/gpm[4400]: Started gpm successfully. |
35 |
Entered daemon mode. |
36 |
|
37 |
|
38 |
As you can see, it went from running a normal cron job to me booting |
39 |
back up. I don't see any error at all. Not even one electron. One |
40 |
other odd thing. When I first boot up, my ethernet port, net.eth1, |
41 |
fails to come up. I have to reboot and then it comes up fine. It comes |
42 |
up the second time even if I do a complete power off. When I got logged |
43 |
into KDE and started my webrowsers, they are asking about recovering the |
44 |
last session. Obviously they were not closed in a normal way. |
45 |
|
46 |
When I hit the power button to turn it back on the first time, I went |
47 |
into the BIOS and checked the temps of the CPU etc. They all looked |
48 |
normal and all fans were working. I thought maybe it got hot or |
49 |
something but that doesn't seem to be the case either. |
50 |
|
51 |
What should I suspect? Is the UPS display a sign the UPS itself did |
52 |
something? Could my power supply in the puter being going out? |
53 |
Something else I should check? Something else I should check next time |
54 |
before powering up? Ideas? Thoughts? |
55 |
|
56 |
Thanks |
57 |
|
58 |
Dale |
59 |
|
60 |
:-) :-) |