Arthur Bergman wrote:
Ok,
Recompiled the kernel module and rebooted.
First thing that happened is this.
device-mapper: dm-round-robin version 0.2.1 loaded
scsi(0:0:0) UNDERRUN status detected 0x15-0x800.
scsi(0:0:0) UNDERRUN status detected 0x15-0x800.
scsi(0:0:0) UNDERRUN status detected 0x15-0x800.
scsi(0:0:1) UNDERRUN status detected 0x15-0x800.
scsi(0:0:1) UNDERRUN status detected 0x15-0x800.
scsi(0:0:1) UNDERRUN status detected 0x15-0x800.
scsi(0:1:0) UNDERRUN status detected 0x15-0x800.
scsi(0:1:0) UNDERRUN status detected 0x15-0x800.
scsi(0:1:0) UNDERRUN status detected 0x15-0x800.
scsi(0:1:1) UNDERRUN status detected 0x15-0x800.
scsi(0:1:1) UNDERRUN status detected 0x15-0x800.
scsi(0:1:1) UNDERRUN status detected 0x15-0x800.
scsi(0:2:0) UNDERRUN status detected 0x15-0x800.
scsi(0:2:0) UNDERRUN status detected 0x15-0x800.
scsi(0:2:0) UNDERRUN status detected 0x15-0x800.
scsi(0:2:1) UNDERRUN status detected 0x15-0x800.
scsi(0:2:1) UNDERRUN status detected 0x15-0x800.
scsi(0:2:1) UNDERRUN status detected 0x15-0x800.
scsi(0:3:0) UNDERRUN status detected 0x15-0x800.
scsi(0:3:0) UNDERRUN status detected 0x15-0x800.
scsi(0:3:0) UNDERRUN status detected 0x15-0x800.
scsi(0:3:1) UNDERRUN status detected 0x15-0x800.
scsi(0:3:1) UNDERRUN status detected 0x15-0x800.
scsi(0:3:1) UNDERRUN status detected 0x15-0x800.
scsi(1:0:0) UNDERRUN status detected 0x15-0x800.
scsi(1:0:0) UNDERRUN status detected 0x15-0x800.
scsi(1:0:0) UNDERRUN status detected 0x15-0x800.
scsi(1:0:1) UNDERRUN status detected 0x15-0x800.
scsi(1:0:1) UNDERRUN status detected 0x15-0x800.
scsi(1:0:1) UNDERRUN status detected 0x15-0x800.
scsi(1:1:0) UNDERRUN status detected 0x15-0x800.
scsi(1:1:0) UNDERRUN status detected 0x15-0x800.
scsi(1:1:0) UNDERRUN status detected 0x15-0x800.
scsi(1:1:1) UNDERRUN status detected 0x15-0x800.
scsi(1:1:1) UNDERRUN status detected 0x15-0x800.
scsi(1:1:1) UNDERRUN status detected 0x15-0x800.
scsi(1:2:0) UNDERRUN status detected 0x15-0x800.
scsi(1:2:0) UNDERRUN status detected 0x15-0x800.
scsi(1:2:0) UNDERRUN status detected 0x15-0x800.
scsi(1:2:1) UNDERRUN status detected 0x15-0x800.
scsi(1:2:1) UNDERRUN status detected 0x15-0x800.
scsi(1:2:1) UNDERRUN status detected 0x15-0x800.
scsi(1:3:0) UNDERRUN status detected 0x15-0x800.
scsi(1:3:0) UNDERRUN status detected 0x15-0x800.
scsi(1:3:0) UNDERRUN status detected 0x15-0x800.
scsi(1:3:1) UNDERRUN status detected 0x15-0x800.
scsi(1:3:1) UNDERRUN status detected 0x15-0x800.
scsi(1:3:1) UNDERRUN status detected 0x15-0x800.
This is the 8.00.00b21-k" driver that came with 2.6.10-rc1
Do I need to worry?
I don't think so, I have this at every boot.
(using debug enabled qla drivers)
This summer, I had lots of underrun & scsi errors, like you see.
It was rather variable (after 1 day ou 1 week), often when a bust of
transfer was happening.
After 1 month of debug with andrew vasquez (qlogic engineer),
and after having suspected raid firmware, qlogic driver, and even dm code,
it turns to be a card wich had problems with his laser AND an sfp wich
had problems
on 1 of my raid channel.
So beware of the physical part. Those opticals parts seems rather sensitive.
This was with multipath off.
Maybe you have problem on 1 of yours paths ??
--
Yann Dupont, Cri de l'université de Nantes
Tel: 02.51.12.53.91 - Fax: 02.51.12.58.60 - Yann.Dupont@xxxxxxxxxxxxxx
