adst70 troubles with OpenServer 6 - SCO

This is a discussion on adst70 troubles with OpenServer 6 - SCO ; Hi, We have a SCO OpenServer 6 box with 2 SCSI adapters. One is an LSI MegaRaid adapter that's used for the hard drives (no problems with this one), the other is an Adaptec Ultra 160 card that's used for ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: adst70 troubles with OpenServer 6

  1. adst70 troubles with OpenServer 6

    Hi,
    We have a SCO OpenServer 6 box with 2 SCSI adapters. One is an LSI
    MegaRaid adapter that's used for the hard drives (no problems with this
    one), the other is an Adaptec Ultra 160 card that's used for the tape
    drive (this is the one causing trouble).

    As the title suggests the Adaptec card uses the adst70 driver that
    comes with OpenServer 6.

    Also, we have applied Maintainance Pack 2 right after installing
    OpenServer 6 and before adding the Adaptec card.

    The card and tape drive were initially set up about a month ago, and
    everything was working well with no apparent problems until late last
    week, when we started getting random take errors. Cleaning the tape
    drive / replacing tapes did not help.

    This morning I tried running a backup manually (as opposed to a
    scheduled one), after running for a few hours, the server rebooted with
    a kernel panic. The following was in the syslog:


    ---- /usr/adm/syslog --------------------

    Jul 17 11:04:36 scobkp WARNING: Tape Driver: HA 2 TC 2 LU 0 - CHECK
    CONDITION:
    Jul 17 11:04:36 scobkp A "MEDIUM ERROR" condition has been detected.
    Jul 17 11:04:36 scobkp Additional data = "UNRECOVERED READ ERROR".
    Jul 17 11:04:36 scobkp Logical block address = 0xEAFCFFFF
    Jul 17 11:11:18 scobkp
    Jul 17 11:11:18 scobkp WARNING: adst70: Command timed out (Abort)
    [810070D0] (ha= 2)
    PANIC: kernel-mode address fault on kernel address 0xEAC73802
    Kernel Page Fault from (cs:eip) = (100:C00C52B5):
    eax=442 ebx=EAC73802 ecx=803CA90 edx=0
    esi=FFFF6394 edi=400 ebp=FFFF2408 esp=D405AA18
    Raw stack dump begins at 0xD405AA18:
    A18 00000001 D405AA60 E5AB2E20 C0189C77 C00CFC64 E622D16F FFFF6394
    0000003B
    A38 C0000F92 00000400 00000000 00000001 00000100 C0001037 0803CA90
    00000000
    A58 D405AA60 00000100 000000AA E622D144 0000003B C00045C9 0803CA90
    00000000
    A78 00000001 00000000 D405AB24 D405ABB0 00000000 00000005 00000001
    E622D100
    A98 00000000 C018ADF5 D405AAA4 00000001 C018AADD F4153F20 00000000
    C018A8A5
    AB8 D405AABC 00008000 C018CBBB F4154450 00000000 CB4A95C0 00000010
    F58CDA60
    AD8 F58CDA60 C0003D80 F58CDA60 D405ABB0 00000000 CB4A95C0 ED627A40
    FFFF6374
    AF8 00000000 00000800 00000000 00000000 C0004012 C000405E C000408B
    FFFF46DA
    B18 00000000 00000005 00000001 00000000 C0004283 0803CA90 00000000
    00000001
    B38 00000748 D405AB68 00000000 00000000 00000005 D405AF08 00000000
    00000030

    PANIC REGISTERS:
    kcp:d405ac08 trp: - efl: - eip:c018cffb xcmn_panic+5b()
    eax:d405ac08 ebx: 0 ecx:c04da958 edx: 7 cs: 100 ds: 108
    fs: 0
    esi:ffff62a0 edi:c022babc ebp:d405a908 esp:d405a8e8 ss: 108 es: 108
    gs: 0
    STACK TRACE FOR PROCESS 86 LWP 0:
    xcmn_panic+5b(c022babc)........................... ...esp:d405a90c
    ret:c018dfd7
    xcmn_err+1c7(3 c022babc d405a95c)....................esp:d405a940
    ret:c018aeca
    cmn_err+14(3 c022babc eac73802)......................esp:d405a950
    ret:c00d8b0f
    kpageflt+17f(0)................................... ...esp:d405a974
    ret:c016c329
    trap+239()........................................ ...esp:d405a9d4
    ret:c016c092
    TRAP 0xe from 100:c00c52b5 (r0ptr:d405a9f8)
    eax: 442 ebx:eac73802 ecx: 803ca90 edx: 0 efl: 10082
    esi:ffff6394 edi: 400 ebp:ffff2408 esp:d405aa10
    kmem_alloc+125(400 0)................................esp:d405aa38
    ret:c0000f92
    pn_get+12(803ca90 0 d405aa60)........................esp:d405aa4c
    ret:c0001037
    lookupname+17(803ca90 0 1 0 d405ab24)................esp:d405aa6c
    ret:c00045c9
    vn_open+139(803ca90 0 1 748 d405ab68 0)..............esp:d405ab28
    ret:c0004283
    copen+83(803ca90 1 bfff4748 d405ab9c)................esp:d405ab6c
    ret:c0005110
    *open+20(d405af08 d405ab9c)...........................esp:d405ab84
    ret:c016bb80
    systrap+2f0()..................................... ...esp:d405abb4
    ret:c01762e0
    SYSTEM CALL from 17:bffb27bc (r0ptr:d405abd4, ss:esp: 1f:803ca70)
    eax: 5 ebx:bfffdd44 ecx: 0 edx: 803ca90 efl: 202
    ds: 1f
    esi: 803caad edi: 803ca90 ebp:bfff4772 esp:d405abf4
    es: 1f
    Engine: 1 of 2 Procslot: 86 Lwpslot: 0 /bin/edge -zBG -TTV -zINDEX
    -zSMMR=pi
    >


    Jul 17 11:24:55 scobkp syslogd: restart
    Jul 17 11:24:55 scobkp SCO OpenServer(tm) Version 6, based on UNIX
    System V Release 5 from SCO

    ---------
    ------------------

    >From the above it really looks like the driver caused the panic.


    Is this a bug? Is there a patch or a newer version of the driver we are
    supposed to be using?

    Thanks,
    --Dmitriy


  2. Re: adst70 troubles with OpenServer 6

    Dmitriy,

    The adst70 driver you are using is the latest driver.

    The fact that this was working but is no longer working suggests to me
    that
    you may have a problem with the Server hardware. If the server is only
    panicing when using the tape drive and is panicing consistently then
    I would look to:

    1) Try a different tape drive on the SCSI bus to see if you can
    replicate.
    If you cannot then it could be that the tape drive is faulty

    2) Try a different set of SCSI cables and terminators on the bus

    3) Try reseating and replacing the Adaptec controller to see if it is
    at
    fault

    Regards,

    John


+ Reply to Thread