All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Kashyap Desai <kashyap.desai@broadcom.com>
Cc: Jens Axboe <axboe@kernel.dk>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [REGRESSION] 4.9-rc4+ doesn't boot on my test box
Date: Tue, 08 Nov 2016 21:28:48 -0500	[thread overview]
Message-ID: <yq1h97hpesf.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <802c0d7b475ef619f6fb4aaeef7f138d@mail.gmail.com> (Kashyap Desai's message of "Wed, 9 Nov 2016 07:44:15 +0530")

>>>>> "Kashyap" == Kashyap Desai <kashyap.desai@broadcom.com> writes:

Kashyap,

>> Send a fix on top of current -git asap. The current tree is
>> completely broken for any megaraid user. -rc4 is no time to send in
>> untested patches, especially not something that claims to fix a 9
>> year old bug and is marked for stable as well.

*sigh* It's always the most innocuous patches that cause the worst
regressions :(

Kashyap> I will run some more test (using patch set only marked for
Kashyap> stable from last series) and submit fix ASAP.

I just tried a system with a megaraid card and things are broken in both
4.9/scsi-fixes and 4.10/scsi-queue unless the controller firmware has
the new sync flag set.

So, yes. Let's get a fix for this queued up ASAP.

Thanks!

-- 
Martin K. Petersen	Oracle Linux Engineering

      reply	other threads:[~2016-11-09  2:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-08 17:42 [REGRESSION] 4.9-rc4+ doesn't boot on my test box Jens Axboe
2016-11-08 23:15 ` Martin K. Petersen
2016-11-09  0:20   ` Kashyap Desai
2016-11-09  1:19     ` Jens Axboe
2016-11-09  2:14       ` Kashyap Desai
2016-11-09  2:28         ` Martin K. Petersen [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=yq1h97hpesf.fsf@sermon.lab.mkp.net \
    --to=martin.petersen@oracle.com \
    --cc=axboe@kernel.dk \
    --cc=kashyap.desai@broadcom.com \
    --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 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.