Return-Path: <linux-kernel-owner+willy=40w.ods.org@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S262941AbTI2Jl6 (ORCPT <rfc822;willy@w.ods.org>);
	Mon, 29 Sep 2003 05:41:58 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262942AbTI2Jl6
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Mon, 29 Sep 2003 05:41:58 -0400
Received: from 213-187-164-3.dd.nextgentel.com ([213.187.164.3]:60935 "EHLO
	ford.pronto.tv") by vger.kernel.org with ESMTP id S262941AbTI2Jl4
	(ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Mon, 29 Sep 2003 05:41:56 -0400
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Michael Frank <mhf@linuxmail.org>, linux-kernel@vger.kernel.org
Subject: Re: [BUG?] SIS IDE DMA errors
References: <yw1x7k3vlokf.fsf@users.sourceforge.net>
	<200309262208.30582.mhf@linuxmail.org>
	<yw1x3cejlk34.fsf@users.sourceforge.net>
	<200309262332.30091.mhf@linuxmail.org> <20030926165957.GA11150@ucw.cz>
	<yw1x7k3vjw8o.fsf@users.sourceforge.net>
	<20030926175358.GA12072@ucw.cz>
	<yw1x3cejjvdw.fsf@users.sourceforge.net>
	<20030926183323.GA12614@ucw.cz>
From: mru@users.sourceforge.net (=?iso-8859-1?q?M=E5ns_Rullg=E5rd?=)
Date: Mon, 29 Sep 2003 11:22:28 +0200
In-Reply-To: <20030926183323.GA12614@ucw.cz> (Vojtech Pavlik's message of
 "Fri, 26 Sep 2003 20:33:23 +0200")
Message-ID: <yw1xy8w8uey3.fsf@users.sourceforge.net>
User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Rational FORTRAN, linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

Vojtech Pavlik <vojtech@suse.cz> writes:

>> > Can you send me the output of 'lspci -vvxxx' of the IDE device?
>> > I'll take a look to see if it looks correct.
>> 
>> Here you go:
>
> Thanks.
>
>> 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0) (prog-if 80 [Master])
>>         Subsystem: Asustek Computer, Inc.: Unknown device 1688
>>         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
>>         Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>>         Latency: 128
>>         Region 4: I/O ports at b800 [size=16]
>> 00: 39 10 13 55 07 00 00 00 d0 80 01 01 00 80 80 00
>> 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 20: 01 b8 00 00 00 00 00 00 00 00 00 00 43 10 88 16
>> 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 40: 31 81 00 00 31 85 00 00 08 01 e6 51 00 02 00 02
>
> Ok, this means:
>
> 31 - hda: 90ns data active time, 30 ns data recovery time (PIO4)
> 41 - hda: UDMA enabled, UDMA mode 5 (UDMA100)
> 00 - hdb: 240ns/360ns (PIO0) - no drive present
> 00 - hdb: UDMA disabled
> 31 - hdc: 90ns/30ns PIO4
> 85 - hdc: UDMA enabled, UDMA mode 2 (UDMA33)
> 00 - hdd: 240ns/360ns (PIO0) - no drive present
> 00 - hdd: UDMA disabled
>
> So the config is correct if you have /dev/hda your harddrive, that's
> capable of UDMA100 and /dev/hdc a CDROM and capable of UDMA33. Is that
> right?

That's it.

> 08 - 80-wire cables (needed for UDMA44 and higher) NOT installed.
>      FIFO threshold set to 3/4 for read and to 1/4 for write.
>
> 01 - IDE controller in compatibility mode. Native and test modes
>      disabled. (normal)
>
> e6 - PCI burst enable, EDB R-R pipeline enable, Fast postwrite enable,
>      device ID masqueraded as sis5513 (although real is 5517)
>      channels 0 and 1 enabled in normal mode
>
> 51 - Postwrite enabled on hda and hdc, prefetch on hda only
>
> 00 02 - 512 bytes prefetch size for hda
> 00 02 - 512 bytes prefetch size for hdc
>
> All this is OK, possibly except for the 80-wire cable not being present,
> but if this is a notebook, there might be a completely different cable
> type than what's standard, and the detection might not work there.

I've got no idea what the cable is like.  Is there anything to be
learned from opening the beast?  Anything in particular to look for?

-- 
M?ns Rullg?rd
mru@users.sf.net
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/