On 3/14/01 3:18 AM, "Hauke Fath" <hauke@Espresso.Rhein-Neckar.DE> wrote:

> At 17:07 Uhr +0100 13.3.2001, Scott Boone wrote:
>> 1. I was still getting the following errors. I'm going to be watching to see
>> if they are more or less, in frequency. DOES ANYONE KNOW WHAT THESE ARE
>> SAYING?
>>>>>> I am getting this error VERY frequently (actually, I whole bunch of ones
>>>>>> SIMILAR to it, I just grabbed this as an example):
>>>>>> 
>>>>>> sd0(esp0:0:0):  Check Condition on CDB: 0x0a 00 2c 10 10 00
>>>>>>    SENSE KEY:  Recovered Error
>>>>>>   INFO FIELD:  11292
>>>>>> COMMAND INFO:  3604808 (0x370148)
>>>>>>     ASC/ASCQ:  Peripheral Device Write Fault
>>>>>>         SKSV:  Actual Retry Count: 1
> 
> The device (disk) had a problem with writing data that went away when
> retrying ("soft error"). Re-check your bus termination and cabling (esp.
> power: I have had at least two cases where flaky disk operation was caused
> by bad power cable plugs!).


What I am most interested in is the Check Condition code, the info field,
and the command info. What are the human readable equivalents? I'm figuring
that somewhere in there is the block on the drive where the write took
place, but I'm not sure where. I notice a lot of patterns in my logs, like
90% of the Check Condition on CDB end with 10 00. But the numbers are not
completely the same (there are SOME that are the same tho). That's why, if
maybe that translates into something like a cylinder or a head or platter,
it might be pointing to a solution.


>> 2. Your kernel did not like my Farallon NuBus Etherpeek card.
>> Your kernel:
>> Mar 13 10:24:11 bsdserver /netbsd: nubus0 at mainbus0
>> Mar 13 10:24:11 bsdserver /netbsd: nubus0 slot e: Farallon EtherMac II-TP
>> (Vendor: Farallon, Part: PN 590a-TP) Type: 0004 0001 010c 0100 not
>> configured
>> 
>> Pre1.6 32 kernel:
>> nubus0 at mainbus0
>> ae0 at nubus0 slot e: Farallon EtherMac II-TP, 32KB memory
>> ae0: Ethernet address 00:00:c5:41:33:0f
> 
> Looks like the card ID was added in -current and not yet pulled up to the
> release branch(es).

When will the next Pre 1.5.1 ALPHA be hitting the streets? And do you think
that will be in it?

-- 

Scott Boone
Scott@ScottBoone.com
717.860.2666