From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934548AbeAOPdd (ORCPT + 1 other); Mon, 15 Jan 2018 10:33:33 -0500 Received: from mx1.redhat.com ([209.132.183.28]:56234 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934253AbeAOPdc (ORCPT ); Mon, 15 Jan 2018 10:33:32 -0500 Date: Mon, 15 Jan 2018 23:33:01 +0800 From: Ming Lei To: Mike Snitzer Cc: Stephen Rothwell , Alasdair G Kergon , Linux-Next Mailing List , Linux Kernel Mailing List , Laurence Oberman , axboe@kernel.dk, linux-block@vger.kernel.org, hch@lst.de Subject: Re: 4.16 genirq change prevents HP servers from booting [was: Re: linux-next: Signed-off-by missing for commit in the device-mapper tree] Message-ID: <20180115153300.GB13816@ming.t460p> References: <20180116002736.4d464214@canb.auug.org.au> <20180115152501.GA24239@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180115152501.GA24239@redhat.com> User-Agent: Mutt/1.9.1 (2017-09-22) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.28]); Mon, 15 Jan 2018 15:33:21 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On Mon, Jan 15, 2018 at 10:25:01AM -0500, Mike Snitzer wrote: > On Mon, Jan 15 2018 at 8:27am -0500, > Stephen Rothwell wrote: > > > Hi all, > > > > Commit > > > > 34e1467da673 ("Revert "genirq/affinity: assign vectors to all possible CPUs"") > > > > is missing a Signed-off-by from its author and committer. > > > > Reverts are commits as well. > > Right, I'm aware. I staged the tree that made some HP servers finally > work with the latest linux-block 4.16 changes. Without thinking about > the broader implications. Anyway, I'll drop the revert from > linux-dm.git's 'for-next'. > > Because I'm confident others will hunt down the irq issues. > > I think Ming was looking to grab the queue mapping info and CPU related > info from the affected server. Hi Mike, I have cooked a fix today, please see the following link: https://marc.info/?l=linux-kernel&m=151601867018444&w=2 This issue is clear, and has been described in above link and the patch. If no objection, I will prepare a formal version. -- Ming