From: Thomas Gleixner <tglx@linutronix.de>
To: Matthias Prager <linux@matthiasprager.de>
Cc: Sreekanth Reddy <sreekanth.reddy@broadcom.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
Jason Taylor <jason.taylor@simplivity.com>,
LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org
Subject: Re: [BUG] mpt2sas: driver init fails on kernel >=4.2 for 9211-8i IT
Date: Thu, 24 Mar 2016 07:06:12 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.11.1603240701270.3978@nanos> (raw)
In-Reply-To: <56F34BB5.3090007@matthiasprager.de>
On Thu, 24 Mar 2016, Matthias Prager wrote:
> The timeout happens reliably after two warm boots with a 'bad' kernel
> after coming from a 'good' kernel, and also after one cold boot with a
> 'bad' kernel (meaning cold booting a 'bad' kernel leads directly to the
> timeout and warm booting needs a second run to produce the timeout). I
> haven't tested bare metal yet - I can do that tomorrow if necessary.
That's on VMWare, right? Jason has seen the same issue:
http://marc.info/?l=linux-kernel&m=145280623530135&w=2
http://marc.info/?l=linux-kernel&m=145523785705624&w=2
"Works fine on real hardware and KVM. Filed an issue with VMware and the fix
is in the works."
Jason, what's the state of this?
Thanks,
tglx
next prev parent reply other threads:[~2016-03-24 6:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-20 20:14 [BUG] mpt2sas: driver init fails on kernel >=4.2 for 9211-8i IT Matthias Prager
2016-03-21 4:53 ` Sreekanth Reddy
2016-03-21 9:18 ` Matthias Prager
2016-03-21 13:59 ` Sreekanth Reddy
2016-03-21 15:52 ` Matthias Prager
2016-03-21 16:30 ` Matthias Prager
2016-03-22 10:52 ` Sreekanth Reddy
2016-03-22 21:02 ` Matthias Prager
2016-03-24 2:06 ` Matthias Prager
2016-03-24 6:06 ` Thomas Gleixner [this message]
2016-03-24 9:08 ` Matthias Prager
2016-03-24 11:02 ` Jason Taylor
2016-06-20 11:13 ` Matthias Prager
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=alpine.DEB.2.11.1603240701270.3978@nanos \
--to=tglx@linutronix.de \
--cc=jason.taylor@simplivity.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux@matthiasprager.de \
--cc=sreekanth.reddy@broadcom.com \
--cc=x86@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