This message indicates the kernel gave up waiting on the 1078 to set the 'F' bit in the VPD capabilities structure. Setting this flag is the hardware's method to indicate to software that data is ready in the VPD data register. The PERC6/i and PERC6/E appear to have some bad behavior in this area. This problem either resides in the controller firmware or hardware, and only affects a very specific sequence of PCIe configuration space operations. This does not indicate a more broad issue with normal controller access. The megaraid_sas driver is not involved in this communication path. In fact, this is a PCI layer issue, not a SCSI problem. It looks like more recent kernels starting querying this information, which is why the message starting appearing. -Jim -----Original Message----- From: linux-scsi-owner@xxxxxxxxxxxxxxx [mailto:linux-scsi-owner@xxxxxxxxxxxxxxx] On Behalf Of DemonCcC Sent: Monday, June 27, 2011 12:48 PM To: linux-scsi@xxxxxxxxxxxxxxx Subject: megaraid_sas driver issues Hi all, I have installed Debian on PowerEdge R710 Dell system. I upgrade the storage controller (LSI MegaRAID SAS 1078) to the last firmware version that Dell provides (6.3.0-0001). The server has two storage controllers, one internal (PERC 6/i Integrated) and other external ( PERC 6/E Adapter). With the kernels 2.6.35, 2.6.38 and 2.6.39 the kernel returns these messages: Jun 24 21:41:44 mysql01 kernel: [ 29.428857] megaraid_sas 0000:03:00.0: vpd r/w failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update. Jun 24 21:41:45 mysql01 kernel: [ 29.817765] megaraid_sas 0000:0a:00.0: vpd r/w failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update. The kernel 2.6.32 doesn't return any error. I tested with the pci=nocrs, because I have read that the default is pci=use_crs in the newest kernel and it could cause a timeout when the kernel tries to read the vpd, but the kernel still logging these messages. Also I compiled the latest megaraid_sas driver (00.00.05.38-rc1) but these messages keep appearing. Do you know what could be the issue? Why the newest kernels log these messages? Regards. Claudio César Sánchez Tejeda -- 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 -- 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
