Received:  by oss.sgi.com id <S553798AbRCBQnm>;
	Fri, 2 Mar 2001 08:43:42 -0800
Received: from sgi.SGI.COM ([192.48.153.1]:38729 "EHLO sgi.com")
	by oss.sgi.com with ESMTP id <S553788AbRCBQng>;
	Fri, 2 Mar 2001 08:43:36 -0800
Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) 
	by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam:
       SGI does not authorize the use of its proprietary
       systems or networks for unsolicited or bulk email
       from the Internet.) 
	via ESMTP id IAA09328
	for <linux-xfs@oss.sgi.com>; Fri, 2 Mar 2001 08:43:33 -0800 (PST)
	mail_from (chait@getafix.engr.sgi.com)
Received: from getafix.engr.sgi.com (IDENT:root@getafix.engr.sgi.com [163.154.5.110])
	by cthulhu.engr.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id IAA39427;
	Fri, 2 Mar 2001 08:42:17 -0800 (PST)
Received: from localhost (chait@localhost)
	by getafix.engr.sgi.com (8.9.3/8.9.3) with ESMTP id IAA20622;
	Fri, 2 Mar 2001 08:38:19 -0500
Date:   Fri, 2 Mar 2001 08:38:18 -0500 (EST)
From:   Chaitanya Tumuluri <chait@getafix.engr.sgi.com>
To:     Thomas Graichen <thomas.graichen@innominate.com>
cc:     linux-xfs@oss.sgi.com
Subject: Re: kio on non-x86
In-Reply-To: <news2mail-97oct1$d7c$1@mate.bln.innominate.de>
Message-ID: <Pine.LNX.4.21.0103020830520.20445-100000@getafix.engr.sgi.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-xfs@oss.sgi.com
Precedence: bulk
Return-Path: <owner-linux-xfs@oss.sgi.com>
X-Orcpt: rfc822;linux-xfs-outgoing

On 2 Mar 2001, Thomas Graichen wrote:
> Steve Lord <lord@sgi.com> wrote:
> >> just updated the kernel on my ppc machine yesterday - worked all fine
> >> so far ... that i tried the kio and kiocluster options on the ppc too
> >> and ran into problems: as soon as i write to the fs it detects an io
> >> error and shuts down ... thus a few questions:
> 
> > I presume the same devices worked OK without kio, did they work OK after
> > this shutdown?

Hi,

Do you have the error messages? 
AFAIK, kiobuf code is _not_ arch specific.

> >> * am i right in assuming that the kio stuff does not contain any
> >>   arch specific parts so it should - in principle - work also on
> >>   the pcc which would leave endian or gcc issues as a possible
> >>   reason for the problem?
> 
> > I think this is true, there are no os specific components, where you using
> > ide or scsi? The ide kio code is specific to having dma turned on. So which
> > combination was this?
> 
> it's ide and dma turned on

There are no arch specific components to the kiobuf code. Though, if you
are using more than 1GB there may be an issue with highmem bouncing code
in kiobuf I/O. How much memory do you have on your system?

> >> * does anyone have an idea off-mind what might be the reson for
> >>   this? ... i'll turn on all the debugging options and see if i
> >>   get any more information out of it this evening i think
> 
> > Chait may have some suggestions, but the specific hardware combination is
> > the most interesting part of the equation right now.
> 
> thanks - as said i waill (and can) do more testing this evening

Error messages, if any, would help....I'll wait for the results from
your tests.

Cheers,
-Chait.