linux-kernel - RE: megaraid_sas: "FW in FAULT state!!", how to get more debug output? [BKO63661]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1435584320.4646.53.camel@chaos.site>
Date:	Mon, 29 Jun 2015 15:25:20 +0200
From:	Jean Delvare <jdelvare@...e.de>
To:	Kashyap Desai <kashyap.desai@...gotech.com>
Cc:	Bjorn Helgaas <bhelgaas@...gle.com>,
	"Robin H. Johnson" <robbat2@...too.org>,
	Adam Radford <aradford@...il.com>,
	Neela Syam Kolli <megaraidlinux@....com>,
	linux-scsi@...r.kernel.org, arkadiusz.bubala@...n-e.com,
	Matthew Garrett <matthew.garrett@...ula.com>,
	Sumit Saxena <sumit.saxena@...gotech.com>,
	Uday Lingala <uday.lingala@...gotech.com>,
	"PDL,MEGARAIDLINUX" <megaraidlinux.pdl@...gotech.com>,
	linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
	Myron Stowe <myron.stowe@...hat.com>
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


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/