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] [day] [month] [year] [list]

Message-ID: <1436944915.4661.5.camel@chaos.site>
Date:	Wed, 15 Jul 2015 09:21:55 +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]

Le Friday 10 July 2015 à 19:46 +0530, Kashyap Desai a écrit :
> >
> > I am about to commit the patch that was successfully tested by the
> > customer on
> > SLES 12, but I'm a bit confused. The upstream patch you referred to is:
> >
> > https://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-
> > next&id=6431f5d7c6025f8b007af06ea090de308f7e6881
> > [SCSI] megaraid_sas: megaraid_sas driver init fails in kdump kernel
> >
> > But the patch I used is the one you sent by e-mail on May 28th. It is
> > completely
> > different!
> >
> > So what am I supposed to do? Use the patch you sent (and that was tested
> > by the customer) for SLES 11 SP3 and SLES 12? Or was it just for testing
> > and the proper way of fixing the problem would be to backport the
>>upstream commit?
> 
> You can use that patch as valid candidate for upstream submission. Some of
> the MR maintainer (Sumit Saxena) will send that patch. We are just
> organizing other patch series.
> Since SLES already ported patch without commit id, we are fine. I am just
> giving reference that patch which send via email will be send to upstream
> very soon along with other patch set.

OK, thanks for the clarification. The patched SLES 11 SP3 kernel is
currently under testing by the customer, apparently it doesn't work but
I don't have all the details yet. Maybe some more patches need to be
backported because that kernel is older.

-- 
Jean Delvare
SUSE L3 Support

--
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/