Bug#498667: linux-image-2.6.18-6-686: megaraid abort errors in system log (Intel SRCS28X RAID Controller)
Package: linux-image-2.6.18-6-686
Version: 2.6.18.dfsg.1-18etch6
Severity: important
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-686
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Versions of packages linux-image-2.6.18-6-686 depends on:
ii coreutils 5.97-5.3 The GNU core utilities
ii debconf [debconf-2.0] 1.5.11etch1 Debian configuration management sy
ii initramfs-tools [linux-initr 0.85h tools for generating an initramfs
ii module-init-tools 3.3-pre4-2 tools for managing Linux kernel mo
Versions of packages linux-image-2.6.18-6-686 recommends:
ii libc6-i686 2.3.6.ds1-13etch5 GNU C Library: Shared libraries [i
-- debconf information:
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.18-6-686/preinst/elilo-initrd-2.6.18-6-686: true
* linux-image-2.6.18-6-686/preinst/already-running-this-2.6.18-6-686:
linux-image-2.6.18-6-686/postinst/depmod-error-2.6.18-6-686: false
linux-image-2.6.18-6-686/preinst/initrd-2.6.18-6-686:
linux-image-2.6.18-6-686/postinst/old-initrd-link-2.6.18-6-686: true
linux-image-2.6.18-6-686/preinst/bootloader-initrd-2.6.18-6-686: true
linux-image-2.6.18-6-686/preinst/abort-install-2.6.18-6-686:
linux-image-2.6.18-6-686/preinst/lilo-has-ramdisk:
linux-image-2.6.18-6-686/preinst/overwriting-modules-2.6.18-6-686: true
linux-image-2.6.18-6-686/postinst/bootloader-error-2.6.18-6-686:
linux-image-2.6.18-6-686/prerm/would-invalidate-boot-loader-2.6.18-6-686: true
linux-image-2.6.18-6-686/postinst/bootloader-test-error-2.6.18-6-686:
linux-image-2.6.18-6-686/postinst/create-kimage-link-2.6.18-6-686: true
linux-image-2.6.18-6-686/postinst/depmod-error-initrd-2.6.18-6-686: false
linux-image-2.6.18-6-686/preinst/lilo-initrd-2.6.18-6-686: true
linux-image-2.6.18-6-686/postinst/old-dir-initrd-link-2.6.18-6-686: true
linux-image-2.6.18-6-686/preinst/failed-to-move-modules-2.6.18-6-686:
linux-image-2.6.18-6-686/preinst/abort-overwrite-2.6.18-6-686:
linux-image-2.6.18-6-686/prerm/removing-running-kernel-2.6.18-6-686: true
linux-image-2.6.18-6-686/postinst/old-system-map-link-2.6.18-6-686: true
linux-image-2.6.18-6-686/postinst/kimage-is-a-directory:
I am seeing a large number of instances of this error in the system log:
Sep 11 16:00:05 localhost kernel: megaraid: aborting-10564708 cmd=2a <c=1 t=0 l=0>
Sep 11 16:00:05 localhost kernel: megaraid abort: scsi cmd:10564708, do now own
Sep 11 16:00:05 localhost kernel: megaraid: aborting-10564709 cmd=2a <c=1 t=0 l=0>
Sep 11 16:00:05 localhost kernel: megaraid abort: scsi cmd:10564709, do now own
Sep 11 16:00:05 localhost kernel: megaraid: aborting-10564710 cmd=2a <c=1 t=0 l=0>
Sep 11 16:00:05 localhost kernel: megaraid abort: scsi cmd:10564710, do now own
Sep 11 16:00:05 localhost kernel: megaraid: aborting-10564711 cmd=2a <c=1 t=0 l=0>
Sep 11 16:00:05 localhost kernel: megaraid abort: scsi cmd:10564711, do now own
Sep 11 16:00:05 localhost kernel: megaraid: aborting-10564712 cmd=2a <c=1 t=0 l=0>
Sep 11 16:00:05 localhost kernel: megaraid abort: scsi cmd:10564712, do now own
Sep 11 16:00:05 localhost kernel: megaraid: aborting-10564713 cmd=2a <c=1 t=0 l=0>
Sep 11 16:00:05 localhost kernel: megaraid abort: 10564713:0[255:0], fw owner
Sep 11 16:00:05 localhost kernel: megaraid: aborting-10564714 cmd=2a <c=1 t=0 l=0>
Sep 11 16:00:05 localhost kernel: megaraid abort: 10564714:6[255:0], fw owner
Sep 11 16:00:05 localhost kernel: megaraid: aborting-10564715 cmd=2a <c=1 t=0 l=0>
Sep 11 16:00:05 localhost kernel: megaraid abort: 10564715:71[255:0], fw owner
Sep 11 16:00:05 localhost kernel: megaraid: aborting-10564716 cmd=2a <c=1 t=1 l=0>
Sep 11 16:00:05 localhost kernel: megaraid abort: scsi cmd:10564716, do now own
Sep 11 16:00:05 localhost kernel: megaraid: 3 outstanding commands. Max wait 300 sec
Sep 11 16:00:05 localhost kernel: megaraid mbox: Wait for 3 commands to complete:300
Sep 11 16:00:05 localhost kernel: megaraid mbox: reset sequence completed sucessfully
On at least one recent occasion, users have lost connections (SMB) to this server which appear to have been caused by these errors.
Reply to: