Re: 2.0.37pre9 instability

Gerard Roudier (groudier@club-internet.fr)
Thu, 1 Apr 1999 21:53:12 +0200 (MET DST)


On Thu, 1 Apr 1999, Hans-Joachim Baader wrote:

> Hi,
>
> after ony 2 days uptime, my server fell over with SCSI timeout.
> I had to reset it. Unfortunately the messages didn't make it into the log.
> The error was probably on one of these devices:
>
> Host: scsi0 Channel: 00 Id: 01 Lun: 00
> Vendor: HP Model: C2490A-300 Rev: 4140
> Type: Direct-Access ANSI SCSI revision: 02
> Host: scsi0 Channel: 00 Id: 02 Lun: 00
> Vendor: IBM Model: DORS-32160 Rev: WA6A
> Type: Direct-Access ANSI SCSI revision: 02
>
> I think we had a similar problem in pre37-4 when the Symbios
> SCSI code was updated, but I don't remember exactly.

It is the first problem about pre37 failure I read and that may involve
update of the generic Symbios driver. Sorry if I missed a previous report
from you. If you could give a try to latest version and see if it makes
differences, this will help. This patch is against 2.0.37-pre8 and is
available in 2 different places at tux site. This one below is one of
them. I haven't time to check if it applies to pre9, but if it doesn't it
should be trivialy fixable by hand.

ftp://ftp.tux.org/pub/roudier/drivers/linux/sym53c8xx/patch-53c8xx-s01-d00-2.0.37-pre8.gz

(This patch contains both ncr53c8xx updates and sym53c8xx addition)

If it fixes something for your system using the ncr53c8xx driver and not
the sym one, I will send Alan the part of this patch that applies to the
generic ncr53c8xxx. Let me know as quickly as possible.

Regards,
Gérard.

> My config:
> CONFIG_EXPERIMENTAL=y
> CONFIG_MODULES=y
> CONFIG_MODVERSIONS=y
> CONFIG_KERNELD=y
> CONFIG_MEM_STD=y
> CONFIG_MAX_MEMSIZE=1024
> CONFIG_NET=y
> CONFIG_PCI=y
> CONFIG_PCI_OPTIMIZE=y
> CONFIG_SYSVIPC=y
> CONFIG_BINFMT_AOUT=m
> CONFIG_BINFMT_ELF=y
> CONFIG_BINFMT_JAVA=m
> CONFIG_KERNEL_ELF=y
> CONFIG_M486=y
> CONFIG_BLK_DEV_FD=m
> CONFIG_BLK_DEV_IDE=y
> CONFIG_BLK_DEV_IDECD=y
> CONFIG_BLK_DEV_CMD640=y
> CONFIG_BLK_DEV_RZ1000=y
> CONFIG_BLK_DEV_LOOP=m
> CONFIG_BLK_DEV_MD=y
> CONFIG_MD_LINEAR=m
> CONFIG_MD_STRIPED=m
> CONFIG_MD_MIRRORING=m
> CONFIG_MD_RAID5=m
> CONFIG_BLK_DEV_RAM=y
> CONFIG_BLK_DEV_INITRD=y
> CONFIG_FIREWALL=y
> CONFIG_NET_ALIAS=y
> CONFIG_INET=y
> CONFIG_IP_FORWARD=y
> CONFIG_SYN_COOKIES=y
> CONFIG_IP_FIREWALL=y
> CONFIG_IP_FIREWALL_VERBOSE=y
> CONFIG_IP_MASQUERADE=y
> CONFIG_IP_MASQUERADE_IPSEC=y
> CONFIG_IP_MASQUERADE_IPSEC_EXPIRE=30
> CONFIG_IP_MASQUERADE_ICMP=y
> CONFIG_IP_ACCT=y
> CONFIG_NET_IPIP=m
> CONFIG_IP_ALIAS=m
> CONFIG_INET_RARP=m
> CONFIG_IP_NOSR=y
> CONFIG_SKB_LARGE=y
> CONFIG_IPX=m
> CONFIG_SCSI=y
> CONFIG_BLK_DEV_SD=y
> CONFIG_CHR_DEV_ST=m
> CONFIG_BLK_DEV_SR=m
> CONFIG_CHR_DEV_SG=m
> CONFIG_SCSI_CONSTANTS=y
> CONFIG_SCSI_AHA1542=m
> CONFIG_SCSI_NCR53C8XX=y
> CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS=8
> CONFIG_SCSI_NCR53C8XX_MAX_TAGS=32
> CONFIG_SCSI_NCR53C8XX_SYNC=10
> CONFIG_SCSI_NCR53C8XX_SYMBIOS_COMPAT=y
> CONFIG_SCSI_PPA=m
> CONFIG_SCSI_PPA_HAVE_PEDANTIC=y
> CONFIG_NETDEVICES=y
> CONFIG_PLIP=m
> CONFIG_PPP=m
> CONFIG_SLIP=m
> CONFIG_SLIP_COMPRESSED=y
> CONFIG_SLIP_SMART=y
> CONFIG_SLIP_MODE_SLIP6=y
> CONFIG_NET_ETHERNET=y
> CONFIG_NET_VENDOR_3COM=y
> CONFIG_VORTEX=m
> CONFIG_NET_PCI=y
> CONFIG_VIA_RHINE=m
> CONFIG_NET_ISA=y
> CONFIG_NE2000=m
> CONFIG_ISDN=m
> CONFIG_ISDN_PPP=y
> CONFIG_ISDN_PPP_VJ=y
> CONFIG_ISDN_MPP=y
> CONFIG_ISDN_AUDIO=y
> CONFIG_ISDN_DRV_LOOP=m
> CONFIG_ISDN_DRV_HISAX=m
> CONFIG_HISAX_EURO=y
> CONFIG_DE_AOC=y
> CONFIG_HISAX_16_3=y
> CONFIG_CD_NO_IDESCSI=y
> CONFIG_MCD=m
> CONFIG_MCDX=m
> CONFIG_QUOTA=y
> CONFIG_MINIX_FS=y
> CONFIG_EXT2_FS=y
> CONFIG_NLS=m
> CONFIG_ISO9660_FS=m
> CONFIG_FAT_FS=m
> CONFIG_MSDOS_FS=m
> CONFIG_UMSDOS_FS=m
> CONFIG_VFAT_FS=m
> CONFIG_NLS_CODEPAGE_437=m
> CONFIG_NLS_CODEPAGE_850=m
> CONFIG_NLS_ISO8859_1=m
> CONFIG_NLS_ISO8859_15=m
> CONFIG_PROC_FS=y
> CONFIG_NFS_FS=y
> CONFIG_SMB_FS=m
> CONFIG_NCP_FS=m
> CONFIG_NCPFS_NFS_NS=y
> CONFIG_NCPFS_OS2_NS=y
> CONFIG_NCPFS_MOUNT_SUBDIR=y
> CONFIG_AUTOFS_FS=m
> CONFIG_UFS_FS=m
> CONFIG_BSD_DISKLABEL=y
> CONFIG_SMD_DISKLABEL=y
> CONFIG_SERIAL=y
> CONFIG_STALDRV=y
> CONFIG_PRINTER=m
> CONFIG_MOUSE=y
> CONFIG_PSMOUSE=m
> CONFIG_FTAPE=m
> CONFIG_WATCHDOG=y
> CONFIG_SOFT_WATCHDOG=m
> CONFIG_RTC=y
> CONFIG_SOUND=m
>
> NCR driver info:
>
> Chip NCR53C810, device id 0x1, revision id 0x2
> IO port address 0xe800, IRQ number 15
> Using memory mapped IO at virtual address 0x4805000
> Synchronous period factor 25, max commands per lun 32
>
> Complete device list:
>
> Host: scsi0 Channel: 00 Id: 00 Lun: 00
> Vendor: TOSHIBA Model: CD-ROM XM-3601TA Rev: 0265
> Type: CD-ROM ANSI SCSI revision: 02
> Host: scsi0 Channel: 00 Id: 01 Lun: 00
> Vendor: HP Model: C2490A-300 Rev: 4140
> Type: Direct-Access ANSI SCSI revision: 02
> Host: scsi0 Channel: 00 Id: 02 Lun: 00
> Vendor: IBM Model: DORS-32160 Rev: WA6A
> Type: Direct-Access ANSI SCSI revision: 02
> Host: scsi0 Channel: 00 Id: 04 Lun: 00
> Vendor: FUJITSU Model: M1603S-512 Rev: 6C01
> Type: Direct-Access ANSI SCSI revision: 02
>
> I also suspect memory leaks but this is hard to test. It needs a lot
> of time to show up, and if the SCSI subsystem crashes before that,
> there's no way in finding it...
>
> hjb
> --
> "Every use of Linux is a proper use of Linux." -- John "Maddog" Hall
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
> Please read the FAQ at http://www.tux.org/lkml/

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