On Mon, Jan 16, 2017 at 6:15 PM, ojab <ojab@xxxxxxx> wrote: > On 2017/01/16 12:36, Sreekanth Reddy wrote: >> >> Ojab, >> >> I am checking internally with our FW team and Architect to known >> whether they aware/observed any issues similar to this (since this >> issue is nothing to do with driver). >> >> Meanwhile is it possible to provide us the PCI config space and FW >> logs when issue occurs? > > > AFAIU FW log is enabled when `logging_level=0x3f8` is passed to the module, > right? This is a driver logging_level. Firmware logs can be collected using UART logs. > Where can I find info about PCI config space? You can get PCI config space info from lspci command. > > //wbr ojab >> >> >> Thanks, >> Sreekanth >> >> On Mon, Jan 16, 2017 at 5:37 PM, ojab <ojab@xxxxxxx> wrote: >>> >>> On 2017/01/06 15:48, Sreekanth Reddy wrote: >>>> >>>> >>>> On Fri, Jan 6, 2017 at 7:24 AM, Martin K. Petersen >>>> <martin.petersen@xxxxxxxxxx> wrote: >>>> >>>> Matin, We need some time to review this patch. I will provide my >>>> review comments by end of next week. >>>> >>> ping? >>> >>> //wbr ojab >>>> >>>> >>>> Thanks, >>>> Sreekanth >>> >>> >>> >> -- >> 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
