[ale] ASUS P5MT question

Dow_Hurst dhurst at mindspring.com
Sat Jul 22 11:25:17 EDT 2006


Hey, I found after the crashes yesterday that the machine stayed up til 11pm.  I have done a couple of things since disabling HT in the BIOS and using a default uniprocessor kernel:

I switched to a larger UPS, Tripplite 2200.

I turned off at 11pm the Zen update daemon, powersaved, cups, and postfix.  I'm trying to isolate down to the bare minimum of processes.  So here is the process list:

doodle:~ # ps aux
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1  0.0  0.0    716    56 ?        S    Jul21   0:01 init [3]
root         2  0.0  0.0      0     0 ?        SN   Jul21   0:00 [ksoftirqd/0]
root         3  0.0  0.0      0     0 ?        S<   Jul21   0:00 [events/0]
root         4  0.0  0.0      0     0 ?        S<   Jul21   0:00 [khelper]
root         5  0.0  0.0      0     0 ?        S<   Jul21   0:00 [kthread]
root         7  0.0  0.0      0     0 ?        S<   Jul21   0:02 [kblockd/0]
root        46  0.0  0.0      0     0 ?        S    Jul21   0:00 [kapmd]
root        70  0.0  0.0      0     0 ?        S<   Jul21   0:00 [aio/0]
root        69  0.0  0.0      0     0 ?        S    Jul21   0:55 [kswapd0]
root       282  0.0  0.0      0     0 ?        S<   Jul21   0:00 [cqueue/0]
root       283  0.0  0.0      0     0 ?        S<   Jul21   0:00 [kseriod]
root       319  0.0  0.0      0     0 ?        S<   Jul21   0:00 [kpsmoused]
root       663  0.0  0.0      0     0 ?        S<   Jul21   0:00 [ata/0]
root       672  0.0  0.0      0     0 ?        S<   Jul21   0:00 [scsi_eh_0]
root       675  0.0  0.0      0     0 ?        S<   Jul21   0:00 [scsi_eh_1]
root       709  0.0  0.0      0     0 ?        S<   Jul21   0:00 [scsi_eh_2]
root       772  0.0  0.0      0     0 ?        D<   Jul21   0:27 [reiserfs/0]
root       866  0.0  0.0   1864   168 ?        S<s  Jul21   0:00 /sbin/udevd --daemon
root      1366  0.0  0.0      0     0 ?        S    Jul21   0:00 [shpchpd_event]
root      1404  0.0  0.0      0     0 ?        S<   Jul21   0:00 [khubd]
100       2170  0.0  0.0   3416   504 ?        Ss   Jul21   0:00 /usr/bin/dbus-daemon --system
root      2198  0.0  0.0   1800   156 ?        Ss   Jul21   0:00 /sbin/resmgrd
root      2211  0.0  0.1   4424   840 ?        Ss   Jul21   0:01 /usr/sbin/hald --daemon=yes --retain-privileges
root      2485  0.0  0.0   1820   192 ?        S    Jul21   0:00 hald-addon-storage
root      2548  0.0  0.0   1548    48 ?        Ss   Jul21   0:00 /sbin/dhcpcd -C -D -K -N -t 999999 -h doodle -c /etc/sysconfig/network/sc
mdnsd     2762  0.0  0.0   1972   328 ?        Ss   Jul21   0:00 /usr/sbin/mdnsd -f /etc/nss_mdns.conf -b
root      2781  0.0  0.0   1892   348 ?        Ss   Jul21   0:00 /sbin/syslog-ng
root      2784  0.0  0.0   1656   360 ?        Ss   Jul21   0:00 /sbin/klogd -c 1 -x -x
nobody    2795  0.0  0.0   1560   120 ?        Ss   Jul21   0:00 /sbin/portmap
root      2822  0.0  0.0   9856   212 ?        S<sl Jul21   0:00 /sbin/auditd -n
root      2834  0.0  0.0      0     0 ?        S<   Jul21   0:00 [kauditd]
root      2930  0.0  0.1 106472   608 ?        Ssl  Jul21   0:00 /usr/sbin/nscd
root      3304  0.0  0.0   1820   240 ?        Ss   Jul21   0:00 /usr/sbin/cron
root      3361  0.0  0.0   4956   384 ?        Ss   Jul21   0:00 /usr/sbin/sshd -o PidFile=/var/run/sshd.init.pid
root      3503  0.0  0.0   1956   164 tty1     Ss+  Jul21   0:00 /sbin/mingetty --noclear tty1
root      3507  0.0  0.0   1956   156 tty2     Ss+  Jul21   0:00 /sbin/mingetty tty2
root      3511  0.0  0.0   1956   156 tty3     Ss+  Jul21   0:00 /sbin/mingetty tty3
root      3514  0.0  0.0   1960   156 tty4     Ss+  Jul21   0:00 /sbin/mingetty tty4
root      3516  0.0  0.0   1956   156 tty5     Ss+  Jul21   0:00 /sbin/mingetty tty5
root      3518  0.0  0.0   1956   156 tty6     Ss+  Jul21   0:00 /sbin/mingetty tty6
root      4345  0.0  0.0   4384   112 ?        Ss   01:32   0:00 ssh-agent
root      4348  0.0  0.0   3000   144 ?        Ss   01:33   0:00 SCREEN
root      4349  0.0  0.0   3100   196 pts/1    Ss   01:33   0:00 /bin/bash
root      4366  0.0  7.6 133248 39608 pts/1    S+   01:33   0:21 rsync -av -e ssh albus:/home/backup/ /backup
root      4367 13.7  0.3   6388  1828 pts/1    S+   01:33  78:19 ssh albus rsync --server --sender -vlogDtpr . /home/backup/
root      4370  6.8  7.7 133508 40076 pts/1    D+   01:38  38:29 rsync -av -e ssh albus:/home/backup/ /backup
root      6472  0.0  0.4   8340  2352 ?        Ds   10:59   0:00 sshd: root at pts/0
root      6476  0.0  0.3   4132  1916 pts/0    Ss   10:59   0:00 -bash
root      6526  0.1  0.0      0     0 ?        D    11:00   0:00 [pdflush]
root      6529  0.0  0.0      0     0 ?        D    11:01   0:00 [pdflush]
root      6531  0.1  0.0      0     0 ?        D    11:02   0:00 [pdflush]
root      6532  0.0  0.0      0     0 ?        D    11:02   0:00 [pdflush]
root      6537  0.0  0.0      0     0 ?        D    11:02   0:00 [pdflush]



The machine is still up and transferring data at a steady rate.  I was expecting to find it unpingable.  Here is the CPU info:

doodle:/proc # cat cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 15
model           : 6
model name      : Intel(R) Pentium(R) 4 CPU 3.00GHz
stepping        : 2
cpu MHz         : 3000.697
cache size      : 2048 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 6
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl cid cx16 xtpr lahf_lm
bogomips        : 6009.38

It is possible that the onboard ATI graphics and the BIOS have a problem since most crashes occurred when I had the console logged in as root.  Another possibility is that powersaved was generating some directive that caused a crash.  I'm guessing now.  I have one other thought about power in general:

The powersupply is a Antec Truepower 2.0 550watt.  I have 9 SATA drives, 4 120mm fans, 1 80mm fan, USB mouse, P/S2 keyboard, 1 DVDRW drive, and the 3ware RAID card.  I have the power divided up as much as I can among the leads from the powersupply.  However, I wonder how close I am to pushing the powersupply to it's limits?  The 3ware card spins up the 8 RAID drives in a delayed fashion due to my adding a jumper on the WD drives so startup current is minimized.  All the drives are set to spread spectrum operation.  It is just strange that it hasn't crashed yet while the transfer rate is the same as yesterday, so the only major difference is my not touching the keyboard and having the ATI chip waking up the display periodically.

Sorry for the long post!
Dow





-----Original Message-----
>From: Dow_Hurst <dhurst at mindspring.com>
>Sent: Jul 16, 2006 11:12 PM
>To: Atlanta Linux Enthusiasts <ale at ale.org>
>Subject: Re: [ale] ASUS P5MT question
>
>JD,
>I got it to boot with a SATA primary drive and PATA DVDRW drive.  I am in Compatible Mode for the IDE subsystem with SATA as Primary and PATA as Secondary.  I noticed that the kernel ACPI routines had an error shown in dmesg:
> 
><4>ACPI Error (dsopcode-0460): Attempt to create_field of length zero [20060127]
><4>ACPI Error (psparse-0517): Method parse/execution failed [\_SB_.PCI0.IDE0.RATA] (Node dffb7400), AE_AML_OPERAND_VALUE
><4>ACPI Error (psparse-0517): Method parse/execution failed [\_SB_.PCI0.IDE0.CHN1.DRV0._GTF] (Node dffb7620), AE_AML_OPERAND_VALUE
>
>so I disabled ACPI and used the install routine that deselects using ACPI for Suse 10.1.  That combination finally worked.  I'll put the PATA 80Gb drive somewhere else useful and put in a decent SATA drive for the installation.  I'll keep my nice WD4000YR drives for the RAID.  I also need to now doublecheck I can still boot if the RAID card goes back in.  I'm switching cases as well to enhance the cooling of the drives.  It is a Antec P180 Adv. Super Mid Tower.  A really nice design for a lot of quiet air moving in the right directions.  I appreciate your advice!  Thanks for helping out,
>Dow
>
>
>-----Original Message-----
>>From: "J. D." <jdonline at gmail.com>
>>Sent: Jul 16, 2006 8:26 PM
>>To: Dow_Hurst <Dow.Hurst at mindspring.com>, Atlanta Linux Enthusiasts <ale at ale.org>
>>Subject: Re: [ale] ASUS P5MT question
>>
>>>
>>> >Thanks!  I've checked those settings and have disabled them.  There was
>>> no Serial-ATA Boot >ROM.  I disabled the 3ware boot BIOS and the Onboard LAN
>>> Boot ROM.  I found I was still >getting the boot failure so took out the
>>> RAID card.  I still have this problem.  So, I am going >back to square one
>>> and making sure cables are okay and that I can get a single SATA or >PATA
>>> drive to work.  I am amazed at how much trouble I've had trying to put all
>>> this hardware >together and get it to work!  Usually stuff just works.
>>>
>>
>>Sounds like a good plan Dow. I have seen problems in the past with running
>>PATA and SATA on the same board while trying to boot to the PATA. It is
>>strange in your case since you are using a raid controller instead of the
>>onboard SATA. It does sound like some sort of problem with the boot sequence
>>though.
>>     On some boards there is a SATA mode setting that is usually the
>>solution for this type of problem. Usually toggling this setting to enhanced
>>or legacy is helpful. It has been awhile since I troubleshot that problem
>>and it varies a little bit from board to board. Let us know what you find.
>>:)
>>
>>Best regards,
>>
>>J. D.
>
>
>No sig.
>_______________________________________________
>Ale mailing list
>Ale at ale.org
>http://www.ale.org/mailman/listinfo/ale


No sig.



More information about the Ale mailing list