[opensuse] Gigabyte instability? cron out-of-it's-mind?
List, Per,
Continuing on in the guest to what is causing the ever present, but
random instability in my 10.3 install on a Gigabyte N700SL board, I
captured the following processes while the system was rendered useless
by what appears to be cron gone mad. I have no funcky cron jobs, and my
best guess is cron went south as the result of a hardware instability
related to the Gigabyte mb that I have installed.
It's not memory and it's not power supply. Both fresh and changed, but
the same instability continues. The instability was present when the box
was a mandrake 2005 server, and the exact same instability remains under
10.3. Nothing fancy here. Just a simple dm-1 dm-2 (2 250G Seagate) md
raid 1, dvd drive, old ati xpert 2000 card (it is a text mode machine)
and a 20G Maxtor as sda that holds the swap only. Here is what I found
running after the machine went south today:
root@trinity:~ # ssh david@bonza
Last login: Sat Feb 9 23:20:43 2008 from mail.3111skyline.com
Have a lot of fun...
12:45 bonza~> ps ax
PID TTY STAT TIME COMMAND
1 ? Ss 0:01 init [6]
2 ? S< 0:00 [kthreadd]
3 ? S< 0:00 [migration/0]
4 ? SN 0:01 [ksoftirqd/0]
5 ? S< 0:07 [events/0]
6 ? S< 0:00 [khelper]
25 ? R< 0:00 [kblockd/0]
26 ? S< 0:00 [kacpid]
27 ? S< 0:00 [kacpi_notify]
148 ? S< 0:00 [cqueue/0]
149 ? S< 0:00 [kseriod]
172 ? S 0:00 [pdflush]
175 ? S< 0:00 [aio/0]
402 ? S< 0:00 [kpsmoused]
412 ? S< 0:00 [kondemand/0]
459 ? S< 0:02 [ata/0]
460 ? S< 0:00 [ata_aux]
462 ? S< 0:00 [scsi_eh_0]
463 ? S< 0:04 [scsi_eh_1]
467 ? S< 0:00 [scsi_eh_2]
468 ? S< 0:00 [scsi_eh_3]
489 ? S< 0:00 [ksnapd]
627 ? S< 0:00 [ksuspend_usbd]
628 ? S< 0:00 [khubd]
1067 ? S< 0:08 [kmirrord]
1068 ? S< 0:00 [kcopyd]
1122 ? D< 0:03 [kjournald]
1179 ? S
On Monday 11 February 2008, David C. Rankin wrote:
List, Per,
Continuing on in the guest to what is causing the ever present, but random instability in my 10.3 install on a Gigabyte N700SL board, I captured the following processes while the system was rendered useless by what appears to be cron gone mad. I have no funcky cron jobs, and my best guess is cron went south as the result of a hardware instability related to the Gigabyte mb that I have installed.
/snip Hi .. Last time i saw that cron was being called several times i never did find where/how but it was on a machine that runs 24/7 so i canned all the cron-daily mohthly weekly hourly stuff and went back to a sensible hand crafted cron script never had another problem since that was on a suse 10.0 machine on 10.3 not had a problem (YET) althou ihave to admit to not liking the way cron is setup at all these days and the first sign of problems and it will go back to the old style system . Pete . -- SuSE Linux 10.3-Alpha3. (Linux is like a wigwam - no Gates, no Windows, and an Apache inside.) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (2)
-
David C. Rankin
-
peter nikolic