Subject: Re: 1.6 on IPC (tagged queuing bug still there)
To: NetBSD/sparc Discussion List <port-sparc@NetBSD.ORG>
From: Jon Buller <jon@bullers.net>
List: port-sparc
Date: 09/04/2002 19:40:05
In message <20020905010146.D030AAC@proven.weird.com>, Greg A. Woods writes:
>[ On Wednesday, September 4, 2002 at 16:00:19 (-0700), Jon Buller wrote: ]
>> Subject: Re: 1.6 on IPC (tagged queuing bug still there)
>>
>> In message <20020904101359.A10768@antioche.lip6.fr>, Manuel Bouyer writes:
>> >On Wed, Sep 04, 2002 at 09:03:32AM +0900, Izumi Tsutsui wrote:
>> >> In article <20020903195533.GA382@antioche.eu.org>
>> >> bouyer@antioche.eu.org wrote:
>> >>
>> >> > On Wed, Sep 04, 2002 at 01:15:09AM +0900, Izumi Tsutsui wrote:
>> >>
>> >> > > I think only ESP100 has the problem. How about this patch?
>> >>
>> >> If ESP100 cannot handle tagged queuing at all, your patch is better.
>> >> But it is actually implemented even on ESP100 (which doesn't have SELATN3
>>
>> Could this be the same problem I just ran into on my LX?
>>
>>[[....]]
>>
>> esp0 at dma0 slot 4 offset 0x8800000 level 4: ESP200, 40MHz, SCSI ID 7
>> esp1 at dma1 slot 1 offset 0x80000 level 3 (ipl 5): ESP200, 40MHz, SCSI ID 7
>
>You don't seem to have an ESP100, so no, I don't think so.
Well, yea, that part I thought might be different too, but I did
hear someone saying they had seen the bug on a SS10, so it might
be more general than just ESP100. Just out of curiosity, what are
the effects of the bug? Hang at boot? Panic at boot? Panic on
heavy usage of a tagged disk? Random lossage and data corruption?
Jon