> Hans, what ATA modes do you see this problem in? UDMA? MWDMA? Or does just
> having the patch applied but still using PIO mode expose the problem?
This problem occurs in MWDMA 2 mode.
Happy new year
Mit freundlichen Grüßen
Hans Lehmann
Softwareentwicklung
Telefon +49 (0)2191-67-2520
Tim, Grant
here are some more information.
I think there is a also a problem with memory after FEC crasched.
[EMAIL PROTECTED]:~ free
total used free shared buffers
Mem: 12710026424 1006760 432
Swap:
Tim, Grant,
just an info.
Very often the Bestcomm-FEC crashed without any error logs if I initiate a
transaction over FEC and save the file to disk (I rememeber I have read
something like that). A restart of FEC don't work.
But no I figured out, if I connect to the other ethernet port of our
Hmm even with DMA built in my disk (Seagate 5400.8) still "configured" for
PIO4.
This is probably my fault. Tim, could you respin the patch anyway since
it doesn't apply cleanly to the 2.6.27 kernel? :)
This did work for me once but we were still using a SUSE kernel (from
11.0) to patch it onto
We take a vanilla kernel with rt11 patches from Ingo Mollnar.
Here are the section of my boot messages
ata: MPC52xx IDE/ATA libata driver
scsi0 : mpc52xx_ata
ata1: PATA max UDMA/33 ata_regs 0xf0003a00 irq 135
ata1.00: ATA-0: ELITE PRO CF CARD 1GB, 20070131, max MWDMA2
ata1.00: 2031120 sectors, mu
