From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"abdhalee@linux.vnet.ibm.com" <abdhalee@linux.vnet.ibm.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"hch@lst.de" <hch@lst.de>,
"brking@linux.vnet.ibm.com" <brking@linux.vnet.ibm.com>,
"sfr@canb.auug.org.au" <sfr@canb.auug.org.au>,
"sachinp@linux.vnet.ibm.com" <sachinp@linux.vnet.ibm.com>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"hare@suse.com" <hare@suse.com>,
"mpe@ellerman.id.au" <mpe@ellerman.id.au>
Subject: Re: [BUG][bisected 270065e] linux-next fails to boot on powerpc
Date: Wed, 16 Aug 2017 17:21:14 +0000 [thread overview]
Message-ID: <1502904072.2421.3.camel@wdc.com> (raw)
In-Reply-To: <1502902815.3305.22.camel@abdul.in.ibm.com>
On Wed, 2017-08-16 at 22:30 +0530, Abdul Haleem wrote:
> As of next-20170809, linux-next on powerpc boot hung with below trace
> message.
>
> [ ... ]
>
> A bisection resulted in first bad commit (270065e92 - scsi: scsi-mq:
> Always unprepare ...) in the merge branch 'scsi/for-next'
>
> System booted fine when the below commit is reverted:
>
> commit 270065e92c317845d69095ec8e3d18616b5b39d5
> Author: Bart Van Assche <bart.vanassche@wdc.com>
> Date: Thu Aug 3 14:40:14 2017 -0700
>
> scsi: scsi-mq: Always unprepare before requeuing a request
Hello Brian and Michael,
Do you agree that this probably indicates a bug in the PowerPC block driver
that is used to access the boot disk? Anyway, since a solution is not yet
available, I will submit a revert for this patch.
Bart.
WARNING: multiple messages have this Message-ID (diff)
From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"abdhalee@linux.vnet.ibm.com" <abdhalee@linux.vnet.ibm.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"hch@lst.de" <hch@lst.de>,
"brking@linux.vnet.ibm.com" <brking@linux.vnet.ibm.com>,
"sfr@canb.auug.org.au" <sfr@canb.auug.org.au>,
"sachinp@linux.vnet.ibm.com" <sachinp@linux.vnet.ibm.com>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"hare@suse.com" <hare@suse.com>,
"mpe@ellerman.id.au" <mpe@ellerman.id.au>
Subject: Re: [BUG][bisected 270065e] linux-next fails to boot on powerpc
Date: Wed, 16 Aug 2017 17:21:14 +0000 [thread overview]
Message-ID: <1502904072.2421.3.camel@wdc.com> (raw)
In-Reply-To: <1502902815.3305.22.camel@abdul.in.ibm.com>
T24gV2VkLCAyMDE3LTA4LTE2IGF0IDIyOjMwICswNTMwLCBBYmR1bCBIYWxlZW0gd3JvdGU6DQo+
IEFzIG9mIG5leHQtMjAxNzA4MDksIGxpbnV4LW5leHQgb24gcG93ZXJwYyBib290IGh1bmcgd2l0
aCBiZWxvdyB0cmFjZQ0KPiBtZXNzYWdlLg0KPiANCj4gWyAuLi4gXQ0KPiANCj4gQSBiaXNlY3Rp
b24gcmVzdWx0ZWQgaW4gZmlyc3QgYmFkIGNvbW1pdCAoMjcwMDY1ZTkyIC0gc2NzaTogc2NzaS1t
cToNCj4gQWx3YXlzIHVucHJlcGFyZSAuLi4pIGluIHRoZSBtZXJnZSBicmFuY2ggJ3Njc2kvZm9y
LW5leHQnDQo+IA0KPiBTeXN0ZW0gYm9vdGVkIGZpbmUgd2hlbiB0aGUgYmVsb3cgY29tbWl0IGlz
IHJldmVydGVkOiANCj4gDQo+IGNvbW1pdCAyNzAwNjVlOTJjMzE3ODQ1ZDY5MDk1ZWM4ZTNkMTg2
MTZiNWIzOWQ1DQo+IEF1dGhvcjogQmFydCBWYW4gQXNzY2hlIDxiYXJ0LnZhbmFzc2NoZUB3ZGMu
Y29tPg0KPiBEYXRlOiAgIFRodSBBdWcgMyAxNDo0MDoxNCAyMDE3IC0wNzAwDQo+IA0KPiAgICAg
c2NzaTogc2NzaS1tcTogQWx3YXlzIHVucHJlcGFyZSBiZWZvcmUgcmVxdWV1aW5nIGEgcmVxdWVz
dA0KDQpIZWxsbyBCcmlhbiBhbmQgTWljaGFlbCwNCg0KRG8geW91IGFncmVlIHRoYXQgdGhpcyBw
cm9iYWJseSBpbmRpY2F0ZXMgYSBidWcgaW4gdGhlIFBvd2VyUEMgYmxvY2sgZHJpdmVyDQp0aGF0
IGlzIHVzZWQgdG8gYWNjZXNzIHRoZSBib290IGRpc2s/IEFueXdheSwgc2luY2UgYSBzb2x1dGlv
biBpcyBub3QgeWV0DQphdmFpbGFibGUsIEkgd2lsbCBzdWJtaXQgYSByZXZlcnQgZm9yIHRoaXMg
cGF0Y2guDQoNCkJhcnQu
next prev parent reply other threads:[~2017-08-16 17:22 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 17:00 [BUG][bisected 270065e] linux-next fails to boot on powerpc Abdul Haleem
2017-08-16 17:21 ` Bart Van Assche [this message]
2017-08-16 17:21 ` Bart Van Assche
2017-08-16 23:18 ` Brian King
2017-08-17 15:52 ` Bart Van Assche
2017-08-17 15:52 ` Bart Van Assche
2017-08-18 21:04 ` Brian King
2017-08-18 21:17 ` [PATCH] ipr: Set no_report_opcodes for RAID arrays Brian King
2017-08-21 20:22 ` Martin K. Petersen
2017-08-21 20:22 ` Martin K. Petersen
2017-08-18 21:41 ` [BUG][bisected 270065e] linux-next fails to boot on powerpc Bart Van Assche
2017-08-18 21:41 ` Bart Van Assche
2017-08-18 21:57 ` Brian King
2017-08-18 22:13 ` Bart Van Assche
2017-08-18 22:13 ` Bart Van Assche
2017-08-21 22:11 ` [PATCH 0/2] Allow scsi_prep_fn to occur for retried commands Brian King
2017-08-21 22:13 ` [PATCH 1/2] scsi: Move scsi_cmd->jiffies_at_alloc initialization to allocation time Brian King
2017-08-21 22:16 ` Brian King
2017-08-21 22:40 ` [PATCHv2 " Brian King
2017-08-22 6:51 ` [PATCH " hch
2017-08-21 22:14 ` [PATCH 2/2] scsi: Preserve retry counter through scsi_prep_fn Brian King
2017-08-22 6:51 ` hch
2017-08-22 6:42 ` [PATCH 0/2] Allow scsi_prep_fn to occur for retried commands Abdul Haleem
2017-08-21 20:27 ` [BUG][bisected 270065e] linux-next fails to boot on powerpc Martin K. Petersen
2017-08-21 20:27 ` Martin K. Petersen
2017-08-17 1:33 ` Michael Ellerman
2017-08-17 1:33 ` Michael Ellerman
2017-08-16 20:25 ` Bart Van Assche
2017-08-16 20:25 ` Bart Van Assche
2017-08-17 7:06 ` Michael Ellerman
2017-08-17 7:06 ` Michael Ellerman
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=1502904072.2421.3.camel@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=abdhalee@linux.vnet.ibm.com \
--cc=brking@linux.vnet.ibm.com \
--cc=hare@suse.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=sachinp@linux.vnet.ibm.com \
--cc=sfr@canb.auug.org.au \
/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.