All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel@corrosive.freeserve.co.uk
To: linux-kernel@vger.kernel.org
Subject: IDE Problems on SIS 735?
Date: Wed, 5 Sep 2001 08:52:51 +0100	[thread overview]
Message-ID: <20010905085251.A3154@corrosive.freeserve.co.uk> (raw)

Hi,
I've been having repeated DMA problems on my SIS 735 based board, I've done a
search for the meaning of the error message I'm getting, but I must be looking
in the wrong places since I can't seem to find something that explains it
fully.  Since this chipset is fairly new I thought I'd mention it here to see
if anyone has an idea what might be wrong (I'm suspecting the cables, but I've
already swapped them over once..).

I've stuck some (possibly) useful/relevant information below.  I'm running
2.4.9-ac7.

Cheers,
Adrian.

(Boot information)
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes
SIS5513: IDE controller on PCI bus 00 dev 15
SIS5513: chipset revision 208
SIS5513: not 100% native mode: will probe irqs later
SiS735
    ide0: BM-DMA at 0xff00-0xff07, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xff08-0xff0f, BIOS settings: hdc:DMA, hdd:DMA
hda: Maxtor 91024U4, ATA DISK drive
hdb: FUJITSU MPE3064AT, ATA DISK drive
hdc: Hewlett-Packard CD-Writer Plus 9300, ATAPI CD/DVD-ROM drive
hdd: Pioneer DVD-ROM ATAPIModel DVD-104S 020, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: 19999728 sectors (10240 MB) w/2048KiB Cache, CHS=1244/255/63, UDMA(66)
hdb: 12672450 sectors (6488 MB) w/512KiB Cache, CHS=788/255/63, UDMA(33)
Partition check:
 hda: hda1 hda2 hda3 < hda5 hda6 hda7 hda8 hda9 >
 hdb: hdb1 hdb2 < hdb5 >

(Error message itself)
hda: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hda: drive not ready for command

(Result from "cat /proc/ide/sis")
--------------- Primary Channel ---------------- Secondary Channel -------------
Channel Status: On 	 	 	 	 On 
Operation Mode: Compatible 	 	 	 Compatible 
Cable Type:     80 pins 	 	 	 80 pins
Prefetch Count: 512 	 	 	 	 512
Drive 0:        Postwrite Enabled 	 	 Postwrite Disabled
                Prefetch  Enabled 	 	 Prefetch  Disabled
                UDMA Enabled 	 	 	 UDMA Enabled
                UDMA Cycle Time    2 CLK 	 UDMA Cycle Time    2 CLK
                Data Active Time   2 PCICLK 	 Data Active Time   5 PCICLK
                Data Recovery Time 1 PCICLK 	 Data Recovery Time 1 PCICLK
Drive 1:        Postwrite Enabled 	 	 Postwrite Disabled
                Prefetch  Enabled 	 	 Prefetch  Disabled
                UDMA Enabled 	 	 	 UDMA Enabled
                UDMA Cycle Time    2 CLK 	 UDMA Cycle Time    2 CLK
                Data Active Time   2 PCICLK 	 Data Active Time   2 PCICLK
                Data Recovery Time 1 PCICLK 	 Data Recovery Time 1 PCICLK


             reply	other threads:[~2001-09-05  7:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-05  7:52 kernel [this message]
2001-09-05 12:01 ` IDE Problems on SIS 735? Alan Cox
2001-09-05 17:59   ` Adrian Burgess
2001-09-09 20:49     ` IDE Problems on SIS 735? (continued) Adrian Burgess
2001-09-11  4:03       ` Matthew S. Hallacy

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=20010905085251.A3154@corrosive.freeserve.co.uk \
    --to=kernel@corrosive.freeserve.co.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.