From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Luck, Tony" <tony.luck@intel.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: "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 10:56:57 -0800 [thread overview]
Message-ID: <1452279417.2297.5.camel@HansenPartnership.com> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F39FA7873@ORSMSX114.amr.corp.intel.com>
On Fri, 2016-01-08 at 18:42 +0000, Luck, Tony wrote:
> > We're not quite out of the woods yet: dracut should have seen this
> > automatically because of the module alias bindings. Is your system
> > somehow unusual and you don't expect the initrd automatic module
> > selection to work? If not, could you help us debug why it didn't?
>
> I saw the same problem building a 4.4-rc* kernel on a RHEL7.2
> and SLES12-SP1 system.
>
> My build process is in both cases is:
> $ tar xf linux-...
> $ cd linux...
> $ cp /boot/config-xyzzy .
> $ yes "" | make oldconfig
> $ make -j 100
> $ su
> # make -j 100 modules_install && make install
>
> What sort of features of a system might be considered "unusual"?
> This looks a very simple system ... just one disk controller with two
> drive bays occupied.
>
> Let me know if you'd like run any topology reporting commands.
No, the problem will lie in the initrd building part. I know that with
debian mkinitramfs takes the -v option which will tell you what modules
it's selecting and why, but I'm not very familiar with enterprise
distributions; chances are whatever command you use to build the initrd
does take a -v.
James
prev parent reply other threads:[~2016-01-08 18:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 22:55 System "hangs" on kernels > v4.4-rc1 - mpt2sas problem? Luck, Tony
2016-01-08 0:48 ` Tony Luck
2016-01-08 2:34 ` Martin K. Petersen
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: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
2016-01-08 17:28 ` Martin K. Petersen
2016-01-08 17:32 ` Luck, Tony
2016-01-08 17:41 ` Martin K. Petersen
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: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 [this message]
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=1452279417.2297.5.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--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 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.