From: "Adam McKenna" <adam-dated-1007281507.c7177f@flounder.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: DMA problem (?) w/ 2.4.6-xfs and ServerWorks OSB4 Chipset
Date: Tue, 27 Nov 2001 00:25:05 -0800 [thread overview]
Message-ID: <20011127002505.V252@flounder.net> (raw)
In-Reply-To: <20011113023029.A15075@flounder.net> <E163bNB-0000pS-00@the-village.bc.nu>
In-Reply-To: <E163bNB-0000pS-00@the-village.bc.nu>
On Tue, Nov 13, 2001 at 11:04:57AM +0000, Alan Cox wrote:
> > I am having problems with both UDMA and Multiword DMA. The problem doesn't
> > go away unless I disable CONFIG_IDEDMA_PCI_AUTO.
> >
> > I don't know if there is actual FS corruption with MWord DMA, but there is
> > definitely a "hang" for a few seconds accompanied by a DMA error.
>
> I've no other reports from MWDMA other than the usual "CDROM that doesnt
> handle DMA" things
ops01:~# hdparm -Ii /dev/hda
/dev/hda:
Model=IBM-DTLA-307075, FwRev=TXAOA50C, SerialNo=YSDYSG5S166
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=40
BuffType=3(DualPortCache), BuffSize=1916kB, MaxMultSect=16, MultSect=16
DblWordIO=no, OldPIO=2, DMA=yes, OldDMA=2
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=150136560
tDMA={min:120,rec:120}, DMA modes: mword0 mword1 *mword2
IORDY=on/off, tPIO={min:240,w/IORDY:120}, PIO modes: mode3 mode4
UDMA modes: mode0 mode1 mode2 mode3 mode4 mode5
Model=BI-MTDAL3-7070 5 , FwRev=XTOA5AC0,
SerialNo= Y DSSY5G1S66
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=40
BuffType=3(DualPortCache), BuffSize=1916kB, MaxMultSect=16, MultSect=16
DblWordIO=no, OldPIO=2, DMA=yes, OldDMA=2
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=150136560
tDMA={min:120,rec:120}, DMA modes: mword0 mword1 *mword2
IORDY=on/off, tPIO={min:240,w/IORDY:120}, PIO modes: mode3 mode4
UDMA modes: mode0 mode1 mode2 mode3 mode4 mode5
ops01:~# hdparm -Ii /dev/hdb
/dev/hdb:
Model=Maxtor 4W100H6, FwRev=AAH01310, SerialNo=W6H2JCRC
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57
BuffType=3(DualPortCache), BuffSize=2048kB, MaxMultSect=16, MultSect=16
DblWordIO=no, OldPIO=2, DMA=yes, OldDMA=0
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=195711264
tDMA={min:120,rec:120}, DMA modes: mword0 mword1 *mword2
IORDY=on/off, tPIO={min:120,w/IORDY:120}, PIO modes: mode3 mode4
UDMA modes: mode0 mode1 mode2 mode3 mode4 mode5
Model=aMtxro4 1W006H , FwRev=AA0H3101,
SerialNo=6W2HCJCR
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57
BuffType=3(DualPortCache), BuffSize=2048kB, MaxMultSect=16, MultSect=16
DblWordIO=no, OldPIO=2, DMA=yes, OldDMA=0
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=195711264
tDMA={min:120,rec:120}, DMA modes: mword0 mword1 *mword2
IORDY=on/off, tPIO={min:120,w/IORDY:120}, PIO modes: mode3 mode4
UDMA modes: mode0 mode1 mode2 mode3 mode4 mode5
Here is a sample of the I/O errors:
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=15220172,
sector=1548794
end_request: I/O error, dev 03:05 (hda), sector 1548794
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=15220173,
sector=1548795
end_request: I/O error, dev 03:05 (hda), sector 1548795
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=15220174,
sector=1548796
end_request: I/O error, dev 03:05 (hda), sector 1548796
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=15220175,
sector=1548797
end_request: I/O error, dev 03:05 (hda), sector 1548797
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=15220176,
sector=1548798
end_request: I/O error, dev 03:05 (hda), sector 1548798
--Adam
--
Adam McKenna <adam@flounder.net> | GPG: 17A4 11F7 5E7E C2E7 08AA
http://flounder.net/publickey.html | 38B0 05D0 8BF7 2C6D 110A
next prev parent reply other threads:[~2001-11-27 8:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-25 1:25 DMA problem (?) w/ 2.4.6-xfs and ServerWorks OSB4 Chipset Adam McKenna
2001-07-25 3:08 ` Rico Tudor
2001-07-26 16:11 ` Facing problem Dipak Biswas
2001-07-26 17:28 ` Fwd: " Dipak Biswas
2001-07-25 13:30 ` DMA problem (?) w/ 2.4.6-xfs and ServerWorks OSB4 Chipset Alan Cox
2001-11-13 7:46 ` Adam McKenna
2001-11-13 9:51 ` Alan Cox
2001-11-13 10:30 ` Adam McKenna
2001-11-13 11:04 ` Alan Cox
2001-11-27 8:25 ` Adam McKenna [this message]
2001-07-25 15:46 ` Larry Sendlosky
-- strict thread matches above, loose matches on Subject: below --
2001-07-29 21:50 Marvin Justice
2001-07-29 22:29 ` Ignacio Vazquez-Abrams
2001-07-29 22:37 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011127002505.V252@flounder.net \
--to=adam-dated-1007281507.c7177f@flounder.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox