mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: "Luck\, Tony" <tony.luck@intel.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-scsi\@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: System "hangs" on kernels > v4.4-rc1 - mpt2sas problem?
Date: Fri, 08 Jan 2016 12:28:03 -0500	[thread overview]
Message-ID: <yq1r3hsf0bg.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F39FA727F@ORSMSX114.amr.corp.intel.com> (Tony Luck's message of "Fri, 8 Jan 2016 16:55:52 +0000")

>>>>> "Luck," == Luck, Tony <tony.luck@intel.com> writes:

Luck,> I also see that mpt2 and mpt3 were merged, with mpt2 option still
Luck,> there as a legacy driver.  Which should I be using?

If you previously had MPT2SAS enabled in your .config then the new
kernel should automatically pull MPT3SAS in. You still need to verify in
your initrd that the mpt3sas.ko module gets included, though. How that
works depends on your distro.

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2016-01-08 17:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-07 22:55 Luck, Tony
2016-01-08  0:48 ` Tony Luck
2016-01-08  2:34 ` Martin K. Petersen
2016-01-08  5:01   ` Luck, Tony
2016-01-08 17:25     ` Martin K. Petersen
2016-01-08 17:29       ` Luck, Tony
2016-01-08 16:55   ` Luck, Tony
2016-01-08 17:28     ` Martin K. Petersen [this message]
2016-01-08 17:32       ` Luck, Tony
2016-01-08 17:41         ` Martin K. Petersen
2016-01-08 18:23           ` Luck, Tony
2016-01-08 18:32             ` James Bottomley
2016-01-08 18:40               ` Martin K. Petersen
2016-01-08 18:55                 ` Luck, Tony
2016-01-08 18:42               ` Luck, Tony
2016-01-08 18:56                 ` James Bottomley

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=yq1r3hsf0bg.fsf@sermon.lab.mkp.net \
    --to=martin.petersen@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=tony.luck@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®