From: Kashyap Desai <kashyap.desai@avagotech.com>
To: Jean Delvare <jdelvare@suse.de>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"Robin H. Johnson" <robbat2@gentoo.org>,
Adam Radford <aradford@gmail.com>,
Neela Syam Kolli <megaraidlinux@lsi.com>,
linux-scsi@vger.kernel.org, arkadiusz.bubala@open-e.com,
Matthew Garrett <matthew.garrett@nebula.com>,
Sumit Saxena <sumit.saxena@avagotech.com>,
Uday Lingala <uday.lingala@avagotech.com>,
"PDL,MEGARAIDLINUX" <megaraidlinux.pdl@avagotech.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Myron Stowe <myron.stowe@redhat.com>
Subject: RE: megaraid_sas: "FW in FAULT state!!", how to get more debug output? [BKO63661]
Date: Tue, 30 Jun 2015 16:03:46 +0530 [thread overview]
Message-ID: <12176d8f15f49359898726ccede592bd@mail.gmail.com> (raw)
In-Reply-To: <1435584320.4646.53.camel@chaos.site>
Jean,
Patch is available at below repo -
git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git - b for-next
Commit id -
6431f5d7c6025f8b007af06ea090de308f7e6881
If you share megaraid_sas driver code of your tree, I can provide patch for
you.
` Kashyap
> -----Original Message-----
> From: Jean Delvare [mailto:jdelvare@suse.de]
> Sent: Monday, June 29, 2015 6:55 PM
> To: Kashyap Desai
> Cc: Bjorn Helgaas; Robin H. Johnson; Adam Radford; Neela Syam Kolli;
> linux-
> scsi@vger.kernel.org; arkadiusz.bubala@open-e.com; Matthew Garrett; Sumit
> Saxena; Uday Lingala; PDL,MEGARAIDLINUX; linux-pci@vger.kernel.org; linux-
> kernel@vger.kernel.org; Myron Stowe
> Subject: RE: megaraid_sas: "FW in FAULT state!!", how to get more debug
> output? [BKO63661]
>
> Hi Kashyap,
>
> Thanks for the patch. May I ask what tree it was based on? Linus'
> latest? I am trying to apply it to the SLES 11 SP3 and SLES 12 kernel
> trees (based
> on kernel v3.0 + a bunch of backports and v3.12
> respectively) but your patch fails to apply in both cases. I'll try harder
> but I don't
> know anything about the megaraid_sas code so I really don't know where I'm
> going.
>
> Does your patch depend on any other that may not be present in the SLES
> 11 SP3 and SLES 12 kernels?
>
> Thanks,
> Jean
>
> Le Thursday 28 May 2015 à 19:05 +0530, Kashyap Desai a écrit :
> > 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.
> >
> > Thanks, Kashyap
>
next prev parent reply other threads:[~2015-06-30 10:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-12 11:56 megaraid_sas: "FW in FAULT state!!", how to get more debug output? [BKO63661] Robin H. Johnson
2014-07-12 17:29 ` Bjorn Helgaas
2014-07-13 1:35 ` Robin H. Johnson
2015-04-29 17:28 ` Bjorn Helgaas
2015-05-28 12:24 ` Bjorn Helgaas
2015-05-28 13:35 ` Kashyap Desai
2015-06-29 13:25 ` Jean Delvare
2015-06-29 13:25 ` Jean Delvare
2015-06-30 10:33 ` Kashyap Desai [this message]
2015-07-01 9:20 ` Jean Delvare
2015-07-07 8:44 ` Jean Delvare
2015-07-07 9:18 ` Kashyap Desai
2015-07-10 14:05 ` Jean Delvare
2015-07-10 14:16 ` Kashyap Desai
2015-07-15 7:21 ` Jean Delvare
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=12176d8f15f49359898726ccede592bd@mail.gmail.com \
--to=kashyap.desai@avagotech.com \
--cc=aradford@gmail.com \
--cc=arkadiusz.bubala@open-e.com \
--cc=bhelgaas@google.com \
--cc=jdelvare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew.garrett@nebula.com \
--cc=megaraidlinux.pdl@avagotech.com \
--cc=megaraidlinux@lsi.com \
--cc=myron.stowe@redhat.com \
--cc=robbat2@gentoo.org \
--cc=sumit.saxena@avagotech.com \
--cc=uday.lingala@avagotech.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.