2.5.43 scsi _eh_ buslogic

2.5.43 scsi _eh_ buslogic

Post by andy barla » Sat, 19 Oct 2002 21:20:13



Buslogic is still not functional in 2.5.43.
Info below is from successive boots on the same system.
Two scsi HDs and one scsi cdrom.
Removing the cdrom changes nothing.

Kernel 2.4.19 has run buslogic scsi just fine:

SCSI subsystem driver Revision: 1.00
PCI: Assigned IRQ 10 for device 00:08.0
scsi: ***** BusLogic SCSI Driver Version 2.1.15 of 17 August 1998 *****

scsi0: Configuring BusLogic Model BT-958 PCI Wide Ultra SCSI Host Adapter
scsi0:   Firmware Version: 5.06J, I/O Address: 0xE800, IRQ Channel: 10/Level
scsi0:   PCI Bus: 0, Device: 8, Address: 0xED001000, Host Adapter SCSI ID: 7
scsi0:   Parity Checking: Disabled, Extended Translation: Disabled
scsi0:   Synchronous Negotiation: FFFFSFF#FFFFFFFF, Wide Negotiation: YYYYNYY#YY
YYYYYY
scsi0:   Disconnect/Reconnect: Enabled, Tagged Queuing: Enabled
scsi0:   Scatter/Gather Limit: 128 of 8192 segments, Mailboxes: 211
scsi0:   Driver Queue Depth: 211, Host Adapter Queue Depth: 192
scsi0:   Tagged Queue Depth: Automatic, Untagged Queue Depth: 3
scsi0:   Error Recovery Strategy: Default, SCSI Bus Reset: Disabled
scsi0:   SCSI Bus Termination: High Enabled, SCAM: Disabled
scsi0: *** BusLogic BT-958 Initialized Successfully ***
scsi0 : BusLogic BT-958
  Vendor: CONNER    Model: CFP2107E  2.14GB  Rev: 1423
  Type:   Direct-Access                      ANSI SCSI revision: 02
  Vendor: SEAGATE   Model: SX423451W         Rev: 9E18
  Type:   Direct-Access                      ANSI SCSI revision: 02
  Vendor: TOSHIBA   Model: CD-ROM XM-5701TA  Rev: 0167
  Type:   CD-ROM                             ANSI SCSI revision: 02
scsi0: Target 0: Queue Depth 28, Wide Synchronous at 20.0 MB/sec, offset 15
scsi0: Target 1: Queue Depth 28, Wide Synchronous at 20.0 MB/sec, offset 15
scsi0: Target 2: Queue Depth 3, Synchronous at 10.0 MB/sec, offset 8
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0
SCSI device sda: 4194303 512-byte hdwr sectors (2147 MB)
 sda: sda1 sda2
SCSI device sdb: 45322644 512-byte hdwr sectors (23205 MB)
 sdb: sdb1 sdb2 sdb3

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

Kernel 2.5.43 and earlier produce this dmesg info
(edited  redundant lines):

SCSI subsystem driver Revision: 1.00
PCI: Assigned IRQ 10 for device 00:08.0
scsi: ***** BusLogic SCSI Driver Version 2.1.16 of 18 July 2002 *****

scsi0: Configuring BusLogic Model BT-958 PCI Wide Ultra SCSI Host Adapter
scsi0:   Firmware Version: 5.06J, I/O Address: 0xE800, IRQ Channel: 10/Level
scsi0:   PCI Bus: 0, Device: 8, Address: 0xED001000, Host Adapter SCSI ID: 7
scsi0:   Parity Checking: Disabled, Extended Translation: Disabled
scsi0:   Synchronous Negotiation: FFFFSFF#FFFFFFFF, Wide Negotiation: YYYYNYY#YY
YYYYYY
scsi0:   Disconnect/Reconnect: Enabled, Tagged Queuing: Enabled
scsi0:   Scatter/Gather Limit: 128 of 8192 segments, Mailboxes: 211
scsi0:   Driver Queue Depth: 211, Host Adapter Queue Depth: 192
scsi0:   Tagged Queue Depth: Automatic, Untagged Queue Depth: 3
scsi0:   Error Recovery Strategy: Default, SCSI Bus Reset: Disabled
scsi0:   SCSI Bus Termination: High Enabled, SCAM: Disabled
scsi0: *** BusLogic BT-958 Initialized Successfully ***
scsi0 : BusLogic BT-958
  Vendor: CONNER    Model: CFP2107E  2.14GB  Rev: 1423
  Type:   Direct-Access                      ANSI SCSI revision: 02
  Vendor: SEAGATE   Model: SX423451W         Rev: 9E18
  Type:   Direct-Access                      ANSI SCSI revision: 02
scsi_eh_offline_sdevs: Device offlined - not ready or command retry failed after
 error recovery: host 0 channel 0 id 1 lun 0
scsi_eh_offline_sdevs: Device offlined - not ready or command retry failed after
 error recovery: host 0 channel 0 id 1 lun 0
scsi_eh_offline_sdevs: Device offlined - not ready or command retry failed after
 error recovery: host 0 channel 0 id 2 lun 0
  Vendor:           Model:                   Rev:
  Type:   Direct-Access                      ANSI SCSI revision: 00
scsi_eh_offline_sdevs: Device offlined - not ready or command retry failed after
 error recovery: host 0 channel 0 id 2 lun 0
scsi_eh_offline_sdevs: Device offlined - not ready or command retry failed after
 error recovery: host 0 channel 0 id 2 lun 0
scsi_eh_offline_sdevs: Device offlined - not ready or command retry failed after
 error recovery: host 0 channel 0 id 3 lun 0
  Vendor:           Model:                   Rev:
  Type:   Direct-Access                      ANSI SCSI revision: 00
.
.
.
scsi_eh_offline_sdevs: Device offlined - not ready or command retry failed after
 error recovery: host 0 channel 0 id 15 lun 0
  Vendor:           Model:                   Rev:
  Type:   Direct-Access                      ANSI SCSI revision: 00
scsi_eh_offline_sdevs: Device offlined - not ready or command retry failed after
 error recovery: host 0 channel 0 id 15 lun 0
scsi_eh_offline_sdevs: Device offlined - not ready or command retry failed after
 error recovery: host 0 channel 0 id 15 lun 0
st: Version 20021015, fixed bufsize 32768, wrt 30720, s/g segs 256
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0
Attached scsi disk sdc at scsi0, channel 0, id 2, lun 0
Attached scsi disk sdd at scsi0, channel 0, id 3, lun 0
Attached scsi disk sde at scsi0, channel 0, id 4, lun 0
Attached scsi disk sdf at scsi0, channel 0, id 5, lun 0
Attached scsi disk sdg at scsi0, channel 0, id 6, lun 0
Attached scsi disk sdh at scsi0, channel 0, id 8, lun 0
Attached scsi disk sdi at scsi0, channel 0, id 9, lun 0
Attached scsi disk sdj at scsi0, channel 0, id 10, lun 0
Attached scsi disk sdk at scsi0, channel 0, id 11, lun 0
Attached scsi disk sdl at scsi0, channel 0, id 12, lun 0
Attached scsi disk sdm at scsi0, channel 0, id 13, lun 0
Attached scsi disk sdn at scsi0, channel 0, id 14, lun 0
Attached scsi disk sdo at scsi0, channel 0, id 15, lun 0
scsi_eh_offline_sdevs: Device offlined - not ready or command retry failed after
 error recovery: host 0 channel 0 id 0 lun 0
scsi_eh_offline_sdevs: Device offlined - not ready or command retry failed after
 error recovery: host 0 channel 0 id 0 lun 0
SCSI device sda: drive cache: write through
scsi_eh_offline_sdevs: Device offlined - not ready or command retry failed after
 error recovery: host 0 channel 0 id 0 lun 0
sda : sector size 0 reported, assuming 512.
SCSI device sda: 1 512-byte hdwr sectors (0 MB)
.
.
.

scsi_eh_offline_sdevs: Device offlined - not ready or command retry failed after
 error recovery: host 0 channel 0 id 15 lun 0
scsi_eh_offline_sdevs: Device offlined - not ready or command retry failed after
 error recovery: host 0 channel 0 id 15 lun 0
SCSI device sdo: drive cache: write through
scsi_eh_offline_sdevs: Device offlined - not ready or command retry failed after
 error recovery: host 0 channel 0 id 15 lun 0
sdo : sector size 0 reported, assuming 512.
SCSI device sdo: 1 512-byte hdwr sectors (0 MB)
Initializing USB Mass Storage driver...

--

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

2.5.43 scsi _eh_ buslogic

Post by Mike Anderso » Sun, 20 Oct 2002 00:50:06


Andy,
        From looking at the driver it looks like the locking had been
update to 2.5, but that the driver error handling has not been updated.
scsi_obsolete.c has not existed in the 2.5 view for a while.

I have cc'd linux-scsi as someone on the list might be able to
give more information on the status of the driver.

So if you where previously getting timeouts / errors on probe in 2.4 the
older error handler might have been clearing things up and now nothing
is being called.

We should remove the older error handling interfaces as they are not
called and possibly print a warning if a driver loads with no error
handling functions set.

The older abort handler BusLogic_AbortCommand should be easy to change
by just adjusting the locking. I do not have one of these adapter, but
could look into the changes.

andy barlak [an...@island.net] wrote:

> Buslogic is still not functional in 2.5.43.
> Info below is from successive boots on the same system.
> Two scsi HDs and one scsi cdrom.
> Removing the cdrom changes nothing.

> Kernel 2.4.19 has run buslogic scsi just fine:

> SCSI subsystem driver Revision: 1.00
> PCI: Assigned IRQ 10 for device 00:08.0
> scsi: ***** BusLogic SCSI Driver Version 2.1.15 of 17 August 1998 *****
> scsi: Copyright 1995-1998 by Leonard N. Zubkoff <l...@dandelion.com>
> scsi0: Configuring BusLogic Model BT-958 PCI Wide Ultra SCSI Host Adapter
> scsi0:   Firmware Version: 5.06J, I/O Address: 0xE800, IRQ Channel: 10/Level
> scsi0:   PCI Bus: 0, Device: 8, Address: 0xED001000, Host Adapter SCSI ID: 7
> scsi0:   Parity Checking: Disabled, Extended Translation: Disabled
> scsi0:   Synchronous Negotiation: FFFFSFF#FFFFFFFF, Wide Negotiation: YYYYNYY#YY
> YYYYYY
> scsi0:   Disconnect/Reconnect: Enabled, Tagged Queuing: Enabled
> scsi0:   Scatter/Gather Limit: 128 of 8192 segments, Mailboxes: 211
> scsi0:   Driver Queue Depth: 211, Host Adapter Queue Depth: 192
> scsi0:   Tagged Queue Depth: Automatic, Untagged Queue Depth: 3
> scsi0:   Error Recovery Strategy: Default, SCSI Bus Reset: Disabled
> scsi0:   SCSI Bus Termination: High Enabled, SCAM: Disabled
> scsi0: *** BusLogic BT-958 Initialized Successfully ***
> scsi0 : BusLogic BT-958
>   Vendor: CONNER    Model: CFP2107E  2.14GB  Rev: 1423
>   Type:   Direct-Access                      ANSI SCSI revision: 02
>   Vendor: SEAGATE   Model: SX423451W         Rev: 9E18
>   Type:   Direct-Access                      ANSI SCSI revision: 02
>   Vendor: TOSHIBA   Model: CD-ROM XM-5701TA  Rev: 0167
>   Type:   CD-ROM                             ANSI SCSI revision: 02
> scsi0: Target 0: Queue Depth 28, Wide Synchronous at 20.0 MB/sec, offset 15
> scsi0: Target 1: Queue Depth 28, Wide Synchronous at 20.0 MB/sec, offset 15
> scsi0: Target 2: Queue Depth 3, Synchronous at 10.0 MB/sec, offset 8
> Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
> Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0
> SCSI device sda: 4194303 512-byte hdwr sectors (2147 MB)
>  sda: sda1 sda2
> SCSI device sdb: 45322644 512-byte hdwr sectors (23205 MB)
>  sdb: sdb1 sdb2 sdb3

> -----------------------------

> Kernel 2.5.43 and earlier produce this dmesg info
> (edited  redundant lines):

> SCSI subsystem driver Revision: 1.00
> PCI: Assigned IRQ 10 for device 00:08.0
> scsi: ***** BusLogic SCSI Driver Version 2.1.16 of 18 July 2002 *****
> scsi: Copyright 1995-1998 by Leonard N. Zubkoff <l...@dandelion.com>
> scsi0: Configuring BusLogic Model BT-958 PCI Wide Ultra SCSI Host Adapter
> scsi0:   Firmware Version: 5.06J, I/O Address: 0xE800, IRQ Channel: 10/Level
> scsi0:   PCI Bus: 0, Device: 8, Address: 0xED001000, Host Adapter SCSI ID: 7
> scsi0:   Parity Checking: Disabled, Extended Translation: Disabled
> scsi0:   Synchronous Negotiation: FFFFSFF#FFFFFFFF, Wide Negotiation: YYYYNYY#YY
> YYYYYY
> scsi0:   Disconnect/Reconnect: Enabled, Tagged Queuing: Enabled
> scsi0:   Scatter/Gather Limit: 128 of 8192 segments, Mailboxes: 211
> scsi0:   Driver Queue Depth: 211, Host Adapter Queue Depth: 192
> scsi0:   Tagged Queue Depth: Automatic, Untagged Queue Depth: 3
> scsi0:   Error Recovery Strategy: Default, SCSI Bus Reset: Disabled
> scsi0:   SCSI Bus Termination: High Enabled, SCAM: Disabled
> scsi0: *** BusLogic BT-958 Initialized Successfully ***
> scsi0 : BusLogic BT-958
>   Vendor: CONNER    Model: CFP2107E  2.14GB  Rev: 1423
>   Type:   Direct-Access                      ANSI SCSI revision: 02
>   Vendor: SEAGATE   Model: SX423451W         Rev: 9E18
>   Type:   Direct-Access                      ANSI SCSI revision: 02
> scsi_eh_offline_sdevs: Device offlined - not ready or command retry failed after
>  error recovery: host 0 channel 0 id 1 lun 0
> scsi_eh_offline_sdevs: Device offlined - not ready or command retry failed after
>  error recovery: host 0 channel 0 id 1 lun 0
> scsi_eh_offline_sdevs: Device offlined - not ready or command retry failed after
>  error recovery: host 0 channel 0 id 2 lun 0
>   Vendor:           Model:                   Rev:
>   Type:   Direct-Access                      ANSI SCSI revision: 00
> scsi_eh_offline_sdevs: Device offlined - not ready or command retry failed after
>  error recovery: host 0 channel 0 id 2 lun 0
> scsi_eh_offline_sdevs: Device offlined - not ready or command retry failed after
>  error recovery: host 0 channel 0 id 2 lun 0
> scsi_eh_offline_sdevs: Device offlined - not ready or command retry failed after
>  error recovery: host 0 channel 0 id 3 lun 0
>   Vendor:           Model:                   Rev:
>   Type:   Direct-Access                      ANSI SCSI revision: 00
> .
> .
> .
> scsi_eh_offline_sdevs: Device offlined - not ready or command retry failed after
>  error recovery: host 0 channel 0 id 15 lun 0
>   Vendor:           Model:                   Rev:
>   Type:   Direct-Access                      ANSI SCSI revision: 00
> scsi_eh_offline_sdevs: Device offlined - not ready or command retry failed after
>  error recovery: host 0 channel 0 id 15 lun 0
> scsi_eh_offline_sdevs: Device offlined - not ready or command retry failed after
>  error recovery: host 0 channel 0 id 15 lun 0
> st: Version 20021015, fixed bufsize 32768, wrt 30720, s/g segs 256
> Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
> Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0
> Attached scsi disk sdc at scsi0, channel 0, id 2, lun 0
> Attached scsi disk sdd at scsi0, channel 0, id 3, lun 0
> Attached scsi disk sde at scsi0, channel 0, id 4, lun 0
> Attached scsi disk sdf at scsi0, channel 0, id 5, lun 0
> Attached scsi disk sdg at scsi0, channel 0, id 6, lun 0
> Attached scsi disk sdh at scsi0, channel 0, id 8, lun 0
> Attached scsi disk sdi at scsi0, channel 0, id 9, lun 0
> Attached scsi disk sdj at scsi0, channel 0, id 10, lun 0
> Attached scsi disk sdk at scsi0, channel 0, id 11, lun 0
> Attached scsi disk sdl at scsi0, channel 0, id 12, lun 0
> Attached scsi disk sdm at scsi0, channel 0, id 13, lun 0
> Attached scsi disk sdn at scsi0, channel 0, id 14, lun 0
> Attached scsi disk sdo at scsi0, channel 0, id 15, lun 0
> scsi_eh_offline_sdevs: Device offlined - not ready or command retry failed after
>  error recovery: host 0 channel 0 id 0 lun 0
> scsi_eh_offline_sdevs: Device offlined - not ready or command retry failed after
>  error recovery: host 0 channel 0 id 0 lun 0
> SCSI device sda: drive cache: write through
> scsi_eh_offline_sdevs: Device offlined - not ready or command retry failed after
>  error recovery: host 0 channel 0 id 0 lun 0
> sda : sector size 0 reported, assuming 512.
> SCSI device sda: 1 512-byte hdwr sectors (0 MB)
> .
> .
> .

> scsi_eh_offline_sdevs: Device offlined - not ready or command retry failed after
>  error recovery: host 0 channel 0 id 15 lun 0
> scsi_eh_offline_sdevs: Device offlined - not ready or command retry failed after
>  error recovery: host 0 channel 0 id 15 lun 0
> SCSI device sdo: drive cache: write through
> scsi_eh_offline_sdevs: Device offlined - not ready or command retry failed after
>  error recovery: host 0 channel 0 id 15 lun 0
> sdo : sector size 0 reported, assuming 512.
> SCSI device sdo: 1 512-byte hdwr sectors (0 MB)
> Initializing USB Mass Storage driver...

-andmike
--
Michael Anderson
andm...@us.ibm.com

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

2.5.43 scsi _eh_ buslogic

Post by Mike Anderso » Sun, 20 Oct 2002 22:10:06


Bill,
        In 2.5.44. I submitted a patch that changed the way scsi_host* is
        accessed. This patch also removed put_device which is replaced
        by device_unregister. That should fix one problem.

The other issue is that this driver like the BusLogic is using the old
error handler. Did it run on previous 2.5 versions?

If you go to 2.5.44 I believe you will also need the patch posted by
John Levon.


> > > scsi_eh_offline_sdevs: Device offlined - not ready or command retry failed after
> > >  error recovery: host 0 channel 0 id 3 lun 0
> > >   Vendor:           Model:                   Rev:
> > >   Type:   Direct-Access                      ANSI SCSI revision: 00

I am looking at this right now I believe when we offline a device we are
not setting the result if no action was performed on the command which
would happen if the device has no error handling.

Quote:> kernel BUG at drivers/base/core.c:269!
> invalid operand: 0000
> ncr53c8xx ide-scsi  
> CPU:    0
> EIP:    0060:[<c01e2d90>]    Not tainted
> EFLAGS: 00010202
> EIP is at put_device+0x50/0x80
> eax: 00000001   ebx: cf53b964   ecx: c03ee5d0   edx: cf53b9fc
> esi: cf948c98   edi: cf948c00   ebp: d08bf2e0   esp: cf60ff14
> ds: 0068   es: 0068   ss: 0068
> Process modprobe (pid: 332, threadinfo=cf60e000 task=cf7c7980)
> Stack: 00000000 cf53b800 c022b8c9 cf53b964 fffffff4 cfde6000 00000286 c014febe
>        cfde6009 00000008 ff883e60 fffffffe c03bda00 00000000 c0138b4f c0138b66
>        c12562a0 c12562a0 000001ff 00000000 c03be400 00000000 c0138ea2 c03bda00
> Call Trace:
>  [<c022b8c9>] scsi_unregister_host+0x259/0x540
>  [<c014febe>] getname+0x5e/0xa0
>  [<c0138b4f>] buffered_rmqueue+0x12f/0x150
>  [<c0138b66>] buffered_rmqueue+0x146/0x150
>  [<c0138ea2>] __alloc_pages+0xb2/0x290
>  [<d08b988a>] exit_this_scsi_driver+0xa/0xc [ncr53c8xx]
>  [<d08bf2e0>] driver_template+0x0/0x80 [ncr53c8xx]
>  [<c011c07e>] free_module+0x1e/0xf0
>  [<c011b454>] sys_delete_module+0x154/0x2e0
>  [<c010736f>] syscall_call+0x7/0xb

2.5.44 scsi_unregister_host update to device_unregister should fix this
problem.

-andmike
--
Michael Anderson

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

2.5.43 scsi _eh_ buslogic

Post by Doug Ledfor » Tue, 22 Oct 2002 18:30:12



> Andy,
>    From looking at the driver it looks like the locking had been
> update to 2.5, but that the driver error handling has not been updated.
> scsi_obsolete.c has not existed in the 2.5 view for a while.

Actually, I sent a patch to Linus for this driver that I think made it
into 2.5.44.  Andy, could you let me know if 2.5.44 works?  If not, then
I'll see what I can find.  Side note: Mike's right about the error
handling being horked, but that shouldn't really make any difference in
bootup since it shouldn't be needing error recovery.

--

         Red Hat, Inc.
         1801 Varsity Dr.
         Raleigh, NC 27606

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

1. Problems in the sk98lin driver (2.5.43)

I get the following when I attempt to build it as a module (gcc-3.0.4):

make -f arch/i386/lib/Makefile modules_install
if [ -r System.map ]; then /sbin/depmod -ae -F System.map -b /var/tmp/kernel-2.5.43-root -r 2.5.43-1sb; fi
depmod: *** Unresolved symbols in /var/tmp/kernel-2.5.43-root/lib/modules/2.5.43-1sb/kernel/drivers/net/sk98lin/sk98lin.o
depmod:         __udivdi3

This is coming from line 1481 in drivers/net/sk98lin/skgepnmi.c(SkPnmiInit):
                pAC->Pnmi.StartUpTime = SK_PNMI_HUNDREDS_SEC(SkOsGetTime(pAC));

SkOsGetTime is defined to return an unsigned 64 bit integer, and
SK_PNMI_HUNDREDS_SEC is a macro which does (arg * 100) / 1000.  The
1000 is coming from HZ and this macro does not get defined when HZ is
exactly a 100.

When scanning this file, I found another potential problem.  The Vpd()
function consumes 2851 bytes on the stack in auto variables.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

2. Flipbytes

3. i2c-elektor (2.5.43) non-fatal error: unresolved symbol cli, sti

4. Second Solaris partion on same hard disk?

5. 2.5.43-menuconfig

6. help: YDL-2.0 does not boot into installer

7. 2.5.43 : net/ipv4/ip_forward.c compile error

8. Results - Printer filter.

9. 2.5.43 oops in adaptec driver

10. LSM changes for 2.5.43

11. 2.5.43-mm1 Oops (nfs)

12. LTT for 2.5.43 3/10: Trace subsystem 2/2

13. Fix Linux 2.5.43 build of aic7xxx