I recently upgraded to R5A30.2, moved to new hardware and added a hidef tuner (DCT-6200) to my myth setup and I am having some stability problems. Periodically I find that the entire system is hung. I can't even remote log in via "putty" and I am forced to hit the reset button. After a recent hang I looked in /var/log/messages I saw the following:

From this I conclude that the system died somewhere around 12:30; I believe the entry at 15:42 was a result of my resetting the system. After doing some more grepping of various logs I have found the following error messages:



Note: I mis-copied the "drive_cmd" messages in my original posting -- I've updated them to reflect the two different messages I am getting.

The APIC error is repeated many times. The drive_cmd error messages each occur only once/boot.

Does anyone have an experience with these error messages? Do the APIC or "drive_cmd" error messages indicate a root cause for the hang? I ran a quick test of both hard drives (hda & hdb), but it came up clean.

Thanks for any help you can provided.

Marc

A brief update. I've made two changes to my configuration and the "drive_cmd" message no longer happen during boot:

1. I moved the "hdb" drive so so that it is now "hdd". So my configuration is "hda = boot drive; hdb = unused; hdc = DVD burner; hdd = second drive".

2. I changed my hdparm commands in bootmisc.sh from

to


ie: I now set the "interup umask" flag to 0. The drive_cmd error messages are no longer being produced on the boot. I will need to run for a few days to see if this has any impact on my stability.

Marc

Posting the solution in case anyone has the same problem and finds this thread on a search. I did the following:

1, Edited "/etc/lilo.conf" and added "noapic" to the "append" line,

2. Ran "lilo -v"

3. Rebooted.

The APIC errors are gone and hyper-threading still works...

Marc