https://bugzilla.kernel.org/show_bug.cgi?id=60758 --- Comment #24 from Alan Bartlett <ajb@xxxxxxxxxx> --- (1) I have critically examined the configuration files used (from 3.10 to 3.10.10) paying particular attention to 3.10.4 v 3.10.5 There is nothing untoward in the configuration that can account for this problem. (2) I have performed a diff (diff -Npru) between the sources of 3.10.4 and 3.10.5 Subsequent checking the output for scsi references does not show anything obvious, to me. The output is attached, as the file diff-3.10.4-to-3.10.5.txt (3) Grep'ing the standard RHEL 6 /etc/rc.d/rc.sysinit file shows something interesting on line 165 but, once again, I do not think it is relevant. [quote] [Duo2 ~]$ grep -n -C 10 scsi /etc/rc.d/rc.sysinit 155-# Configure kernel parameters 156-update_boot_stage RCkernelparam 157-apply_sysctl 158- 159-# Set the hostname. 160-update_boot_stage RChostname 161-action $"Setting hostname ${HOSTNAME}: " hostname ${HOSTNAME} 162-[ -n "${NISDOMAIN}" ] && domainname ${NISDOMAIN} 163- 164-# Sync waiting for storage. 165:{ rmmod scsi_wait_scan ; modprobe scsi_wait_scan ; rmmod scsi_wait_scan ; } >/dev/null 2>&1 166- 167-# Device mapper & related initialization 168-if ! __fgrep "device-mapper" /proc/devices >/dev/null 2>&1 ; then 169- modprobe dm-mod >/dev/null 2>&1 170-fi 171- 172-if [ -f /etc/crypttab ]; then 173- init_crypto 0 174-fi 175- [/quote] -- You are receiving this mail because: You are the assignee for the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
