[PlanetCCRMA] Problems with Redhat kernel

[R Parker]

Take what I say with a grain of salt. My guess is that
something in the new kernel is telling hda to perform
with set of specs that it's not capable of.

I suppose you'll need to gather the specs for the
disk, read up on the hdparm program and figure out
where RH is telling the disk to do X.

My hda (ide) is reporting "hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }" which I believe means it's
being told to transfer data at a rate that it's not
capable of doing. In my case, ide resets to lower
rates until the drive passes the test. So, I just
leave the damned thing to error because once the
correct parameter is met it is retained until a
reboot. The error only occurs during boot because
that's when the rate is set. I could probably find the
correct drive specs and pass them to the kernel from
grub or a RH config file but...I'm a bad person.

I know my example isn't exactly what you are seeing
but it might be indicative of something. Here's my
theory; when we don't have the answer, we should
immediately pack our brains full of as much unrelated
information as possible. While this causes confusion
it also excersizes the brain and makes it stronger.
When the brain is stronger we solve our problems with
greater ease and effiecency. If you know what I mean,
let me know. It'll make two of us.

ron 

--- Laurel Ann Murphy
<annieirishpianist147@eudoramail.com> wrote:
> Hi.  I just installed the Redhat kernel with
> low-latency patch, kernel version
> 2.4.24-2.2140.rhfc1.caps. I'm experiencing problems
> with it.  The same problems occur with the newest
> kernel avaliable for Fedora Core and the Planet
> CCRMA kernel version 2.2.24-1.11.rhfc1.ccrma, but
> not with the original kernel, version
> 2.24.2-2.2061.nptl.  The errors I'm getting follow.
> 
> hda:  dma-timer expiry - dma status==0x61
> hda:  dma-timer expiry - dma status =0x61
> hda error waiting for DMA
> hda timeout retry:  status=0xd0 (Busy)
> 
> ide0:  reset:  success
> 
> The computer freezes when this message appears on 
> the console.  I have this same problem with the
> Fedora Core kernel 2.4.24-2.2174.nptl.  Even if the
> computer stops freezing after a while, fsck needs
> run manually after every boot or reboot.  It needs
> run even if I have shut down cleanly.  I've never
> experienced this problem with Redhat 8 or 9.  I do
> know that it has something to do with the hard
> drive.  Is there any way to correct this problem?
> 
> 
> 
> Need a new email address that people can remember
> Check out the new EudoraMail at
> http://www.eudoramail.com
> 
> _______________________________________________
> PlanetCCRMA mailing list
> PlanetCCRMA@ccrma.stanford.edu
>
http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma


__________________________________
Do you Yahoo!?
Yahoo! Finance Tax Center - File online. File on time.
http://taxes.yahoo.com/filing.html