I had a READ_DMA timeout situation which I'm pretty sure was
related to a drive problem.
I'm running 5.3-RELEASE-p5 on an older machine (333 MHz AMD
K6). The 20 GB hard drive in this system periodically, but
only occasionally, gave READ_DMA timeout errors. These errors
sometimes cited identical
Johny Mattsson wrote:
> Basically, the problem seems to be related to using more than one
> channel on the IDE controller.
This isn't a solution to my problem. I only have one hard drive.
It's 120GB Seagate. We seem to have different problems, btw.
I also don't think, my problem is ATA-related.
Hi all,
Today I've taken a fresh stab at the problem (I'm never at my best at
5am in the morning having worked through the night), and I have managed
to come up with what appears to amount to a successful workaround. It
would be good if my observations could be confirmed by someone else.
Bas
I don't think it is a hardware problem. Unless you replace it with
the exact same hardware, it'll be difficult to determine if it was the
hardware.
I haven't had any issues with 5.3R or any stable version before April
15. I am going to do some checking this weekend and see if it is
hardware or s
twesky wrote:
I am having ATA_DMA errors on 5.4R and 5 STABLE up to June 16 (haven't
done a cvsup again). It doesn't happen on 5.3R or lower.
I've just upgraded my fileserver from 5.1-R to 5.4-R, and I'm seeing
this problem too now on 3 out of 4 drives.
The exact error message is below:
I wrote:
>So, kernel got the DMA error at boot and couldn't mount the root fs.
Ah, btw.. it's a SATA disk, on an ICH6 SATA150 controller.
mkb.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsub
Jayton Garnett <[EMAIL PROTECTED]> writes:
>I had a similar problem and i changed system cases where i was getting a
>ICRC error and FreeBSD refused to load or even mount the root fs, it was
>also giving errors with something to do with the ATA something or other,
>it turned out to be the cable
twesky wrote:
> My laptop works fine with Fedora Core 4. I'm not sure it's a hardware
> issue, and I don't have an identical laptop to test. Do we know the
> last working stable version?
I just compiled the kernel from May 26th. Works fine. It looks like
for me it's broken between May 26th and M
Jayton Garnett wrote:
I had a similar problem and i changed system cases where i was getting
a ICRC error and FreeBSD refused to load or even mount the root fs, it
was also giving errors with something to do with the ATA something or
other, it turned out to be the cable i used after rebuilding
I had a similar problem and i changed system cases where i was getting a
ICRC error and FreeBSD refused to load or even mount the root fs, it was
also giving errors with something to do with the ATA something or other,
it turned out to be the cable i used after rebuilding the system in the
new
Tony Byrne wrote:
Hello Bob,
can be hardware reasons for timeouts such as a dying disk or cable,
but I think we've eliminated these in our case. [etc]
BB> Don't ignore the possibility of failing controller hardware. We had
BB> comparable mysterious problems on a client system, cau
Here is my controller:
atapci0: port
0x1860-0x186f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on
pci0
ata0: channel #0 on atapci0
ata1: channel #1 on atapci0
The last known good stable version for me was aprox April 25, my next
cvsup was May 17, but I have problems with 5.4 Release so I
twesky wrote:
> I am having ATA_DMA errors on 5.4R and 5 STABLE up to June 16 (haven't
> done a cvsup again). It doesn't happen on 5.3R or lower.
I have got same problem. I tried yesterday's kernel and I got lots of
ATA DMA errors. A question: do you have a VIA IDE controller like mine?
atapci0:
13 matches
Mail list logo
