Chaitanya Tumuluri <chait@xxxxxxxxxxxxxxxxxxxx> wrote:
>> > I presume the same devices worked OK without kio, did they work OK after
>> > this shutdown?
> Do you have the error messages?
> AFAIK, kiobuf code is _not_ arch specific.
none so far - but i did not have any of the debugging options turned
on (no idea if they would help - maybe not)
>> >> * 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?
128MB - so no problem here (also keep in mind this is on ppc not i386)
>> >> * 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.
more later - then i'm at the machine
t
--
thomas.graichen@xxxxxxxxxxxxxx
innominate AG
the linux architects
tel: +49-30-308806-13 fax: -77 http://www.innominate.com
|