Fujitsu Hard drives & Linux - problems
Shawn Starr
The motherboard I have is an Acer AP53:
I flashed the BIOS to the latest without issue
(AP53R3C0)
The problem can be reproduced when you copy from the other channel to the
channel the Fujitsu drive is on (HDA --> HDC) DMA timeouts happen.
It has an 430HX PCI chipset and 2 USB ports which Linux detects with USB
support compiled in.
On Thu, 3 Aug 2000, Benson Chow wrote:
> Hi,
> I have a fujitsu drive, but it's a different model - mpd3137ah. It's also
> a udma (but udma66). I have a piix4 controller though - but it shouldnt
> matter... It works fine...
>
> I think the PIIX3 controller isn't too bad. I've owned several
> motherboards with PIIX3 and they've all been pretty good in terms of
> DMA... albeit they're only DMA16 devices. My PIIX3 motherboard is now
> hooked up to a UDMA33 drive at DMA16, and it's working fine.
>
> So perhaps you have a bad motherboard? Yeah, it doesn't seem right that
> it's not working... Do other brands of harddrives work with DMA?
>
> -bc
>
> On Wed, 2 Aug 2000, Shawn Starr wrote:
>
> >
> > hda: WDC AC32500H, 2441MB w/128kB Cache, CHS=620/128/63
> > hdb: CD-912E/ATK, ATAPI CDROM drive
> > hdb: ATAPI 4X CD-ROM drive, 120kB Cache
> >
> > hdc: FUJITSU MPE3064AT, 6187MB w/512kB Cache, CHS=13410/15/63, (U)DM
> >
> > I have the above models on my system. As well as a CD-ROM (12x) it doesn't
> > see it as a 12x but thats another issue ;-)
> >
> > The problem I'm getting is this, When DMA is turned on for the FUJITSU
> > drive Linux something doesn't like it I get the following error
> >
> > hdc: timeout waiting for DMA
> > hdc: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
> >
> > When DMA is disabled the drive is fine, this DMA timeout happens
> > randomly. I dont know whats causing it. I replaced the IDE cables, and
> > even replaced the drive for a new one which is the same model same
> > problem. This drive can support UDMA33/66.
> >
> > Here's part of the kern.log from bootup.
> >
> > Linux version 2.2.16 (ro...@visualnet.dhs.org) (gcc version 2.95.2 19991024 (release)) Jun 7 23:38:51 EDT 2000
> > Detected 199435 kHz processor.
> > Console: colour VGA+ 80x25
> > Calibrating delay loop... 398.13 BogoMIPS
> > Memory: 63344k/65536k available (872k kernel code, 416k reserved, 860k data, 44k init)
> > Dentry hash table entries: 8192 (order 4, 64k)
> > Buffer cache hash table entries: 65536 (order 6, 256k)
> > Page cache hash table entries: 16384 (order 4, 64k)
> > CPU: Intel Pentium 75 - 200 stepping 0c
> > Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
> > Checking 'hlt' instruction... OK.
> > Intel Pentium with F0 0F bug - workaround enabled.
> > POSIX conformance testing by UNIFIX
> > PCI: PCI BIOS revision 2.10 entry at 0xfdb91
> > PCI: Using configuration type 1
> > PCI: Probing PCI hardware
> > Linux NET4.0 for Linux 2.2
> > Based upon Swansea University Computer Society NET3.039
> > NET4: Unix domain sockets 1.0 for Linux NET4.0.
> > NET4: Linux TCP/IP 1.0 for NET4.0
> > IP Protocols: ICMP, UDP, TCP
> > TCP: Hash tables configured (ehash 65536 bhash 65536)
> > Initializing RT netlink socket
> > Starting kswapd v 1.5
> > parport0: PC-style at 0x378 [SPP,PS2]
> > parport_probe: failed
> > parport0: no IEEE-1284 device present.
> > Serial driver version 4.27 with no serial options enabled
> > ttyS00 at 0x03f8 (irq = 4) is a 16550A
> > ttyS01 at 0x02f8 (irq = 3) is a 16550A
> > pty: 256 Unix98 ptys configured
> > lp0: using parport0 (polling).
> > apm: BIOS version 1.2 Flags 0x03 (Driver version 1.13)
> > Sound initialization started
> > <Sound Blaster 16 (4.13)> at 0x220 irq 5 dma 1,5
> > <Sound Blaster 16> at 0x330 irq 5 dma 0
> > Sound initialization complete
> > PIIX3: IDE controller on PCI bus 00 dev 39
> > PIIX3: not 100% native mode: will probe irqs later
> > ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio
> > ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:pio
> > hda: WDC AC32500H, ATA DISK drive
> > hdb: CD-912E/ATK, ATAPI CDROM drive
> > hdc: FUJITSU MPE3064AT, ATA DISK drive
> > ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> > ide1 at 0x170-0x177,0x376 on irq 15
> > hda: Disabling (U)DMA for WDC AC32500H
> > hda: DMA disabled
> > hda: WDC AC32500H, 2441MB w/128kB Cache, CHS=620/128/63
> > hdc: FUJITSU MPE3064AT, 6187MB w/512kB Cache, CHS=13410/15/63, (U)DMA
> > hdb: ATAPI 4X CD-ROM drive, 120kB Cache
> > Uniform CD-ROM driver Revision: 3.09
> > Floppy drive(s): fd0 is 1.44M, fd1 is 1.2M
> > FDC 0 is a post-1991 82077
> > 3Com 3c90x Version 1.0.0d 1999 <linux_...@3com.com>
> > Partition check:
> > hda: hda1 hda2
> > hdc: hdc1 hdc2
> > VFS: Mounted root (ext2 filesystem) readonly.
> > Freeing unused kernel memory: 44k freed
> >
> > I hope this is enough info for you, if anyone needs anymore or has a
> > suggestion please let me know :-)
> >
> > I am aware that the PIIX3 chipset is buggy :/ but this can't be right.
> >
> > Shawn.
> >
> >
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majo...@vger.rutgers.edu
> > Please read the FAQ at http://www.tux.org/lkml/
> >
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
Shawn Starr
I don't have windows ;-) not that I couldn't install it on the other HD
i'd have to partition and I dont wanna :-)
I dont know if this drive should be "blacklisted" since it is a UDMA33/66
drive on a real PC (unlike this Pentium 200 w/o MMX)
Yes, If I copy from one channel to the other i get IRQ DMA timeouts from
the Fujitsu drive. The WD and CD-ROM are on the primary channel the
Fujitsu is on the secondary channel as master. I dont see how the CD-Rom
would affect the drive.
On Thu, 3 Aug 2000, Benson Chow wrote:
>
> Hmmm.. that's strange. It's possible your other drive "should" also be on
> the DMA "blacklist"... I don't know -
>
> I think a friend of mine also has a fujitsu 6.4GB drive, and he never got
> it working with DMA under windows (btw, does it work under windows
> even?). He has a Via-chipset though and not an Intel.
>
> I've run DMA over these chipsets:
> 440FX / PIIX3 "Natoma" "Venus" (but it corrupts data with my Maxtor UDMA!)
> 440FX / PIIX3 Dual motherboard (Runs fine with my Maxtor UDMA)
> 440BX / PIIX4 Dual motherboard (Fujitsu)
>
> I could try the fujitsu on the PIIX3 and see what it does, but it should
> be fine...
>
> Can you cause DMA trouble if you copy from the fujitsu to the other
> channel? Reading should also cause DMA transfers to occur...
>
> BTW: I've only had this trouble you're seeing on CDROM drives. I tracked
> it down to the CDROMs because I actually have a CDROM that's implemented
> "correctly" and won't DMA timeout...
>
> -bc
>
> On Thu, 3 Aug 2000, Shawn Starr wrote:
>
> >
> > The motherboard I have is an Acer AP53:
> > I flashed the BIOS to the latest without issue
> > (AP53R3C0)
> >
> > The problem can be reproduced when you copy from the other channel to the
> > channel the Fujitsu drive is on (HDA --> HDC) DMA timeouts happen.
> >
> > It has an 430HX PCI chipset and 2 USB ports which Linux detects with USB
> > support compiled in.
> >
>
>