> -----Original Message----- > From: Jean Delvare [mailto:jdelvare@xxxxxxx] > Sent: Tuesday, July 07, 2015 2:14 PM > To: Kashyap Desai > Cc: Bjorn Helgaas; Robin H. Johnson; Adam Radford; Neela Syam Kolli; linux- > scsi@xxxxxxxxxxxxxxx; arkadiusz.bubala@xxxxxxxxxx; Matthew Garrett; Sumit > Saxena; Uday Lingala; PDL,MEGARAIDLINUX; linux-pci@xxxxxxxxxxxxxxx; linux- > kernel@xxxxxxxxxxxxxxx; Myron Stowe > Subject: Re: megaraid_sas: "FW in FAULT state!!", how to get more debug > output? [BKO63661] > > Hi Kashyap, > > On Thu, 28 May 2015 19:05:35 +0530, Kashyap Desai wrote: > > Bjorn/Robin, > > > > Apologies for delay. Here is one quick suggestion as we have seen > > similar issue (not exactly similar, but high probably to have same > > issue) while controller is configured on VM as pass-through and VM reboot > abruptly. > > In that particular issue, driver interact with FW which may require > > chip reset to bring controller to operation state. > > > > Relevant patch was submitted for only Older controller as it was only > > seen for few MegaRaid controller. Below patch already try to do chip > > reset, but only for limited controllers...I have attached one more > > patch which does chip reset from driver load time for > > Thunderbolt/Invader/Fury etc. (In your case you have Thunderbolt > > controller, so attached patch is required.) > > > > http://www.spinics.net/lists/linux-scsi/msg67288.html > > > > Please post the result with attached patch. > > Good news! Customer tested your patch and said it fixed the problem :-) > > I am now in the process of backporting the patch to the SLES 11 SP3 kernel for > further testing. I'll let you know how it goes. Thank you very much for your > assistance. Thanks for confirmation. Whatever patch I submitted to you, we have added recently (as part of common interface approach to do chip reset at load time). We will be submitting that patch to mainline soon. ~ Kashyap > > -- > Jean Delvare > SUSE L3 Support -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
