On 2017/01/17 14:15, Sreekanth Reddy wrote:
On Tue, Jan 17, 2017 at 4:13 AM, ojab <ojab@xxxxxxx> wrote:
On 2017/01/16 14:03, ojab wrote:
On 2017/01/16 13:31, Sreekanth Reddy wrote:
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.
According to the user guide (from
https://www.broadcom.com/products/storage/host-bus-adapters/sas-9217-8i#documentation)
my 9217-8i requires 1.8V UART which I don't have at hand, I'll try to do
something on the weekend.
Is anything needed except connecting UART to gather required info?
…actually I have compatible USB UART here. What should be done to get FW
log? I've tried to reboot with UART connected (9600N1) but got no output.
You have to use, 115200 instead of 9600 baud rate.
No output using 115200 8N1 either.
If I connect Bus Pirate to the pins and enable baud autodetect, I see
something like
>Calculated: 117647 bps
>Estimated: 115200 bps
on reboot and firmware/bios upgrade, but there is no text at all.
Right now I have IT firmware installed, `sas2flash -list` shows
> Adapter Selected is a LSI SAS: SAS2308_2(D1)
>
> Controller Number : 0
> Controller : SAS2308_2(D1)
> PCI Address : 00:02:00:00
> SAS Address : 500605b-0-05a6-c320
> NVDATA Version (Default) : 14.01.00.06
> NVDATA Version (Persistent) : 14.01.00.06
> Firmware Product ID : 0x2214 (IT)
> Firmware Version : 20.00.07.00
> NVDATA Vendor : LSI
> NVDATA Product ID : SAS9207-8i
> BIOS Version : 07.39.02.00
> UEFI BSD Version : 07.27.01.01
> FCODE Version : N/A
> Board Name : SAS9207-8i
> Board Assembly : N/A
> Board Tracer Number : N/A
//wbr ojab
Thanks,
Sreekanth
//wbr ojab
Anyway, right now various MPI2 HBAs doesn't work with ASPM enabled, so
can this patch be applied in the meantime while we're debugging the
issue further? Even if this issue can be properly fixed by FW update,
this workaround will be needed for HBAs with affected FW versions.
//wbr ojab
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
--
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
--
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
