linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 111731] New: mpt2sas doesn't get built
Date: Tue, 02 Feb 2016 09:55:55 +0000	[thread overview]
Message-ID: <bug-111731-11613@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=111731

            Bug ID: 111731
           Summary: mpt2sas doesn't get built
           Product: SCSI Drivers
           Version: 2.5
    Kernel Version: 4.4.0
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Other
          Assignee: scsi_drivers-other@kernel-bugs.osdl.org
          Reporter: nux@li.nux.ro
        Regression: No

Hello,

It looks like 4.4.0 is not building mpt2sas modules any more.
We got bit by this while testing it (via ElRepo) on EL7.

Even though specified in the config, only mpt3sas is built.

While mpt3sas can indeed support the hardware in question (DELL/LSI H200 in my
case), dracut/mkinitrd fails to include it in the initrd, because it's looking
for mpt2sas which is missing from /lib/modules altogether.

`dracut --add-drivers` solves the problem, but this is not a graceful kernel
upgrade and ends up with unbootable OS.

More information about this issue here http://elrepo.org/bugs/view.php?id=628

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2016-02-02  9:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02  9:55 bugzilla-daemon [this message]
2016-02-12  5:04 ` [Bug 111731] mpt2sas doesn't get built bugzilla-daemon

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=bug-111731-11613@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).